Document spatial reference system requirement for extents

[jlblcc]

The Import Extent section should note that any spatial files to be imported must use the EPSG:4326 (WGS 84, World Geodetic System 1984) spatial reference system. For reference, see the GeoJSON spec: https://tools.ietf.org/html/rfc7946#section-4

https://github.com/adiwg/mdEditor-doc/blob/master/reference/edit-window/metadata/extent-panels/features-import.md

[IronRico]

Hello Josh. Looking at the Extent section in the guide, I do see it areas showing requirements for imported files. Rather, it has details for imported file types. The fourth bulleted point notes the GeoJSON files. · GeoJSON (RFC 7946) - a geospatial data interchange format based in JavaScript Object Notation, JSON. o A column name of "id" is assumed to contain the ID of the feature and is saved in an editable field. o A column name of "name" is assumed to contain the name of the feature and is saved in an editable field. o A column name of "description" is assumed to contain a description of the feature and is saved in an editable field. o All other column values are saved in read-only fields. What would be the preferred way to include the EPSG:4326 requirements? I went over and looked at the section 4 area for the GeoJSON details. Would it be best to condense some of that and include it as another bulleted point or instead provide the full unfiltered section as presented on that site? Alternatively, would you place a link to that be preferred?

…

_______________________________________________ *Just to be clear, we are referencing this element, correct?* *4. Coordinate Reference System* The coordinate reference system for all GeoJSON coordinates is a geographic coordinate reference system, using the World Geodetic System 1984 (WGS 84) [WGS84] datum, with longitude and latitude units of decimal degrees. This is equivalent to the coordinate reference system identified by the Open Geospatial Consortium (OGC) URN urn:ogc:def:crs:OGC::CRS84. An OPTIONAL third-position element SHALL be the height in meters above or below the WGS 84 reference ellipsoid. In the absence of elevation values, applications sensitive to height or depth SHOULD interpret positions as being at local ground or sea level. *Note*: the use of alternative coordinate reference systems was specified in [GJ2008], but it has been removed from this version of the specification because the use of different coordinate reference systems -- especially in the manner specified in [GJ2008] – has proven to have interoperability issues. In general, GeoJSON processing software is not expected to have access to coordinate reference system databases or to have network access to coordinate reference system transformation parameters. However, where all involved parties have a prior arrangement, alternative coordinate reference systems can be used without risk of data being misinterpreted. Thanks for your time Josh. Cheers Carlos.P <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Thu, Jun 4, 2020 at 12:40 PM Josh Bradley ***@***.***> wrote: The Import Extent section should note that any spatial files to be imported must use the EPSG:4326 (WGS 84, World Geodetic System 1984) spatial reference system. For reference, see the GeoJSON spec: https://tools.ietf.org/html/rfc7946#section-4 https://github.com/adiwg/mdEditor-doc/blob/master/reference/edit-window/metadata/extent-panels/features-import.md — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#24>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE5QYYH7GBRFTSXD5WFT5H3RU7MCXANCNFSM4NS25ECQ> .

[jlblcc]

Ah, so internally mdJSON uses GeoJSON to store extents. So any of the supported file types is converted to GeoJSON by mdEditor. Therefore, the user must make sure that the files being uploaded are using the 4326 spatial reference system. Something like:

Any imported data should use the World Geodetic System 1984 (WGS 84) [WGS84] coordinate reference system, with longitude and latitude units of decimal degrees, This is equivalent to EPSG:4326 and urn:ogc:def:crs:OGC::CRS84. See https://epsg.io/4326 for more information.

[IronRico]

I am in the process of making the change above. I started from a clear repo without the changes of GitBook version 2 being added.

[jlblcc]

Don't forget to use a hint box to emphasize the text:

{% hint style='info' %}
Important info: this note needs to be highlighted
{% endhint %}

[IronRico]

Got it. I left off the last "%" on there.

[jlblcc]

👍

Also, I'd recommend using a short description/title of the destination rather than "this site".

[IronRico]

How does that look?