Google Maps V3 Geolocation Rails 3 gem 'geocoder' addresses not correct -


i'm using google maps v3 , it's not having trouble getting exact geolocations, it's not finding correct city (even missing more 50 miles in cases).

the way i'm using google maps in rails 3 app gem 'geocoder'. feel pretty sure it's not geocoder gem that's causing google maps off, think i've had problem in google maps v3 before.

my question: there better experience determining user's location? should use browser's built in geolocation features? or should using combination of google maps geolocation , browser's geolocation functions?

i imagined scenario ask user if town correct, , if not enter town, store town in database, seems poor user experience. hope make app on mobile devices in future, wouldn't of problem, it's web app.

anybody else have system dealing apps rely on user's location? thanks!

i ran same problem geocoder. me appeared not interpret address correctly in cases. if sent '250w 450n' street address coords *formatted_address":"250 e 450 s,*. if sent '250 w 450 n' got exact location looking for. try checking json response geocoder, tell "partial_match":true,"types":["street_address"]}} if "guessed" @ something, , can check returned *formatted_address* see came with.

you can use their website quick check on response given address string.


Comments

Popular posts from this blog

jasper reports - Fixed header in Excel using JasperReports -

media player - Android: mediaplayer went away with unhandled events -

python - ('The SQL contains 0 parameter markers, but 50 parameters were supplied', 'HY000') or TypeError: 'tuple' object is not callable -