Geo Follow-up
. Updated: .
‘Miner at the Dial-a-View’ – GrandaddyHello, welcome to dial-a-view
To locate the area in which you wish to observe
You must program in the longitude and the latitude
For a closer, more detailed picture
Use either the zoom or micro-zoom controls
Good luck
Following my pondering about Geo-Accuracy earlier in the week, I’ve finished geotagging (almost all) my Flickr photos and spent a bit of time whether some sort of representation of inaccuracy could be incorporated gracefully into the geo microformat.
Meanwhile on Flickr, I accidentally discovered this:
Warning message from the Flickr Organizr tool
So the wonderful revelation is that Flickr already looks out for vague, less accurate geotagging, allowing you to flag something as inaccurate but still make use of the mapping features. That’s very well thought out. I wonder if they express it through the API, or in mark-up, or if it’s just a background flag.
Links
To share this entry, or reference it in commentary of your own, link to the following:
- Permalink: https://benward.uk/blog/geo-accuracy-2
- Shortlink: https://bnwrd.me/1VnNoa
You can file issues or provide corrections: View Source on Github. Contributor credits.
Comments
Previously, I hosted responses and commentary from readers directly on this site, but have decided not to any more. All previous comments and pingbacks are included here, but to post further responses, please refer me to a post on your own blog or other network. See instructions and recommendations of ways to do this.
Well, according to the API docs locations are returned with a numeric ‘accuracy’ property. I can only assume that it corresponds somehow to the zoom level of the map when it was placed, but the documentation is rather scrappy on this point.
I guess they should really allow tagging with a bounding-box, two pairs of lon/lat coordinates at diagonal opposites of a box.
Do they allow for searching for photos within an area, or any other kind of spatial query?