Phi, Lambda and (Slightly Embarassing) Temporality

Longitude and latitude have been formally used as a geographic coordinate system offset from the Greenwich Meridian since the International Meridian Conference of 1884 in Washington D.C.

As a spatial coordinate system, longitude (abbreviated as φ, or phi) and latitude ( λ, or lambda) work very well in defining a point on the surface of the Earth. But to gain further meaning from a long/lat pair you either need some clever algorithmics or you need to plot the long/lat point on a map which even then will yield information only as good as that which is rendered on the map itself.

Astride The World

Which is why I think identifier systems, such as Yahoo’s WOEID, add so much value. A WOEID adds a linked web of rich metadata, describing not only a point with a long/lat centroid, but also reinforces the concept of a place, with neighbouring and hierarchical relationships.

Coordinates describe the where of a place, identifiers such as WOEIDs describe the how of a place but both conveniently (in a slight embarrassed, foot shuffling short of way) overlook the when of a place.

Former Flickr geo-hacker and current Stamen Design geo-hacker, Aaron Cope, posted a way around the temporality problem on his blog this evening, describing spacetimeid, a web app which encodes and decodes a 64-bit identifier combining x, y and z coordinates.

So far, so timely; a spacetimeid allows us to describe not only a point but also a time. The logical next step to this is to allow the encoding of a WOEID, that includes a long/lat centroid, with a time range. Two immediate use cases spring to mind.

Firstly, this allows us to represent places which have a small temporal range, such as festival or concert venues; this is frequently referred to as The Burning Man Problem, after the annual festival of the same name. During the duration of the festival Burning Man exists as a concrete place, outside of the festival timescales the site of the festival is empty land.

Burning Man 2007

Secondly, this allows us to represent changes in places over a large temporal range, which can be used to rectify historical maps and show the change in a place over a number of years.

I pinged Aaron a mail on this, saying “Encode temporal information in range format plus WOEIDs ? … Thinking a WOEID for Burning Man or similar here“. He replied a few minutes later with “Yes, that would be easy enough to do if the (x) is the WOEID and the (y) time. I can add that later“. Followed, in the time it’s taken me to write this post, with “Ask and all that … http://spacetimeid.appspot.com/woe/encode/44418/1268854022“.

Now all we need to do is get this used in the real world and the slightly embarassing problem of temporality will have been solved once and for all. Easy isn’t it?

Photo Credits: Foxgrrl and Kaptain Kobold on Flickr.
Written and posted from home (51.427051, -0.333344)

One Comment

  • The temporal equivalent for woeids are not time ranges but something more structured and less precise. You’d need permanent and unique ids for concepts like “the middle ages”, “20th century” “the 1990′s” “week 1 of 2010″ etc. that can than be arranged in a similar structural hierarchy as woeids are hierarchically arranged.

    Sadly, nobody has yet come up with these WITids (when-in-time ids).

    But I agree that a WOEid/WITid pair would be a great way to represent things.