| ||
Thu 2024-11-14
Wed 2024-11-13
Tue 2024-11-12
Mon 2024-11-11
Sun 2024-11-10
Fri 2024-11-08
Tue 2024-11-05
Sun 2024-11-03
Sat 2024-11-02
Fri 2024-11-01
Search
Archives
2023
12 11 10 09 08 07 06 05 04 03 02 01
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
One good site
MDN
Nelson Minar
Blog licensed under a Creative Commons License
|
Congratulations to the Flickr team for their new geotagging
interface. I think this is the first time it's truly easy
for normal people to indicate where they took their photographs in a
way others can benefit from.
It's a bit late for a pony request, but I sure wish geocoding interfaces had a notion of uncertainty along with location. Ie: latitude, longitude, and radius. A photo geocoded to "San Francisco, CA" is different from a photo geocoded to "659 Merchant St. San Francisco, CA". The former has a radius of about four miles. The latter, 20 feet. Tagging your photos via a map interface gives a natural radius: a few pixels' width in the map the user clicked on. GPS devices have a natural uncertainy measurement, too. So the data's available, why not store it? Update: A Flickr developer wrote to tell me that their
geotagging does store and use accuracy data. If you ask for
photos in a precise location you don't see photos that are too
general. Cool! Looks like its in the
API too.
Thanks to pb
for the term fuzzy geocoding
|
|
