It was originally based on Pelias, but we've since augmented with additional data sources (such as Foursquare OS Places) and significantly improved the baseline for performance and accuracy.
Happy to answer questions on the topic!
It was originally based on Pelias, but we've since augmented with additional data sources (such as Foursquare OS Places) and significantly improved the baseline for performance and accuracy.
Happy to answer questions on the topic!
Can I keep those points if I'm no longer a customer?
Can I resyndicate those stored points via my own API?
> permanently storing results for future use (e.g., as a database column), in part or in whole, from the Stadia Maps Geocoding APIs without an active Standard, Professional, or Enterprise subscription with appropriate permissions;
(Having scanned those terms I'm still not 100% certain I can confidently answer all three of my questions though. A classic challenge with this is that terms often have language that relates to map tile images, but it's hard to derive if those same terms apply to geocoded lat/lon points.)
https://docs.stadiamaps.com/geocoding-search-autocomplete/bu...
> Can I Store Geocoding API Results?
> Unlike most vendors, we won't charge you 10x the standard fee per request to store geocoding results long-term! However, we do require an active Standard, Professional, or Enterprise subscription to permanently store results (e.g. in a database). Temporary storage in the normal course of your work is allowed on all plans. See our terms of service for the full legal terms.
Is that something I should report as a bug, or is that the way it is supposed to be?
Definitely drop us a line. Our v2 response structure is still undergoing some iteration, especially around the particulars of labeling, so this may be intended (depending on the specific query), but we can certainly look into it to confirm that.