Battuta no longers works because reverse geocoding service no longer exists

[sruti]

Overview

Battuta is no longer updating its file of EEA stations because the API being used to reverse geocode locations no longer works.

Order of events:

• Noticed we weren't pulling any data from the country Georgia after adding in the source file
• Realized it was because GE stations didn't exist in eea-stations.json, whicheea-direct adapter references
• Saw that the daily battuta build has been failing for the past couple of years
• The last time eea-stations.json on s3 was modified was Nov 2017
• Tried to run battuta locally, kept hanging because the reverse geocoding part wasn't working
• Discovered it was because the company that powered the API, Mapzen shut down in 2018

Options to consider

1) We swap out the geocoding service, Mapzen listed some alternatives, and keep running battuta and eea-adapter as is. This would require fixing the build error in Travis (caused by an npm install issue) 2) We find an alternative method to get the correct city for all sources, not just EEA. 3) We get rid of the city parameter all together (unlikely)

[dolugen]

Nice catch!

How many new locations are being added every month? If the numbers are low we could start using one of the free tier services (like OpenCageData).

Mapbox offers free tier of 100K requests/mo for their geocoding service. Although they explicitly prohibit retaining the query responses.

"NOTICE: © 2020 Mapbox and its suppliers. All rights reserved. Use of this data is subject to the Mapbox Terms of Service (https://www.mapbox.com/about/maps/). This response and the information it contains may not be retained. POI(s) provided by Foursquare."