Overview
Scan text for locations, extract addresses, street intersections, postal codes, zip codes and place names. Geocode the extracted locations into Latitude,Longitude,Elevation and export the results as GeoJson, Json, XML or CSV. Reverse geocode coordinates to addresses, place names, postal codes, zip codes, location codes, elevation and unique location numbers. Worldwide. Use our Autocomplete API for incomplete address data. Batch geocode large datasets. Our API also provides sentiment analysis on text and IP address geocoding.
Highlights
- Geoparsing Geocoding Reverse Geocoding API
- Unlimited use
- Worldwide coverage
Details
Typical total price
$1.333/hour
Pricing
- ...
Instance type | Product cost/hour | EC2 cost/hour | Total/hour |
|---|---|---|---|
t2.2xlarge | $1.00 | $0.371 | $1.371 |
t3.2xlarge Recommended | $1.00 | $0.333 | $1.333 |
t3a.2xlarge | $1.00 | $0.301 | $1.301 |
m4.2xlarge | $1.00 | $0.40 | $1.40 |
m4.4xlarge | $1.10 | $0.80 | $1.90 |
m4.10xlarge | $1.20 | $2.00 | $3.20 |
m4.16xlarge | $1.30 | $3.20 | $4.50 |
m5.2xlarge | $1.00 | $0.384 | $1.384 |
m5.4xlarge | $1.10 | $0.768 | $1.868 |
m5.8xlarge | $1.10 | $1.536 | $2.636 |
Additional AWS infrastructure costs
Type | Cost |
|---|---|
EBS General Purpose SSD (gp2) volumes | $0.10/per GB/month of provisioned storage |
Vendor refund policy
We don't offer refunds, but you may cancel at any time.
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Version 2.6 is a security bug fix.
Additional details
Usage instructions
Access the server on http://<instance-ip>:80 for usage instructions & quick start. Make sure your server has at least 30GB of memory. You may also SSH to the instance and log in as 'ec2-user' using the key specified at launch to use the API internally. Additional information can be found at : https://geocode.xyz/api .
Support
Vendor support
Setup and Use of Product
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
Customer reviews
Cannot load
Have tried loading this instance with everything up to a c5.18xlarge and cannot get any response from the public IP or SSH. Thisis after 30 minutes. I hope I'm not being charged from creation of instance ---
worked like a charm
Reverse geocoded a few thousand locations (mostly in western Europe) and it worked like a charm. I ssh-ed into the box and adjusted one of the example scripts to process my csv file.
It is cheaper to just launch a small server which gives unthrottled and unlimited api access(I launched a T2.2xlarge) than using their batch web api if you have a small file ($1.3 vs their minimum $20 charge)
It does the job, but could be a bit faster
So, I went ahead and tested with the cheapest possible instance ( r4.2xlarge ). It is not available on any instance with less than 60GB of RAM, unfortunately.
After I started the instance I got a message on port 80 saying: "Temporarily Unavailable :
Churning through startup tasks. Try again in a few minutes."
"A few minutes" turned out to be about 6 minutes. After that it was still slow to respond for another 10 minutes, so I guess the "churning" was not yet complete.
It did perform reasonably well afterwards on my test suite for both Reverse and Forward geocoding. My test suite contains worldwide locations, with the majority in Singapore, Australia and New Zealand.
As to the quality of the results, they were good. My only reason for the three stars is the slow time it took for the machine to get off the groud and running (about 20 minutes including the "churning" time), and also the fact that it is not available on cheaper instance types.