Written by astoryan on

great thanks

Written by clowride on

Hello Jacques can you create this field for cobalt please i can paid

thank you in advance

Written by jacques_v on

The purpose of this zip database is to calculate distances, for filtering etc.

I think it should be a part of an address field. A standalone field would be confusing for user.

What do you think about it?

It seems that in the Geo field, distance calculation is done. Did you try this field? Or is it something else you ask for?

Written by clowride on

hello

in fact sergei don't want zip in geo field

how can i do ?

Written by jacques_v on

I  for granted that resource fields can also be used as registration/touch fields.

Because I don't see any abstract difference between a record (in resource's sense) and a registered user.

So, for each field, I question its usablility both for records and/or users.

With this POV, it appears clearly that Geo field by itself is not well adapted for users registering. No user when registering would fill all the fields (contact, IM, all the nerd's things).

This Geo field is adapted to business records and is also a nice technical piece of code to make geeks dick hard, but it's not usable by itself by standard users (well, if you're creating a dating service, do you think people will like to be pointed by the global spying system of Google? It's so accurate that you can see your intrance door, even yourself if coupled with streetview. Completely unacceptable for normal people conscious of their privacy "pour vivre heureux, vivons cachés": to live happy, let us stay hidden).

So, users would need an address field plugin, with accesses to  all the text fields (number, street, city, zip, country) well settable from backend and/or frontend (FE: who can see my city, who can see my zip, BE:default value, settable from SE for each text field)  .  This way, a filtering by distance from zip code makes sense.

So so so… an address field is to be built. 

Written by clowride on

i agree, wait and see :(

Written by clowride on

Bonjour Jacques j'aurais besoin de vos connaissances si vous le voulez bien

J'ai soumis l'idée à Sergey au sujet des code postaux dans le field adresse, auriez vous quelques idées sur le "comment" implanter cette fonction. Le topic se trouve à cette adresse :

http://support.mintjoomla.com/en/cobalt-7/all/add+zip+database+to+geo-1558.html

Merci pour tout

Written by jacques_v on

(1) In my view, and having seen this feature on some sites (most administration and state sites), I think autocomplete from zip is not user friendly.

The problem is that, in many cases (all the small towns for example), the last digit has to be entered before autocomplete can work. 

For example, in Bouches-du-rhône, France, my own town: 13860: you have to wait for the 0 to be able to do useful city name autocomplete.

In this case, user saw an empty city field while typing Zip, which automatically fills only after he typed the last digit, and typed a TAB to go to the city field... only to find it being filled with the city name (if Ajax dialog was fast enough…). It's not user friendly at all, and only proves the skills of the geeky programmer (which is likely why you find it in overcrowded IT dept of state agencies…)

(2) I think a good use is to have the Zip as entered validating the city name against it, once it has been entered.

I mean city name field validation, once entered could be done through ajax calls sending city name and zip to the server, which would match them together and trigger an error if they don't (what I mean "trigger an error" is in the way Registration does: a message and a red cross on the field, no reloading of page, no geekeries)

(3) distance calculation can be used in 2 ways: to give an information to user. I mean you have an address field with zip code. You could set it in backend in order it calculates and displays distance to -user address as set in Touch/Registration, -to some fixed place , - to zip code entered by user, -to current gps place of user, as determined by his mobile.

Also as a filter, with the same setting as above, and filtering <threshold, <in this range>, >above threshold