[x3d-public] [geospatial] geoSystem UTM value syntax, is N an allowed parameter?
Andreas Plesch
andreasplesch at gmail.com
Thu Jan 28 07:46:16 PST 2016
Hi Don,
loading
http://www.web3d.org/x3d/content/examples/Basic/Geospatial/Squaw.xhtml
x3dom still complains about
ERROR: Unknown GEO system: [UTM Z10 N ]
This error occurs because in
http://www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawCanonical.xml
the GeoLOD nodes such as
<GeoLOD center="4340965.855617 738223.363583 2183.5"
child1Url=""SquawLOD000.x3d" "
http://www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD000.x3d"
"SquawLOD000.wrl" "
http://www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD000.wrl""
geoSystem=""UTM Z10 N"" range="32266.666016">
give a geoSystem field value of "UTM Z10 N" (a single string) instead of
"UTM" "Z10" "N" (multiple strings) . Could this be fixed since now (a basic
implementation of) GeoLOD is available in the developer version of
x3dom-full.js ?
Also, the default GeoViewpoint node could use a
centerOfRotation='4342525.411173 740603.999947 2001.5' field for better
initial navigation in examine mode.
Thanks,
Andreas
On Tue, Jan 26, 2016 at 5:15 AM, Andreas Plesch <andreasplesch at gmail.com>
wrote:
>
> On Jan 26, 2016 3:37 AM, "Don Brutzman" <brutzman at nps.edu> wrote:
> >
> > On 1/25/2016 1:21 PM, Andreas Plesch wrote:
> >>
> >> I just came across the same issue with the Squaw Valley scene.
> >>
> >> The problem is that geoSystem is a MFString but the value of geoSystem
> in the GeoLOD nodes of
> http://www.web3d.org/x3d/content/examples/Basic/Geospatial/Squaw.xhtml
> >> is given as SFString "UTM Z10 N". It should be ' "UTM" "Z10" "N" ' .
> The sublevel x3ds are all correct, in contrast.
> >
> >
> > yes you are quite correct about that, spec examples are very clear:
> >
> >
> > 25.2.3 Specifying a spatial reference frame
> >
> http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/geodata.html#Specifyingaspatialreference
> >
> > first geosystem value in Squaw.x3d is correct, but second is incorrect
> in that scene. have fixed and checked those in.
> >
>
> Thanks. I believe all GeoLOD nodes in Squaw.x3d had this issue. Other Geo
> nodes were OK.
>
>
> http://www.web3d.org/x3d/content/examples/Basic/Geospatial/_pages/page45.html
>
> sofar still shows "UTM Z10 N" values. Will check again.
>
> >> In my implementation of parsing of the geoSystem field for x3dom, I
> just ignore values other than "S" and assume the northern hemisphere.
> Similarly, I ignore all other strings which cannot be mapped to one of the
> values given in spec .
> >
> >
> > that sounds like good practice for an implementation. am hoping we can
> have a tighter definition in spec and QA tools if appropriate. networking
> maxim: "be strict about what you produce, and forgiving about what you
> receive."
> >
> > i fixed X3D-Edit to add quotes, and added a schematron test to look for
> mismatched quotes/spaces in geoSystem. also tuned up the tooltips to note
> that quoting is expected.
> >
> > so anyway, if "N" isn't found in other uses of UTM but "S" is, then we
> should probably forbid "N" rather than allowing it.
>
> The "N" is often found as part of the UTM zone designation in UTM
> coordinates, since it disambiguates from "S". It should be allowed.
> Assuming the northern hemisphere when not explicitly given is convenient
> but not necessarily standard practice. One would always expect a S or N
> appended to the UTM zone number.
>
> Andreas
>
> >
> >>
> >> Date: Sun, 24 Jan 2016 19:27:56 -0800
> >> From: Don Brutzman <brutzman at nps.edu <mailto:brutzman at nps.edu>>
> >> To: X3D Geospatial Working Group <geospatial at web3d.org <mailto:
> geospatial at web3d.org>>
> >>
> >> Subject: [geospatial] geoSystem UTM value syntax, is N an allowed
> >> parameter?
> >> Message-ID: <56A5963C.2070105 at nps.edu <mailto:
> 56A5963C.2070105 at nps.edu>>
> >>
> >> Content-Type: text/plain; charset="utf-8"; format=flowed
> >>
> >> Wondering is the following legal?
> >>
> >> geoSystem='"UTM Z10 N"'
> >>
> >> The spec indicates that S (for South) is optional but doesn't
> mention North.
> >>
> >> 25.2.3 Specifying a spatial reference frame
> >>
> http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/geodata.html#Specifyingaspatialreference
> >>
> >> all the best, Don
> >> --
> >> Don Brutzman Naval Postgraduate School, Code USW/Br
> brutzman at nps.edu <mailto:brutzman at nps.edu>
> >> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA
> +1.831.656.2149 <tel:%2B1.831.656.2149>
> >>
> >> X3D graphics, virtual worlds, navy robotics
> http://faculty.nps.edu/brutzman
> >>
> >>
> >>
> >> ------------------------------
> >>
> >> Subject: Digest Footer
> >>
> >> _______________________________________________
> >> geospatial mailing list
> >> geospatial at web3d.org <mailto:geospatial at web3d.org>
> >>
> >> http://web3d.org/mailman/listinfo/geospatial_web3d.org
> >>
> >>
> >> ------------------------------
> >>
> >> End of geospatial Digest, Vol 11, Issue 14
> >> ******************************************
> >>
> >>
> >>
> >>
> >> --
> >> Andreas Plesch
> >> 39 Barbara Rd.
> >> Waltham, MA 02453
> >>
> >>
> >> _______________________________________________
> >> geospatial mailing list
> >> geospatial at web3d.org
> >> http://web3d.org/mailman/listinfo/geospatial_web3d.org
> >>
> >
> >
> > 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
>
--
Andreas Plesch
39 Barbara Rd.
Waltham, MA 02453
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160128/823a792e/attachment.html>
More information about the x3d-public
mailing list