|
I'm just starting to convert an app from V2 to V3 that relies on geocoding an address or lat/lng in order to generate directions to nearest hospital. V2 geocode results provided an "accuracy" scale that doesn't appear to be in V3. When accuracy in V2 was 8 I could rely on using the returned result, and if it was lower user was given option to drag marker to attempt to improve on address quality in order to request directions from that location. I'm now trying to parse my own accuracy in V3 using following params result.types I'm surprised the V3 geocoder doesn't provide an accuracy scale the way V2 did. If anyone can provide any feedback on creating an "accuracy" test would be greatly appreciated My starting point is something like: if( types[0]=='street_address' && ! partial_match && geometry.location_type=='ROOFTOP'){ accuracy=10; } same as above but with
partial match => accuracy = 9 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 google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en. |
