Location tagging

[jace]

Hasjob should use location tagging instead of a freeform location text field. The Geonames webservice can be used to autocomplete location names:

http://ws.geonames.org/searchJSON?name_startsWith=<term>&countryBias=IN&featureClass=P&callback=<callback>

[miteshashar]

If we are using jQuery-UI, there is an example on the autocomplete demo
page, which gives us code to quickly pick up and modify to our needs.

On Wednesday, 24 July 2013, Kiran Jonnalagadda wrote:

Hasjob should use location tagging instead of a freeform location text
field. The Geonames webservice can be used to autocomplete location names:

http://ws.geonames.org/searchJSON?name_startsWith=
&countryBias=IN&featureClass=P&callback=

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/55
.

Regards,
Mitesh Ashar

[jace]

The geonames.org service does not work with HTTPS. The certificate is for *.geonames.net, but that domain is for premium users and requires an API key. This means we'll need our own HTTPS-capable version of geonames after all.

[jace]

Premium API starts at 40€ per year. http://www.geonames.org/commercial-webservices.html

[jace]

The 40€ version isn't bad at all. It provides 100,000 API call credits (ie, 100k calls to the search endpoint). If that's not enough, the 80€ plan is 1 million credits. Using this is far cheaper than the developer time required to setup our own copy of the data.

[jace]

Related issue in hascore.

[jace]

Impemented in 8a07316, 419909e and c1f2c42.