Joe Gregorio notes in The end of the AtomPub WG that the Atom Publishing Format and Protocol WG (atompub) in the Application Area has concluded. Developers can go into full programming mode knowing that the encodings and interfaces aren’t changing any time soon. Thanks AtomPub WG for a great standard.
I was working on a Yahoo Pipe last night, and I noticed that Pipes will automatically figure out if you have created a geospatial pipe, and show it on a map without you having to do anything! And to top it off, you can get KML output of your pipe! Now if they drop the old-fashioned W3C Geo point-only format and support real GeoRSS they’ll really have something (hint, hint).
What this means is that you can create and export KML content from Google, Microsoft and Yahoo! now. The mind bubbles at the possibilities…
By the way, if you’re actually interested the content of my Cambridge, MA Happenings pipe and not just the technology, you should know that there are a lot of good events that aren’t getting properly geo-located, so read the feed, not just the map.
I’d like to send out a welcome to one of OGC’s newest members, Microsoft. The SQL Server team is readying spatial support in the database with SQL Server 2008, which will have lot’s of OGC goodness built-in, like Well-Known Text and GML data encodings, and Simple Features for SQL access.
The Virtual Earth team has long supported GeoRSS in their Collections, and KML import and export is the newest OGC-related feature in the Virtual Earth/Live Maps product. Check out Steve Lombardi’s excellent blog for more info. MapCruncher is another very cool offering in the online-geo space that allows “regular” folks to upload scanned maps and perform some basic image rectification so that they can be overlaid on orthophotos.
I can’t wait to see what people do with all these features, and hope to see some cool cross-product mashups with all the content in Google, Microsoft and Yahoo geo-services.
In the OGC Mass Market Geo Working Group meeting yesterday, I presented the preliminary findings of the group brainstorming about the future of KML in the OWS-5 testbed. Most of what was discussed isn’t ready for prime time, so I’ll wait to talk about for a few months, but one critical point that everyone should understand is that KML is, always has been, and will continue to be about mapping/geospatial visualization. Don’t use KML as a data storage or archival format. That’s what GML is for. Yes, KML has some geographic coordinates in there, but KML’s ability to act like a GIS format–attaching other data properties to the geography, typing them, and putting metadata on it all–is weak.
The right way to think about the geographic information “workflow” is to have a spatial database that serves up data to the Web via the Web Feature Service (WFS) API in some flavor of GML. Soon, OGC will specify how that WFS should serve up KML using the existing WFS API plus some extra information to describe the transformation–probably using SLD. The authoritative data will still reside in the spatial database. The KML will just represent one cartographic view of the data at a particular point in time.
I’ve followed Jon Udell’s work for a long time. I’ve found him to have some of the most interesting, original, and clearly presented thoughts on information technology over the years. I’m giving him a blog shoutout because recently he’s been delving into topics near and dear to my own heart. Namely geo web services, exploratory spatial data analysis, urban planning, and GeoRSS. If you’re like me, you’ll want to check out his blog. Especially these entries: