To summarize the main point of roll-your-own vs. a pay-per-request api the main point seems to be updating with updated/new OSM data.
In terms of comparing Google Maps vs. Open Cage vs. roll your own OSM / Nominatim what would you say are the main features that are different? (not dev time or infra stuff- just what's different about the request/result)
though really the key difference is the fact that we use open data. Googles data is not open, this significatly restricts what you can do with the data.
well the pricing models are per request, but just in easy to understand buckets (small, medium, large). Our experience is most people prefer this as they know exactly what they will spend, there is never a surprising bill.
That said we do have enterprise customers with other pricing models to meet their exact needs. Please get in touch if we can help you.
To be specific my use case is for a seasonal-based app. So I neither want to pay for 10 months where $45 is too large, or buy a pre-determined amount without auto-reload where it's possible to run out of requests if I'm not careful.
To summarize the main point of roll-your-own vs. a pay-per-request api the main point seems to be updating with updated/new OSM data.
In terms of comparing Google Maps vs. Open Cage vs. roll your own OSM / Nominatim what would you say are the main features that are different? (not dev time or infra stuff- just what's different about the request/result)