P: Latitude/longitude search wildly inaccurate in Map module

Same issue.
And I would say it's not the only one in terms of poor gmaps integration.
see also: http://forums.adobe.com/message/53521...

Kind of a (nerve-racking ) workaround is to enter the GPS data in the photo meta data directly after using the full-blown gmaps in a browser version

Copied from the merged thread:

There are three separate issues here:

1. As Steve just pointed out, Google Maps shows both the exact coordinates and the nearest named entity, but LR just shows the nearest named entity. Please see these other feedback threads for more details:

2. LR 4.1 RC2 doesn't allow coordinates of the form "30.832783, 111.109783‎" to be entered into a photo's GPS field in the Metadata panel. You have to add compass directions, e.g. "30.832783N, 111.109783E‎". See this thread:

http://feedback.photoshop.com/photosh...

Please add your vote to it.

3. In Internet Explorer, selecting and copying the text "30.832783, 111.109783‎" from your post in this thread results in a Windows clipboard containing an invalid character at the end. Pasting that clipboard into Google Maps results in the error message "We could not understand the location 30.832783, 111.109783‎". Pasting that clipboard into the LR 4 Map search box results in a similar error message. Weird bug in IE.

LR 4.1 RC2, fresh Windows 7 x64 installation.

HOW TO REPRODUCE:

In the map module, trying to create a 'Location' at specific coordinates:

- place focus on the location Searchbox
- input coordinates (as given by maps.google.com): 30.832783, 111.109783‎
- LR complains that they are not found, even if these are perfectly valid coordinates
- input coordinates again (still as given by maps.google.com): +30° 49' 58.02", +111° 6' 35.22"
- LR accepts these now and creates an orange icon at "334 Yiling Road [...]" which is plain wrong. The true coordinates refer to a steep slope with no road at all, as can be seen in the field or on Google Maps.

RESULT : LR places the icon about one mile (!!!) NNW of the user-input coordinates. Note that in some cases, the error can reach as much as 15 miles.

HYPOTHESIS :
It appears Adobe Lightroom forbids creating a user-defined location outside of populated areas (town/village) or road addresses. This is a no-go for any serious wildlife photographer wanting to georeference his/her work, who sometimes has to venture several dozens of meters away from cities and motorways.

FIX (?) :
To define a location at the right place, one should create the location at the wrong place, exit Lightroom, go to the 'Lightroom Settings\Locations' directory, manually edit the related .lrtemplate to input the correct coordinates (this time, in decimal degrees format, although LR supposedly does not understand them...) then relaunch Lightroom.

>> Not sure if such a weird behaviour is rather a bug or some intended feature, but it makes geolocating one's photos with relatively good precision (let's say: at the kilometric level) a pain-in-the-back.

There appears to be a bug in the lightroom map module when you enter GPS coordinates in the search box. For example, if you put in 44.498656,-118.639716 you get taken to a spot that is about 500m off of what google maps is reporting.

BTW the process for reporting a lightroom bug is incredibly cumbersome. I was directed to this site, had to create an account, then had to find where to post the issue, etc.

Another report:

http://feedback.photoshop.com/photosh...

Another person trips over this, but in the central part of a city:

http://forums.adobe.com/thread/960400...

My camera, a Sony a55 has built in GPS. When I take a look at the photos in Lr4, it places most of them in the centre of the town I live in, which is nowhere near where I live (and where the photos were taken). Bizarrely though, other pics are placed not merely at the local science park but in the precise building where they were shot.

This obviously impacts wilderness locations, e.g. 37.101, -118.733.