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

Work on the CRS sections #1

Merged
merged 1 commit into from
May 15, 2013
Merged

Work on the CRS sections #1

merged 1 commit into from
May 15, 2013

Conversation

sgillies
Copy link
Contributor

My text promotes the practice of long, lat coords using the default
CRS (which is the same as with KML) over the practice of using
projected coordinates or, worst of all, lat/lng coordinates.

My text promotes the practice of long, lat coords using the default
CRS (which is the same as with KML) over the practice of using
projected coordinates or, worst of all, lat/lng coordinates.
two GeoJSON crs** CRS84 (an axis-flipped WGS84) and CRSGoogle
(EPGS:3857). So is this really WGS84 mentioned as default?
degrees. In an array of coordinate values, longitude is first and is
followed by latitude.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The first of my notes goes away. Good!

@tschaub tschaub mentioned this pull request May 15, 2013
(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.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a note here about what the default coordinate system is as a crsURN? AFAIK urn:ogc:def:crs:OGC:1.3:CRS84 is WGS84/longitude-latitude (http://portal.opengeospatial.org/files/?artifact_id=8814)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants