| Geo-data is effectively 'read-only', it seems to me.. There are things local people know about, which still diffuse by word of mouth - and I still see paper notices posted on lamp-posts and at supermarket boards. This is why I did an experiment and built lokenote.com I havent nailed it with lokenote, but it hints theres something there... Im aware this is a first, imperfect approximation of the kind of tool that will enable people to annotate locations. Sometimes you need to build these experiments to see what works or doesn't. I dont think the storing/retrieving of geo-data is that hard a problem, you can roll your own nested squares approach, or reuse whats there now, eg. Mongo 2d indexes. Rather, I think the problem is making a nice way to integrate the location dimension into our tools/web apps more seamlessly. eg. a dating chat app might just favour partners close to your location without being told what postcodes to look in. I see this as a 'too many knobs' type problem ( a bit like those search forms you see that have options for 10 different dimensions to filter on, which are better replaced by a single text search field, with hidden smarts. ) So how to bring location to the people, so its useful, effective, un-intrusive and read-write ? I dont think that question has been answered. [edit readability] |
Whilst it's true a lot of data appears to be read only (of the kind, what is where?), even geological features change given enough time (or little time if we're talking water features in a world of global warming).
Given that what we're discussing is mostly man-made features, such as physical buildings and the businesses that occupy them... these are open to change. Buildings get built, demolished, and far more frequently modified.
And then there are problems like "Where can I park?". Most parking in London is street parking rather than car parks, and parking restrictions change frequently enough that it isn't static data.
Once you concede time is a dimension that affects spatial information, you open yourself up to far more interesting possibilities: What is happening nearby? Where are my friends? There's traffic up the road, what's causing it and should I detour?
This is massively changing data. It could be expressed as a read-only stream of 'events' that 'occur' at different places (check-ins, tracking data)... but the data is refreshed so frequently that storing as a read-only audit trail of events just disguises the fact that people will perceive the information as permanently changing.
I think the hardest part of dealing with geospatial data is ensuring that it is fresh enough to be valuable data. And that is to work from the point of view that everything changes constantly.