How We reduced our Google Maps API cost

Post by BubRoss » Tue, Apr 07, 2020, 7:48 PM UTC

AnotherGoodName wrote: post #171

BubRoss wrote: post #170

Earlier quoted context omitted.

Are you saying that you did that to switch off of google's API?

No. The only part of Googles API we considered was reverse geocoding. The train data was always ours.

Right... but that would mean that what you are querying google for doesn't change. The coordinates of the trains would even only be along their route. Once you have done a reverse lookup on enough points along the route, you should have a pretty dense idea of where the neighborhoods change, right?

I am not sure if I'm missing some big, but it really seems like there wouldn't be an ongoing need for querying google's APIs in this case. Finding the boundaries of the neighborhoods and especially labeling stops should be easy enough to do if it would save so much money.

Re: How We reduced our Google Maps API cost

Re: How We reduced our Google Maps API cost