expand/format parameters should not be allowed in CCRS

[Dimitar Misev]

Using expand or format parameters in the inner CRS URLs of a compound CRS URL should throw an exception.

[abeccati]

Milestone 9.0-beta1 deleted

[Bang Pham Huu]

I think there is a exclusive problem if "expand" parameter is not allowed in compound CRS as you also want to add "expand=full" to get the full resolved CRS in here ​http://rasdaman.org/ticket/1106.

[Dimitar Misev]

But these are not expanded by default anyway, check ​http://localhost:8080/def/crs-compound?1=http://localhost:8080/def/crs/EPSG/0/4326&2=http://localhost:8080/def/crs/EPSG/0/4327 for example.

If I add an expand parameter to some single CRS, e.g. ​http://localhost:8080/def/crs-compound?1=http://localhost:8080/def/crs/EPSG/0/4326?expand=full&2=http://localhost:8080/def/crs/EPSG/0/4327 it has no effect and is simply put in the componentReferenceSystem:

<?xml version="1.0" encoding="ISO-8859-1"?>
<CompoundCRS xmlns:gml='http://www.opengis.net/gml/3.2'
   xmlns:epsg='urn:x-ogp:spec:schema-xsd:EPSG:0.1:dataset'
   xmlns:xlink='http://www.w3.org/1999/xlink'
   gml:id='crs' xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmd="http://www.isotc211.org/2005/gmd">
   <metaDataProperty>
      <epsg:CommonMetaData>
         <epsg:type>compound</epsg:type>
      </epsg:CommonMetaData>
   </metaDataProperty>
   <scope>not known</scope>
   <identifier codeSpace='OGC'>http://localhost:8080/def/crs-compound?1=http://localhost:8080/def/crs/EPSG/0/4326?expand=full%262=http://localhost:8080/def/crs/EPSG/0/4327</identifier>
   <name>geographic3D to geographic2D / WGS 84 (geographic 3D)</name>
   <componentReferenceSystem xlink:href='http://localhost:8080/def/crs/EPSG/0/4326?expand=full'/>
   <componentReferenceSystem xlink:href='http://localhost:8080/def/crs/EPSG/0/4327/'/>
</CompoundCRS>

Please check if this is a valid definition btw.

[Dimitar Misev]

Replying to dmisev:

Please check if this is a valid definition btw.

This is a low priority ticket and actually I'm not sure if it's necessary at all. But the validity of the compound CRS definition should be checked.

[Bang Pham Huu]

Replying to dmisev:

Replying to dmisev:

Please check if this is a valid definition btw.

This is a low priority ticket and actually I'm not sure if it's necessary at all. But the validity of the compound CRS definition should be checked.

high to me and I think one can not use Rasdaman but when SECORE was deployed publicly then it is another problem and I'm interested in to check valid.

[Dimitar Misev]

I mean it's low prio regarding the original intention of the ticket, it's not so critical if no exception is thrown. The priority is suitably minor, there are more important bugs.

Using expand or format parameters in the inner CRS URLs of a compound CRS URL should throw an exception.

[Bang Pham Huu]

Patch was accepted, I will close this ticket.