Hi Marcelo, Thanks for your reply. You bring up some good points, so let me try to explain a little more:
> Define "all possible coordinates contained within the polygon". > Hint: There's an infinite number of points inside a polygon. Quite right. I suspect that there is a physical limit to the amount of points within a polygon in google maps... something to do with how many decimal places you can have in a GLatLng, but maybe not. In either case, its way more than the amount of queries I'm allowed to run at once. I think you understand what I mean though. > What is your intended area of coverage? A city? A country? The world? For this tool, the intended area of coverage is a handful of city blocks. > what do you need "all addresses" for? Just a requirement of the tool. They need that info for some business process that they do... something about delivery routes/efficiency. In either case, I'm not about to tell them how to do their job, its just something they want. > If you save your polygons to a database, then you can lookup what polygon a > given address belongs in, only if the address is relevant for a delivery. Polygons will be saved to the database, yes. See my previous answer for the rest. > It is recommended that you do store it. Addresses don't change > latitude/longitude, so there is no need to look up any given address more > than once. I thought this was against the TOC of google maps. Ideally, I would only run the script for all the addresses every few months to keep the documents current, and look up the paticular delivery site on a case- by-case basis. I hope those answers clear some things up. The problem still remains though, as to how to get the addresses contained in the polygon without running "infinite" queries. Is there a function that returns only the GLatLngs with addresses attached to them? That might work out if thats the case. If not, I'm stumped. Any thoughts? --Dan On Oct 21, 1:48 pm, Marcelo <[email protected]> wrote: > On Oct 21, 6:45 pm, DanMPP <[email protected]> wrote: > > > - is there an effective way to do this without running thousands of > > reverse geolocation queries, looping through all possible coordinates > > contained within the polygon? > > Define "all possible coordinates contained within the polygon". > Hint: There's an infinite number of points inside a polygon. > > What is your intended area of coverage? A city? A country? The world? > Those are very different scenarios. > > You might want to think about using predefined polygons, like > zipcodes, or counties. That would simplify the problem a lot. > Aside from that, what do you need "all addresses" for? > If you save your polygons to a database, then you can lookup what > polygon a given address belongs in, only if the address is relevant > for a delivery. You don't need information about the neighbours' > address. > > > I wouldn't be storing any > > of this information, just displaying it for immediate use. > > It is recommended that you do store it. > Addresses don't change latitude/longitude, so there is no need to look > up any given address more than once. > > -- > Marcelo -http://maps.forum.nu > -- > > > > > Any help you guys could provide would be great. Thanks. > > --Dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-api?hl=en -~----------~----~----~----~------~----~------~--~---
