Reviews from AWS customer

4 AWS reviews

External reviews

1 review
from

External reviews are not included in the AWS star rating for the product.


    reviewer2833311

Accurate coordinates have powered faster weather data integration for remote store locations

  • April 28, 2026
  • Review provided by PeerSpot

What is our primary use case?

I was using Geocoder.ca for around two months for a project at my current company. We were trying to work with weather stations and weather data for specific stores in countries like El Salvador, and we used Geocoder.ca to fetch the locations for those weather stations.

Because some of these weather stations were in quite remote locations, Geocoder.ca definitely helped me save time and speed up my development process by fetching the information that I needed. It was used for on-premises purposes as it was only needed for one-time fetching.

What is most valuable?

Geocoder.ca provides an easy-to-use API that programmatically allows for clear access and clear data fetching, which are my main use cases.

The documentation for Geocoder.ca is very clear, allowing me to accurately test my APIs using Postman, and the endpoints are also equally clear and made a lot of sense.

Geocoder.ca helped me move along and ship out location-based features faster. For countries that have sparse latitude and longitude data available, I am able to rely on Geocoder.ca to fetch that information.

What needs improvement?

If Geocoder.ca had a direct connection with weather stations, that would be very useful. Rather than just giving me coordinates, immediately providing me with weather data would be a helpful improvement. Other than that, it does the job quite accurately.

Adding more features than just plain coordinates would be beneficial, such as weather or other features that would make Geocoder.ca a ten for me.

For how long have I used the solution?

I was using Geocoder.ca for around two months for a project at my current company.

What do I think about the stability of the solution?

Geocoder.ca is stable.

What do I think about the scalability of the solution?

Geocoder.ca looks very scalable and seems to handle scalability quite well.

How are customer service and support?

I never had to deal with any customer support for Geocoder.ca because the library and results worked quite well.

What was our ROI?

Time was definitely saved with Geocoder.ca; however, it is tough to quantify exactly by how much.

What's my experience with pricing, setup cost, and licensing?

Because I did not need a large amount of coordinates, I was able to get by with the free tier of Geocoder.ca, making it quite useful and impactful. However, going forward, if I get requirements from a different client, I am sure I will probably get to pricing and higher tiers.

Which other solutions did I evaluate?

I evaluated various weather station APIs before choosing Geocoder.ca; however, the coordinates that they were giving me were not matching up to the actual weather station itself and were off by a fair margin. Geocoder.ca's accuracy was what really impressed me.

What other advice do I have?

Geocoder.ca is a very good platform and it was giving accurate results; however, after consistent usage and client requirements, I did not need that level of detail and granularity, and hence I moved on from Geocoder.ca.

It is a good library. Geocoder.ca does the job that it is supposed to do and does it quickly, efficiently, and more importantly, accurately. When it comes to location, exact coordinates are extremely important, especially for my purpose, which was weather. I would rate this product an eight out of ten.


    Kamil Mroczek

Accurate and Versatile, but

  • December 01, 2017
  • Review from a verified AWS customer

Geocoding was pretty accurate, on par with what you'd expect from Google Maps or ESRI. Lots of info returned on reverse geocoding. Forward geocoding and parsing of raw text was fine too.

A bit slow right off the bat. Using the test_performance.pl script that comes with it:
-bash-4.2$ /home/ec2-user/test_performance.pl
End test at Thu Nov 30 19:17:10 2017 (Test started at Thu Nov 30 19:08:02 2017, total time spent: 547.783696889877 seconds.)
198 requests were sent in parallel
Average response time was 2.76658432772665 seconds per request

Then tried the test again after a few minutes:
End test at Thu Nov 30 19:21:11 2017 (Test started at Thu Nov 30 19:21:06 2017, total time spent: 4.92717409133911 seconds.)
198 requests were sent in parallel
Average response time was 0.0248847176330258 seconds per request


So, it is slow at first, then picks up speed considerably. 0.02 seconds per query vs 2.7. (on a C8x8xlarge server)


    Sean

Incredibly Slow

  • May 31, 2017
  • Review from a verified AWS customer

I appreciate that it works out of the box, but even on an r4.2xlarge instance it regularly takes 15-120s to geocode a structured address. SQS queue has been draining for days now.


    Tim Stallmann

Not very flexible

  • February 09, 2016
  • Review from a verified AWS customer

Very easy to use and install! But

Compared to the free MapQuest nominatim this was slower - although maybe it needed to churn longer to get through startup tasks? I ran 500+ queries and didn't see a significant speed increase - and much less willing to make a guess about vague addresses or assign PO Boxes to the city or zipcode centroid.


    Brian Pichette

Great product!

  • November 09, 2015
  • Review from a verified AWS customer

Very easy to launch, very efficient, and cost effective compared to alternatives. Results were accurate. Highly recommended for high volume processing. Support was very responsive and knowledgeable.


showing 1 - 5