Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

postcode VS postalcode #9

Open
frodrigo opened this issue Jul 9, 2015 · 9 comments
Open

postcode VS postalcode #9

frodrigo opened this issue Jul 9, 2015 · 9 comments

Comments

@frodrigo
Copy link
Contributor

frodrigo commented Jul 9, 2015

Every geocoder API use postalcode in place of postcode.

@yohanboniface
Copy link
Member

Every

At least Photon uses postcode, please be a bit more specific, we need accurate informations to take good decisions :)

@frodrigo
Copy link
Contributor Author

frodrigo commented Jul 9, 2015

postalcode : HERE, Google, OSM tag, Nominatim
postcode: opencagedata

@riordan
Copy link

riordan commented Jul 9, 2015

It just so happens I've been looking across a large variety of geocoders terminologies lately, so perhaps I can be of service. Don't treat this as a comprehensive survey.

Team Postcode:

Team Postalcode:

Team None of the Above:

Other supporting things:
The Universal Postal Union calls them as Post Codes. It's a pretty amazing organization.

@yohanboniface
Copy link
Member

Awesome! This gives some good points to "postalcode" :)
(I don't see Pelias in the list, though ;) )

Michelin | Yes the tire and restaurant people have a comprehensive geo API. Who knew?!

A friend of mine works there cc @vdct ;)

@riordan
Copy link

riordan commented Jul 9, 2015

I figured my commentary on this should remain separate from the above survey.

Here's where we get into semantics. I tend toward postal code the definitive & disambiguating name in this context. In this case, we're working on a standard that will (hopefully) be used frequently alongside HTTP, which has as one of its primary operators POST. In order to preserve (some) clarity between two very distinct ideas, I'd like to throw my support behind postalcode (or postal_code, as Google has done, preserving the complete term) for clarity and interoperability.

@orangejulius
Copy link

👍 for disambiguating between HTTP POST and postcode

@dianashk
Copy link

dianashk commented Jul 9, 2015

(I don't see Pelias in the list, though ;) )

@yohanboniface, we're in the process of redesigning our API (hence the exhaustive survey of existing things @riordan has referenced above) to address naming conventions, among other things. This is also why we have taken such an interest in what you're doing here, as specifying the format of the results is a large piece of the API redesign puzzle.

@riordan
Copy link

riordan commented Jul 9, 2015

@yohanboniface @vdct the Michelin geocoder gives a whole new meaning to the phrase "Kick the tires on that API."

I'll see myself out...

@vdct
Copy link

vdct commented Jul 9, 2015

@riordan @yohanboniface :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants