I helped my friend Tamara Maloney put together a little elegant site to show off her Editors Reels, and drum up a little business. Need an editor/director/producer for your film project? maymaloney.com.
Archive for December, 2006
Andrew Turner has released an Introduction to Neogeography Short Cut for O’Reilly. It’s total drinking from the firehose, intense survey of all things geo-amatuer, a great jump start for neophytes to neogeography, kinda like compressing three years of geowanking, conferences, and hacking into an afternoon read.
Note I’m a pretty biased reviewer. Andrew asked me to review a rough draft, and I have the pleasure to work with Andrew on several projects, some mentioned in the Short Cut. He and myself are presenting much of the same concept in the Adding Location to Web 2.0 Apps session at Web 2.0 Expo. But be sure this Intro matches the volume of Andrew’s unstoppable enthusiasm.
And Andrew’s developing concept of a GeoStack is quite useful. I’ve thought of it as an ecosystem of tools, data, and protocols. Whatever you call it, the pieces are starting to fit together.
OpenStreetMap is only given a short mention, since in itself it could be the subject of a Short Cut. Now there’s an idea that might just be happening in the next couple months
I’ve meant to dig into Yahoo’s new support of GeoRSS since the announcement in September.
Annotations purely in code denies other developers and the entire Geospatial Web of that data. For instance, Housing Maps put work into geolocating Craigslist housing ads, freeing and transforming that data, but if someone else wants to build on that, say combine Housing Maps with Chicago Crime, they can’t leverage any of that work and have to start from scratch, building screenscrapers, etc. GeoRSS is designed to fully liberate data.
Yahoo has supported GeoRSS since the beginning of their API, and now giving developers the ability to export their maps into GeoRSS is a great step at encouraging more sharing. However it could go farther. The developer must actively export, and the exported data is not available in a subscription compatible interface. True, it would be much more complex on Yahoo’s part to provide GeoRSS feeds for all of their API uses. And the developer should have some choice in the matter. But by default, we should be sharing, just like by default RSS feeds are produced for weblogs.
The Yahoo polylines are specified using <geo:line>, which was my unofficial extension to the W3C Geo namespace. Now GeoRSS.org has official support for more geometries .. lines, polygons, and boxes. Perhaps this was partially my fault, since I hadn’t updated the worldKit documentation on GeoRSS and polygons with the work of GeoRSS .. until today, where GeoRSS Simple and GML are the recommended encodings (though every other format at there is still supported).
It would be great to see Yahoo Maps update to GeoRSS.org as well. Other parts of Yahoo, like flickr, are now publishing GeoRSS Simple. And I think there’s enough in GeoRSS to do away with the need for the extra ymap namespace.
So some critical feedback. Still good stuff. Thanks ever to Yahoo for supporting GeoRSS.
And on December 28th in Brighton, I’m speaking at the Sussex Geek Dinner, which is free food and me talking about OpenStreetMap, in some technical detail and focus on progress in Brighton. Probably won’t need any more free food after Christmas in Sweden but this will be a good time in the quiet inter-holiday period.
We will soon be launching OpenStreetMap with Yahoo Maps. That means tracing over their aerial imagery, for extremely quick production of free and open maps. Steve has the details.
This is extremely cool.
Most importantly the map gets better and better. Partnerships like these help accelerate OpenStreetMap, and signal even more big things to come.