All the emerging standards for simple markup and syndication of location are Earth-centric (and sometimes just US/North American-centric). Granted, most people are probably only interested in locations that they can actually go to anytime soon.
However, with the increasing number of interplanetary rovers, observations of moons, and perhaps future excursions, it is still useful to define how to properly handle these other reference frames. Luna and Mars are two suggested Microformats that are starting the discussion on how one might mark locations on the two bodies. Additionally, the OGC is working now on determining standards for scientists and developers to publish and share data sources of planets, moons, asteroids, comets, 'oh my'.
To produce the locations for the map, I put up a Space Blog, using WordPress and a slightly modified GeoPress to publish Mars lander locations and landing dates. I altered the published Microformats produced by GeoPress to make the class "geo mars" as a suggested way to markup Mars coordinates. The published GeoRSS feeds from the Space Blog then produce the locations and layers automatically on the OpenLayers Mars Map.
To Do: CRS and You
So this is all very neat, and in the end, really easy to setup. However, this is just a demonstration and in no way should be construed as "the way to do it". Specifically, there are these questions left unanswered:
- How to define the Microformat and GeoRSS for non-Earth (and non-WGS84) reference frames
- How to define the Microformats and GeoRSS/Geonames location for non-Earth locations (like "Ares Vallis")
- More sources for interplanetary map servers
- Ways to syndicate, and subscribe to, specific bodies
- Support for publishing, consuming, and drawing lines - in order to plot out mission profiles
- Support for publishing, consuming, and drawing areas - in order to plot out mission profiles, landing sites, and expected areas of "mission failures"
I'm sure there are more issues, so please speak up. You know who you space geeks are.