4 ms·

The comparison page link is comprehensive, nice! To summarize the main point of roll-your-own vs. a pay-per-request api the main point seems to be updating wit

by awongh 1y ago

The comparison page link is comprehensive, nice! 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)

freyfogle 1y ago
There is a list here (vs. Google) https://opencagedata.com/guides/how-to-switch-from-google-maps-geocoding https://opencagedata.com/guides/how-to-switch-from-google-ma... 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. And here is a similar comparison versus running your own Nominatim https://opencagedata.com/guides/how-to-switch-from-nominatim https://opencagedata.com/guides/how-to-switch-from-nominatim Please let us know if anything is out of date or can be made more clear. Thanks.
- awongh 1y ago
  Thanks! Is there a chance you guys will ever switch to a per-request pricing model?
  - freyfogle 1y ago
    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.
    - awongh 1y ago
      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. I suppose you can't please everyone.
      - freyfogle 1y ago
        > I suppose you can't please everyone. correct
  - NetToolKit 1y ago
    FYI, my site (NetToolKit) offers per-request pricing, in increments of $10 (for 100,000 requests): https://www.nettoolkit.com/docs/geo/overview/geocoding https://www.nettoolkit.com/docs/geo/overview/geocoding -- no monthly fees if you do not make requests.

by awongh 1y ago

freyfogle 1y ago

There is a list here (vs. Google) https://opencagedata.com/guides/how-to-switch-from-google-maps-geocoding https://opencagedata.com/guides/how-to-switch-from-google-ma... 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. And here is a similar comparison versus running your own Nominatim https://opencagedata.com/guides/how-to-switch-from-nominatim https://opencagedata.com/guides/how-to-switch-from-nominatim Please let us know if anything is out of date or can be made more clear. Thanks.

awongh 1y ago
Thanks! Is there a chance you guys will ever switch to a per-request pricing model?
- freyfogle 1y ago
  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.
  - awongh 1y ago
    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. I suppose you can't please everyone.
    - freyfogle 1y ago
      > I suppose you can't please everyone. correct
- NetToolKit 1y ago
  FYI, my site (NetToolKit) offers per-request pricing, in increments of $10 (for 100,000 requests): https://www.nettoolkit.com/docs/geo/overview/geocoding https://www.nettoolkit.com/docs/geo/overview/geocoding -- no monthly fees if you do not make requests.