[OSGeo-Standards] Fwd: Geometry encoding in JSON

[Volker Mische]

Hi all,

resending this email, as I'm subscribed with different email addresses
to the mailing lists.

Cheers,
  Volker

-------- Original Message --------
Subject: Geometry encoding in JSON
Date: Tue, 31 Jul 2012 12:16:45 +0200
From: Volker Mische <volker at couchbase.com>
To: requests at lists.opengeospatial.org
CC: standards at lists.osgeo.org

PART A


1. Evaluator:
        Volker Mische, volker at couchbase.com

2. Submission:
        GeoServices REST API 12-054


PART B


1. Requirement:
        General

2. Implementation Specification Section number:
        General - Sections 9. Geometry information

3. Criticality:
        Major

4. Comments/justifications for changes:

The current draft uses its own way to encode geometries as JSON. Though
there is an already existing specification (which is not an OGC
standard) which is called GeoJSON [1]. It already provides an encoding
for the geometry types (Multi-)Point, (Multi-)LineString,(Multi-)Polygon
and Geometry Collections.

It is already supported by a huge number of projects that implement OGC
standards. To name a few: PostGIS, GeoServer, OpenLayers.

Hence I propose that GeoServices REST API uses the existing widely used
GeoJSON encoding, rather than inventing it's own one.

[1] http://geojson.org/