Print

Print


The draft working group had some discussion whether coordinates should be specified as arrays, or as objects with named properties, e.g.

[ 1, 2, 3 ] vs. { "x": 1, "y": 2, "z": 3 }

I propose we stick with the array format which has been used so far, as that matches the GeoJSON format.

Note that the array format doesn't reveal which coordinate reference is used, whereas { "x": 1, "y": 2, "z": 3 } would look different from { "lat": 1, "lon": 2, "elev": 3 }, and make code easier to read.

I suggest good coders could use objects with properties throughout their code, but translate these to WebLVC format when messages are sent or received. You could even write web applications using a strongly typed language such as TypeScript. Application decisions can be different from protocol decisions.

Comments?

########################################################################

To unsubscribe from the SAC-PDG-WEBLVC list, click the following link:
https://discussions.sisostds.org/index.htm?SUBED1=SAC-PDG-WEBLVC&A=1