Custom Query (2765 matches)

While adding a CRS to petascopedb a misleading error is printed in console since the import scripts do not check the existence of the URI in ps9_crs table before insertion.

Now that Postgresql 9 is tested (see #431), a ​WHERE NOT EXISTS clause can be added.

When uploading a CRS definition of a parametrized CRS, a gml:description element is not allowed, whereas the schema definition permits it ([0..1] multiplicity in the root gml:AbstractGML)

E.g.:

<ParameterizedCRS xmlns="http://www.opengis.net/CRS-NTS/1.0" xmlns:epsg="urn:x-ogp:spec:schema-xsd:EPSG:1.0:dataset" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" gml:id="param-ansi-date-crs">
  <description>Parametrized temporal CRS of days elapsed from 1-Jan-1601 (00h00 UTC).</description>
  <gml:identifier codeSpace="http://www.ietf.org/rfc/rfc3986">http://localhost:8090/def/crs/OGC/0/AnsiDate</gml:identifier>
  <parameters>
...

Now gives:

<ows:Exception exceptionCode="XmlNotValid" locator="description">
<ows:ExceptionText>
Unexpected element name description, expected one of parameters, identifier, or targetCRS
</ows:ExceptionText>
</ows:Exception>

newline (\n, 0x0a) should be put at the end of a CSV encoded WCPS response.

By default, vim automatically adds it on save, so systemtests can become unreliable when oracles are manually edited.

This currently inhibits multipoint WCPS tests to pass.

$ echo `pwd`
/home/rasdaman/rasdaman/systemtest/testcases_services/test_wcps
$ hexdump -C output/62-subset-all-dims-multipoint.test.out | tail -2
00000800  2c 32 35 35 2c 32 35 35  7d                       |,255,255}|
00000809
$ hexdump -C oracle/62-subset-all-dims-multipoint.test.oracle | tail -2
00000800  2c 32 35 35 2c 32 35 35  7d 0a                    |,255,255}.|
0000080a
$ hexdump -C oracle/01-just_trim.test.oracle | tail -2
00000130  49 45 4e 44 ae 42 60 82                           |IEND.B`.|
00000138