|
My personal advice is to map with the correct coordinates (via map or via geotagged tags and google), and wait until Yahoo improves their maps. If the coordinates are ok, the name of the place will be automatically corrected that day for sure.
Posted 64 months ago.
(permalink)
|
|
It is all automatic. Correct coordinates is important. Anything else may improve by itelf with time. I have plenty of geotagged stuff with a bit odd "Taken in..." labelling.
Posted 64 months ago.
(permalink)
|
|
I have this problem w/ GPS coordinates taken w/ my Japanese cell phone here in Japan. They often show way off the mark when I use machine tags (geo:lat, geo:lon) to input the cell phone GPS data.
I'm glad to hear that I'm not the only one w/ this problem. Hopefully they come up w/ a solution to this.
Posted 64 months ago.
(permalink)
|
|
Ensure that your GPS unit is set to use WGS84 and not a local datum and spheroid. WGS84 is used in Yahoo, Google maps and Terraserver.
The Yahoo basemap is quite poor however, I would recommend use of google map coords via aemkai's bookmarklet v5.
Posted 64 months ago.
(permalink)
|
|
|
Looking in my phone and it's set to WGS-84, so it's definitely a Yahoo problem then.
Thanks for the tip!
Posted 64 months ago.
(permalink)
|
|
I have some photos by pointing to their location on the map or satellite view, and all I could think to do was put a note in my group (GWOS Greater Westchester Orchid Society www.flickr.com/groups/342504@N25/ ) that the named location is 5 miles away, and just hope people can figure it out that way. Since this message started in February 2007, 15 months ago, I guess they're not in a hurry to fix it. It's still wrong for my photos, anyway.
Posted 49 months ago.
(permalink)
|
|
It would be great if the "Taken in:" line was more general and correct instead of very specific and plain wrong (in dubio pro reo, as they say). Example in case:
Taken in: Berlin-Tegel International Airport, BE, DE
Nope, definitely not. The photo in question was taken 2.8km away from the nearest TXL airport fence line (as the crow flies). The embedded coordinates are correct and in maps, the photo is shown at the correct location.
Could it be that the "places" algorithm is too "greedy"? I can understand that flickr wants to identify "places", but a 3km radius around an airport doesn't exactly help when the airport is located in a city.
Originally posted 49 months ago.
(permalink)
cbmd edited this topic 49 months ago.
|
|
Here is an example too, where the country is wrong. It was taken in Germany and not in Austria. The border is the river Salzach.
Posted 49 months ago.
(permalink)
|
|
Seems Flickr is already working on a solution for this issue. Check out "Yahoo hopes users will help pinpoint photos".
I hope the Flickr Corrections project includes suggesting locations to non-geotagged or incorrectly geotagged photos as well.
Posted 49 months ago.
(permalink)
|
|
I don't think it's as simple as just a too sparse map or dumbed-down algorithm. I mapped two of my photos (using the Flickr map) to the same spot—I dropped the second onto the first—and they are "Taken in" two different places:
www.flickr.com/photos/acornsarebitter/2476862020/
www.flickr.com/photos/acornsarebitter/515060877/
The irony is both are located in the heart of Stanford University, where Yahoo! started, and near which it is still located. They talk about it being hard to agree on neighborhood boundaries, when they can't even get well-defined city boundaries correct in their own backyard.
Posted 49 months ago.
(permalink)
|
|
|
1600 Squirrels: I'd think that assigning the "Taken In:" locations happens at upload (or when you geotag using the Flickr map). If you geotagged those photos quite some time apart, your example just shows that there is a certain fluidity in the borders that define sublocations.
That in itself is normal: Some time a ago the city of Berlin decided to restructure city districts and (in theory) a photo tagged as taken in Wedding, Berlin, DE might now be tagged Mitte, Berlin, DE because the Wedding district was merged into the Mitte district (yet, most people would still use the Wedding designator to talk about it, and no it is not related to the ceremony). I can image that this happens all over the place and all the time, so staying on top of those changes will be hard (if not impossible).
My main concern was that the Places algorithm decided (?) to mislabel my image using a very small and geographically well defined sub-sub-sub-location instead of a more broad and likely correct sub-location. The "subbier" or specific the location tag is, the more likely it is going to change over time. For example: the airport referenced for my image will be closed in, uhm, 2013 or so. Also, using sub-sub-sub-sub-locations is kind of superflouus. Either it is already described in my tags or seaching geographically via a bounding box will turn it up.
Incorrect tagging is worse than slightly inaccurate tagging or no tagging at all.
Posted 49 months ago.
(permalink)
|
|
|
Stanford was founded in 1885, and the City of Palo Alto incorporated in 1894 (the city charter dates to 1909). AFAIK, the border between the City and the University has not changed since 1925. One thing I know for sure: Palo Alto hasn't included the Stanford Quad (where the photos were taken) since at least 1992 when I lived on campus and my address was Stanford, California.
So maybe Yahoo! updated its map sometime in the last year, but the City of Palo Alto and the US Postal Service didn't.
It's not a question of just informal neighborhood names. Last time I checked, Flickr categorizes half of the City of Alameda (which dates back to 1853, and has been an island, and thus has had well-defined borders, since 1902) as being part of the City of Oakland.
Posted 49 months ago.
(permalink)
|
|
|
Flickr Corrections is now live, now you can edit the "Taken In" location and in the process improve the reverse geocoding engine. There is an interesting blog post and video on the feature here.
Posted 46 months ago.
(permalink)
|
|
it's like that google maps error last week
www.geeksaresexy.net/2008/08/15/google-maps-gets-its-geor...
Posted 46 months ago.
(permalink)
|
|
|
Kinda. The google maps/news error has more to do with an incorrect geocoding. Flickr Corrections is more about improving reverse geocoding.
You do bring up a good example of a geocoding error, in Flickrs case it would be a case in which a photo is tagged incorrectly. I kinda hoped that Flickr Corrections would also provide a similar method of suggesting locations to the photo's owner like Panoramio does. There has been much discussions on geotagging suggestions on the Flickr Ideas group.
Posted 46 months ago.
(permalink)
|
|
|
I am assuming that the Flickr Corrections feature gets its data from the WOE (Where on Earth) service which Yahoo acquired. Does anybody know if there is a way to suggest location data to the service? I am finding areas which are lacking placenames.
Posted 46 months ago.
(permalink)
|
Would you like to comment?
Sign up for a free account, or sign in (if you're already a member).
|
GeoTagging Flickr /
Discuss
Feed – Subscribe to GeoTagging Flickr discussion threads