There are some minor things I don't understand.

a) we need orientations as in DIS, GeoJSON doesn't support that, so that rules that out. I should've checked DIS first, sorry. Unless we radically revise the format and separate the Orientation, which I would NOT favour, makes errors more likely. I withdraw my suggestion.

b) your language for Point says: "An array of the form { WorldLocation, Orientation }" ... but the example shows that as a JSON object with properties, did you mean object? Or a length-1 array of that object?

c) for Areal, do you mean an array-of-arrays, e.g. [ [1,2,3], [4,5,6], [7,8,9] ] ?

d) for Linear, do you mean an array of objects, e.g. [ { "WorldLocation": [1,2,3], "Orientation": [4,5,6], ... }, {}, {} ] ?

e) why do we have a property 'count'? I think that's unnecessary (redundant) and just adds more data to transmit, parse. Can we eliminate that?

f) I think we need an example, maybe more description of SegmentStruct, it's not entirely obvious to me.

g) I assume the appearance properties apply to either a point, or an area, but that the same appearance properties could be specified for each object in the array for a Linear type? (assuming I understand that correctly) - if so, does that mean an appearance property on the message would apply if no corresponding appearance property is specified for a linear segment (e.g. message appearance properties work like default values for all the segments)?

Thanks,
Brad

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

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