Handling of datum and projection in ADIwg mdJSON and ISO about mdjson-schemas HOT 12 CLOSED

I'm not in favor of forcing users to use 19111 to define custom projections. I just don't see that being realistic.
Just so I'm straight, if we add the extra reference system classes to the ISO output, it will fail to validate using the NOAA xsd?

from mdjson-schemas.

I think asking users to create a 19111 record - or even reference it - is a poor choice. This option was a recommendation from NOAA so I thought it should be included. If the user is to create a custom reference system adding it to the EPSG system seems more palpable.

If we did add MD_CRS to the XML (and I tried it) it will fail validation. If we want to do support MD_CRS and associated classes our option would be to extend the XSDs and maintain an ADIwg copy. I'm not feeling warm and fuzzy about that possibility.

I am leaning toward supporting name, epsgNumber, wkt, and no custom reference system unless added to EPSG.

from mdjson-schemas.

I say we stick with the EPSG codes. I registered all of the ARMAP projections with EPSG in 2006. Here's a list of them if anyone cares.. http://armap.org/Projections.aspx Alaska Albers and web mercator are most folks will use.

from mdjson-schemas.

I agree with the recommendation.

On Thu, Aug 28, 2014 at 4:50 PM, stansmith907 [email protected]
wrote:

I think asking users to create a 19111 record - or even reference it - is
a poor choice. This option was a recommendation from NOAA so I thought it
should be included. If the user is to create a custom reference system
adding it to the EPSG system seems more palpable.

If we did add MD_CRS to the XML (and I tried it) it will fail validation.
If we want to do support MD_CRS and associated classes our option would be
to extend the XSDs and maintain an ADIwg copy. I'm not feeling warm and
fuzzy about that possibility.

I am leaning toward supporting name, epsgNumber, wkt, and no custom
reference system unless added to EPSG.

—
Reply to this email directly or view it on GitHub
#19 (comment)
.

from mdjson-schemas.

I think we need to talk with some more folks about this. I'm not sure why NOAA's not supporting this, but it's a significant departure from CSDGM. I'm not sure how this would impact older data sets that may be using weird projections.

On the other hand, I guess if we're not planning to translate custom projections to ISO, we can add that option later if there's a demonstrated need.

from mdjson-schemas.

Template, example, reader, and writer are updated with spatialDatum changed to spatialReferenceSystem as follows ...

"spatialReferenceSystem": {
    "name": [" "],
    "epsgNumber": [0],
    "wkt": [" "]
}

... resulting in version number increase to 0.7.0.

Changes are pushed to GitHub dev and master.

from mdjson-schemas.

FYI,

The WKT double quotes need to be escaped in the JSON:

      "spatialReferenceSystem":{
        "name":[
          "Alaska State Plane Zone 4",
          "UTM Zone 9"
        ],
        "epsgNumber":[
          102634,
          32609
        ],
        "wkt":[
          "PROJCS[\"NAD_1983_StatePlane_Alaska_4_FIPS_5004_Feet\",GEOGCS[\"GCS_North_American_1983\",DATUM[\"North_American_Datum_1983\",SPHEROID[\"GRS_1980\",6378137,298.257222101]],PRIMEM[\"Greenwich\",0],UNIT[\"Degree\",0.017453292519943295]],PROJECTION[\"Transverse_Mercator\"],PARAMETER[\"False_Easting\",1640416.666666667],PARAMETER[\"False_Northing\",0],PARAMETER[\"Central_Meridian\",-150],PARAMETER[\"Scale_Factor\",0.9999],PARAMETER[\"Latitude_Of_Origin\",54],UNIT[\"Foot_US\",0.30480060960121924],AUTHORITY[\"EPSG\",\"102634\"]]",
          "PROJCS[\"WGS 84 / UTM zone 9N\",GEOGCS[\"WGS 84\",DATUM[\"WGS_1984\",SPHEROID[\"WGS 84\",6378137,298.257223563,AUTHORITY[\"EPSG\",\"7030\"]],AUTHORITY[\"EPSG\",\"6326\"]],PRIMEM[\"Greenwich\",0,AUTHORITY[\"EPSG\",\"8901\"]],UNIT[\"degree\",0.01745329251994328,AUTHORITY[\"EPSG\",\"9122\"]],AUTHORITY[\"EPSG\",\"4326\"]],UNIT[\"metre\",1,AUTHORITY[\"EPSG\",\"9001\"]],PROJECTION[\"Transverse_Mercator\"],PARAMETER[\"latitude_of_origin\",0],PARAMETER[\"central_meridian\",-129],PARAMETER[\"scale_factor\",0.9996],PARAMETER[\"false_easting\",500000],PARAMETER[\"false_northing\",0],AUTHORITY[\"EPSG\",\"32609\"],AXIS[\"Easting\",EAST],AXIS[\"Northing\",NORTH]]"
        ]
      },

from mdjson-schemas.

I changed the double-quotes to single in my example. Was that a bad idea?

from mdjson-schemas.

All the examples I've seen of WKT srs defs use double quotes. Although, I'm not sure how much real impact the change to single quotes would have...

from mdjson-schemas.

Gem published. Close this issue?

from mdjson-schemas.

json-schema Dependency is listed as >=0. Didn't we have a few changes that would bump up the version? Do we need to fork our own version for the chop?

from mdjson-schemas.

Use ESPG.

from mdjson-schemas.