> However, I also want to be able to query for the number of users from > a particular, say, state. I won't have that information from the > postal code alone. And I'd rather not bother my users with me asking > them for additional details. If Google allows me to cache geocode data > in order to save time and stay under the daily API query limit, maybe > extending it to the address components is also reasonable???
Google does not allow you to cache geocode data except in connection with a map. Using geocode data to e.g. analyse a user base is not permitted under the terms of the free licence. For a commercial proposition, obviously you could consider a commercial licence. > In any case, if I went with a different mapping service, I would > probably end up with a similar problem. Not necessarily, but you'll have to do your own homework. Have you looked at www.geonames.org , for one examnple. Or purchasing the postcode data for the country you are working in. > So, focusing on the database > design problem, what's the best way to model such data? Dunno, question for the database forum of your choice. It's rather academic until you have a source of data for your purposes. "Best" is subjective, so you'll need to qualify. Best for searching by which criteria, easiest to implement, minimal storage requirements, easiest to maintain, etc.? -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
