W3C home > Mailing lists > Public > public-geolocation@w3.org > May 2009

Support for GeoJSON?

From: Richard Barnes <rbarnes@bbn.com>
Date: Mon, 11 May 2009 21:00:35 -0400
Message-ID: <4A08CA33.3050509@bbn.com>
To: public-geolocation <public-geolocation@w3.org>
Hey all,

I just became aware of GeoJSON, a JSON format for location information 
that's compatible with GML:
<http://geojson.org/>
It's already supported by several libs and web apps, including FireEagle 
and, more recently, Google Latitude:
<http://wiki.geojson.org/Users>
<http://googlegeodevelopers.blogspot.com/2009/05/build-on-top-of-your-public-latitude.html>

It seems like re-using this object format would help the W3C API to be 
compatible with the larger space of geolocation applications, ranging 
from the web apps above to full-strength GIS apps.

Now, on the other hand, the current object format is limited to points 
and complexes thereof (lines, polygons, etc.), but I've hacked together 
an extension that supports a better set of shapes that still maps over 
to GML:
<http://geopriv.dreamhosters.com/geojson/geojson-spec.html>
<http://lists.geojson.org/pipermail/geojson-geojson.org/2009-May/000484.html>

I'd like to propose that the Position.coords element be split into two 
elements, one of which is a GeoJSON Geometry object (call it "geometry") 
for the static parts of Position.coords, and the other of which (call it 
"dynamic") which holds the parts related to motion.

interface Position {
   readonly attribute Geometry geometry;
   readonly attribute Dynamic dynamic;
   readonly attribute DOMTimeStamp timestamp;
};

interface Dynamic {
   readonly attribute double heading;
   readonly attribute double speed;
};

(The current static attributies (latitude, longitude, altitude, 
accuracy, altitudeAccuracy) can be mapped to a circle or ellipsoid.)

--Richard
Received on Tuesday, 12 May 2009 01:01:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 August 2009 20:54:10 GMT