> I do wonder though whether its fair to expect that street names that > we might enter will match identically with googles geocoded street > names, and would also need to deal with identical street names.
"seems fair"? I think whatever you might expect, you have to give Google enough to work with to guess what you might mean; just the same as if you try to send mail to an address the postal service doesn't recognise. But why do you think things need to match identically? > Out of interest - if appears that detection of polyline crossings is a > common requirement in GIS and I'm wondering if anyone is aware whether > this might be built into future API versions (or whether it is > something that the API should / cannot be expected to do)? Google Maps API is maps display for webpages ... is not really a GIS system. If you want a GIS system, get one. If you want to add line crossing algorithms to the API, you can; it does give you the flexibility. http://www.google.com/search?q=line+crossing+algorithm You could create an enhancement request for poly-crossing features, to garner support http://code.google.com/p/gmaps-api-issues/issues/list No-one has yet done so -- 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.
