CODEWITHSUNDEEP
sql-server-2008google-maps-api-3geocoding
user1480836
user1480836

Reputation: 45

Best Practice around Geocoding?

Can anyone weigh in on best practice around geocoding location data?

We have several hundred "locations" (and growing) that are regularly inserted into the database.

We will occassionally run queries to plop these on a Google Maps using the Javascript API.

Do you think it's better to geocode these addresses when they're inserted into the database (ie, add lng and lat fields and populate and store these--addresses won't be modified manually) or call a geocoding service whenever we are generating our maps?

Upvotes: 1

Views: 387

Answers (3)

ccuesta
ccuesta

Reputation: 497

Storing the geocodes (but updating them occasionally) is a recommended best practice by Google.

Upvotes: 0

John Flack
John Flack

Reputation: 106

We call the geocoding api and store the latitude/longitude upon insert of a new record or update of any address field. Not only is this quicker when adding the location to a map, but it reduces repeated calls to the API. Given that there is a limit to the number of calls you may make in a day (enforced as calls per second) you don't want to do it any more than you have to.

Upvotes: 0

PaulMolloy
PaulMolloy

Reputation: 632

Storing the long/lat values will be much faster when it comes to use them. As long as you're happy they wont be moving around on their own between data entry and map drawing then do that.

Upvotes: 1

Related Questions