-
Notifications
You must be signed in to change notification settings - Fork 10
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
Comments
At least Photon uses |
postalcode : HERE, Google, OSM tag, Nominatim |
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: |
Awesome! This gives some good points to "postalcode" :)
A friend of mine works there cc @vdct ;) |
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. |
👍 for disambiguating between HTTP POST and postcode |
@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. |
@yohanboniface @vdct the Michelin geocoder gives a whole new meaning to the phrase "Kick the tires on that API." I'll see myself out... |
Every geocoder API use postalcode in place of postcode.
The text was updated successfully, but these errors were encountered: