Opened 11 years ago
Closed 11 years ago
#688 closed defect (fixed)
Wrong usage of tuple and coordinate separator in range set
Reported by: | Piero Campalani | Owned by: | Piero Campalani |
---|---|---|---|
Priority: | critical | Milestone: | 9.0.x |
Component: | petascope | Version: | development |
Keywords: | tuple coordinate separators | Cc: | Dimitar Misev, Peter Baumann |
Complexity: | Trivial |
Description
From GML standard:
gml:CoordinatesType consists of a list of coordinate tuples, with each coordinate tuple separated by the ts or tuple separator (whitespace), and each coordinate in the tuple by the cs or coordinate separator (comma). The gml:tupleList encoding is effectively "band-interleaved".
(gml:CoordinatesType) cs symbol used to separate components within a tuple or coordinate string (default="," a comma) ts symbol used to separate tuples or coordinate strings (default=" " a space
On the other hand, rasdaman
/Petascope uses the comma as tuple separator and the white-space as coordinate separator (within the tuple). In the example of 2 grid points from a 2-band coverage:
<tupleList> 3.11651 0.451686,7.64325 0.618357 \____tuple1____/ \____tuple2____/ \____/ \_____/ \____/ \_____/ c1.1 c1.2 c2.1 c2.2 </tupleList>
To keep backward compatibility with release 9.0 we need to explicitly declare cs
and ts
attributes to overwrite defaults:
<tupleList ts="," cs=" "> 3.11651 0.451686,7.64325 0.618357 </tupleList>
(Correct me if I'm wrong)
Note:
See TracTickets
for help on using tickets.
Fixed in changeset:45e47d6.