[x3d-public] Please desupport @geoSystem "N" for Northern Hemisphere in X3dToJson.xslt

[John Carlson]

I have looked at JSON schema that Roy painstaking created, which should be
found in the specifications folder for “N”. I admit that I did not look for
‘N’ or "N" or any other way to create an SFString with N in it.
I basically trusted Roy.

I believe there is also only one occurrence of “S” in the JSON schema.

I’m fairly sure I only modified the notes I added to Mantis.

I verified that there were as many cases of the MFString in Squaw before
and after local susbstitution.   I did not modify any specifications.

You may choose to use or not use the script provided.

This was targeted at non-4.0 examples, so changes in 4.0 should not affect
it.   We’ve got to validate old versions as well.

On Fri, Apr 9, 2021 at 10:45 AM Don Brutzman <brutzman at nps.edu> wrote:

> Thanks for the close review.
>
> Let's travel back to the other end of the playing field please.
>
> For issues like this, we must start at the beginning and work forward.
>
> a. specification: X3D4 Committee Draft (CD)
>     Geospatial Component
>
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD/Part01/components/geospatial.html
>
> b. Examples, both provided and new
>
>     X3D Example Archives: Basic, Geospatial (239 X3D Models)
>     https://www.web3d.org/x3d/content/examples/Basic/Geospatial/index.html
>
> c. Validation
>
> d. Corresponding tool support
>
> So let's fully understand the issue, and how it is implemented in
> practice, before fiddling with tools.
>
> Wondering, are you thinking that "N" is illegal in every case?  Which
> geoSystem: GD, UTM, GC, WM?
>
>
> On 4/9/2021 4:27 AM, John Carlson wrote:
> >
> >
> > Please desupport @geoSystem "N" for Northern Hemisphere in X3dToJson.xslt
> >
> > For example, there are few "N"'s in the specifications folder on
> > sourceforge.
> >
> > There are MANY "S"'s.
> >
> > The best way I know how to fix the 90 some "Squaw" JSON examples is by
> > filtering it in X3dToJson.xslt.
> >
> > You may wish to add this to Tidy config though.
> >
> > Ideally, the originals would be changed with Tidy, if not,
> > X3dToJson.xslt should work.
> >
> > Once this Mantis issue is resolved, we can change X3dToJson.xslt back.
> >
> >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.web3d.org%2Fmember-only%2Fmantis%2Fview.php%3Fid%3D938&data=04%7C01%7Cbrutzman%40nps.edu%7Cbee324aeb5384eeaf06708d8fb4a9d6c%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637535645209852051%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=01tDPKavD3fxwmEvjZzuyyaI3e4%2FsViaq5jzXzvDRLg%3D&reserved=0
> >
> > I can change the X3D JSON schema, but it's changing the hard-coded
> > value, so it will be for all versions, unless I add a conditional.
> >
> > So there should be some discussion as to which versions we are adding
> > "N" for, if we are adding "N" to the schema.
> >
> > Adding this message to Mantis.
> >
> > I may make a local copy of X3dToJson.xslt if not addressed.  It's been 5
> > years!
> >
> > John
> >
>
> all the best, Don
> --
> Don Brutzman  Naval Postgraduate School, Code USW/Br
> brutzman at nps.edu
> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
> X3D graphics, virtual worlds, navy robotics
> http://faculty.nps.edu/brutzman
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20210409/e7539235/attachment-0001.html>