Opened 4 years ago

Last modified 4 months ago

#364 assigned task

expand parameter should be aplicable to ParameterizedCRS

Reported by: dmisev Owned by: dmisev
Priority: minor Milestone: Future
Component: secore Version: 8.4
Keywords: Cc: pcampalani
Complexity: Medium


The expand parameter in SECORE should control whether to resolve a parameterized CRS url. With value none the original CRS definition is returned.


Change History (8)

comment:1 Changed 4 years ago by pcampalani

NOTE: It should replace the flatten parameter.

comment:2 Changed 4 years ago by dmisev

  • Milestone changed from 8.5 to 9.0-alpha1

comment:3 Changed 4 years ago by abeccati

  • Milestone changed from 9.0-beta1 to 9.0

Milestone 9.0-beta1 deleted

comment:4 Changed 22 months ago by dmisev

  • Owner changed from dmisev to bphamhuu
  • Status changed from new to assigned

comment:5 Changed 21 months ago by bphamhuu

May I ask a question, I guess that parameterizedCRS mean user can add "parameters" to URL with key=value, and Dimitar wants when access URL with ?expand=none, it will return the original definition like with /browse.jsp.

<ParameterizedCRS xmlns="" xmlns:epsg="urn:x-ogp:spec:schema-xsd:EPSG:1.0:dataset" xmlns:gml="" xmlns:xlink="" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" gml:id="param-index1d-crs">
  <gml:description>Parametrized 1D CRS with indexed coordinates.</gml:description>
  <gml:identifier codeSpace=""></gml:identifier>
  <gml:name>Parametrized Index 1D CRS</gml:name>
  <gml:remarks>Initial version (0.1)</gml:remarks>
    <parameter name="axis-label">
  <targetCRS xlink:href=""/>

However, I feel expand=none is "confusing" because with expand=0 that means no resolve to any xlink:href. For example a paramerterizedCRS like above when resolve with expand=0 will return only the imported CRS inside it (which is ImageCRS "index1d-crs"))

<ImageCRS id="index1d-crs"><description>CRS for 1D index-domain referenced axis.</description><identifier codeSpace=""></identifier><name>1D Index CRS</name><remarks>Initial version (0.1)</remarks><scope>not known</scope><cartesianCS><CartesianCS xlink:href=""/></cartesianCS><imageDatum><ImageDatum xlink:href=""/></imageDatum></ImageCRS>

So I think, a parameter to return the original definition of CRS in XML (same as in browse.jsp) like "?getDef" is better.

comment:6 Changed 21 months ago by dmisev

  • Owner changed from bphamhuu to dmisev

Let's ignore this one, because we need to decide the parameter first and this needs to be in line with OGC.

comment:7 Changed 21 months ago by bphamhuu

yes, it is good to know. Thanks.

comment:8 Changed 4 months ago by dmisev

  • Milestone changed from 9.0.x to Future
Note: See TracTickets for help on using tickets.