You could/should make the URL be a GeoHash [1]<p>GeoHash's have the extremely attractive property that shorter versions of the same URL correspond to larger areas around the same point - ie, you can trade precision for size.<p>[1] <a href="http://en.wikipedia.org/wiki/Geohash#Example" rel="nofollow">http://en.wikipedia.org/wiki/Geohash#Example</a>
Very nice. We did something very similar some years ago, <a href="http://notamap.com" rel="nofollow">http://notamap.com</a>, with the idea of making it very easy to save maps with notes and embed them on your web. No sign-up, no database storing your data: everything is encoded in the URL you keep. A pity we never really polished it, nor tried to promote it. It has a small but faithful user base.
I like it. (my unsolicited advice) depending on how you are storing the data, you should let the user pass a query string or something to the url that returns the raw lat long in json format as opposed to the actual map, that way you have this mini api for more advanced users.
This looks cool and could be handy. I wonder how many phones could easily use this link for navigation though. Currently I use glympse if I want to tell people where I am so they can meet up with me or pick me up.
"Sorry to see you go" Alert everytime I refresh the site or open it in a new tab, it's actually more or less like a welcome message, so you might want to check it
I didn't think it would be able to "find me" accurately, but it did. Now I'm kind of worried :) I thought Google Location Service would not have this precision.
this is nice, how about letting the user drag the pin around in case the result isn't quite accurate enough (in my case it got my city, but what if i wanted to link to my house?)