Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removing crsURN #6

Merged
merged 1 commit into from
Jul 11, 2013
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion CHANGES.txt
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
20130516 - removed crsURN
20130402 - reduced crsRef to single label with domain RFC 5165 like URN, thus renamed it to crsURN
20130430 - moved repo to GeoJSONWG organization at https://github.com/GeoJSONWG/draft-geojson
20130428 - typos corrected, editorial changes throughout the document and several notes partly explaining thes or requesting further changes or additions. Correction of inconsistent may in GeoJSON Object first list item into MUST, merge with second listitem and provision of js and bib folders
20130427 - initial draft
20130427 - initial draft
57 changes: 7 additions & 50 deletions middle.mkd
Original file line number Diff line number Diff line change
Expand Up @@ -190,10 +190,6 @@ referred to as the GeoJSON object in this document.
value - additional rules apply, then these are stated in the
following sections where each type is further defined.

* A GeoJSON object MAY have an optional "crsURN" member. If it is present,
the value of it MUST be a valid coordinate reference system reference
(see "[3. Coordinate Reference System (CRS) Reference](rfc.section.3)").

* A GeoJSON object MAY have a "bbox" member. If it is present,
the value of it MUST be a bounding box array (see
"4. Bounding Box").
Expand Down Expand Up @@ -222,18 +218,14 @@ member of a geometry object is composed of either:
* or a multidimensional array of positions (MultiPolygon).

A position is represented by an array of numbers. There MUST be two or
more elements. In general the first two elements will be World Geodetic
System (WGS 84) longitude and latitude, precisely in that order, and
a third (optionally) will be altitude in meters.
more elements. The first two elements will be World Geodetic System 1984
(WGS 84) longitude and latitude, precisely in that order, and
a third (optional element) will be altitude in meters.

Any number of additional elements are allowed -- interpretation and
meaning of additional elements is beyond the scope of this
specification.

GeoJSON data producers MAY indicate a different sense of the position
elements by including a "crsURN" object in the position's context. See
the Coordinate Reference System section below for details.

Examples of positions and geometries are provided in "Appendix A.
Geometry Examples".

Expand Down Expand Up @@ -316,42 +308,10 @@ element in the array is a feature object as defined above.

# Coordinate Reference System (CRS)

The coordinate reference system of a GeoJSON object and the sense of
coordinate order is determined by the value of its "crsURN" member
(referred to as the CRS reference below). If an object has no crsURN
member, then its parent or grandparent object's crsURN member may be
acquired. If no crsURN member can be so acquired, the default CRS shall
apply to the GeoJSON object.

* The default CRS is a geographic coordinate reference system, using
the WGS84 datum, and with longitude and latitude units of decimal
degrees. In an array of coordinate values, longitude is first and is
followed by latitude.

* The value of a member named "crsURN" must be a string (referred to
as the CRS reference below) or JSON null. If the value of "crsURN" is
null, no CRS can be assumed. Note-sdrees: FIXME or default CRS as
when crsURN member is left out? It is optional anyway.

* The crsURN member SHOULD be on the top-level GeoJSON object in the
following canonical hierarchical ordering, i.e. if present on a
feature collection, else if present on a feature, else on a geometry
and MUST NOT be repeated or overridden on children or
grandchildren of the object.

Note-sdrees: The name has been changed from crs to crsURN to not
irritate consumers that expect the crs object as of version 1.0 in the
community spec.

If present the CRS reference MUST indicate a coordinate reference
system by name. In this case, the value of it MUST be a string
identifying a coordinate reference system. OGC CRS URNs such as
"urn:ogc:def:crs:OGC:1.3:CRS84" SHALL be preferred over legacy
identifiers such as "EPSG:4326":

"crsURN": "urn:ogc:def:crs:OGC:1.3:CRS84"

For the format of a valid URN cf. [RFC5165].
The coordinate reference system of all GeoJSON objects is a geographic
coordinate reference system, using the WGS84 datum, and with longitude and
latitude units of decimal degrees. In an array of coordinate values,
longitude is first and is followed by latitude.

# Bounding Box

Expand All @@ -361,9 +321,6 @@ collections. The value of the bbox member MUST be an array of length
2*n where n is the number of dimensions represented in the contained
geometries, with the lowest values for all axes followed by the highest
values. The axes order of a bbox follows the axes order of geometries.
In addition, the coordinate reference system for the bbox is assumed to
match the coordinate reference system of the GeoJSON object of which it
is a member.

Example of a bbox member on a feature:

Expand Down