[x3d-public] Invalid geoSystem values in X3D Resources Basic Geospatial examples.

[Andreas Plesch]

http://www.web3d.org/documents/specifications/19775-1/V3.2/Part01/components/geodata.html#Specifyingaspatialreference

lists the supported strings for the geoSystem MFString field.

The prose choosing 'supported' over 'legal' or 'conforming' could be taken
to mean that other than listed strings may be allowed to be supported as
well by some browsers.

However, previous discussions indicate that schemas are not sufficiently
expressive to describe unknown but conforming string values.

One resolution was to explicitly allow 'N' in upcoming X3D version, and
perhaps silently allow it for 3.3.

Outside of X3D UTM zones often have the N hemisphere identifier to avoid
ambiguity.

Andreas




Date: Sat, 12 May 2018 19:54:17 -0400
> From: John Carlson <yottzumm at gmail.com>
> To: Don Brutzman <brutzman at nps.edu>,  X3D Graphics public mailing list
>         <x3d-public at web3d.org>
> Subject: [x3d-public] Invalid geoSystem values in X3D Resources Basic
>         Geospatial examples.
> Message-ID: <5af77ea8.1c69fb81.7da1f.13e3 at mx.google.com>
> Content-Type: text/plain; charset="utf-8"
>
> Don, These files contain "N" in geoSystem, which I believe is not valid,
> and should be removed (default is Northern Hemisphere,  in the standard, I
> believe. "S" can be specified?not in this case).
>
> Is there a tool which hasn?t been changed which is
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180513/7425e7a7/attachment.html>