RFC-001
From GeoJSON
Revision as of 12:52, 12 April 2007 by AllanDoyle (Talk | contribs) (→Specification: Changed definition of coordinates so Point has x,y or x,y,z notation.)
Inspired in part by http://trac.gispython.org/projects/PCL/wiki/PythonFeatureProtocol (or maybe even a complete copy )
Contents
Definitions
- The terms object, name, value, array, and number are defined at http://json.org/
- The terms may, should, and must are defined at http://www.ietf.org/rfc/rfc2119.txt
Specification
- A feature is an object.
- A feature may have a name/value pair whose name is 'geometry' and whose value conforms to rule 3. (A feature may have any other name/value pairs, without restriction.)
- The value of a geometry must itself be an object with the following name/value pairs:
- 'type' - [Point | Line | Polygon | Box]
- 'coordinates' - A coordinate consists of an array of two or three number values representing x, y, and optionally z. In the case of a Point, the value of coordinates is an array consisting of a single coordinate (i.e. an array of two or three number values). In all other cases, an array of coordinates as in Point, restricted as follows:
- A Line must have at least two coordinates.
- A Polygon must have at least three coordinates.
- A Box must have exactly two coordinates.
- 'crs' - an optional string specifying a coordinate reference system of the coordinates. If not present, WGS84 is implied and coordinates represent decimal degrees ordered as "longitude, latitude [,elevation]" and z is expressed as meters above mean sea level per WGS84. If present, the value of crs is to be interpreted as in PROJ4's EPSG tables and the values of the coordinates are to be interpreted accordingly.
- A feature should have a name/value pair whose name is 'id' and whose value can be uniquely interpreted by the source of the GeoJSON string, generally identifying this GeoJSON object's resource.
- A feature should have a name/value pair whose name is 'properties' and whose value is an object that has meaning within a specific community of interest.
- A feature having multiple geometries should have an array of geometries contained within a properties object (see 5) which is called 'geometries' and whose values are as described in 3.
Examples
adapted from Python example at GISPython: Feature Protocol
{ "id": "1", "properties": { "title": "Feature 1", "summary": "The first feature", "link": "http:example.org/features/1", } "geometry": { "type": "Point", "coordinates": [-105.8, 40.05], } }
Authors
- Allan Doyle
- Sean Gillies