SECORE distinct notation to retrieve raw definition of a parametrized CRS
|Reported by:||pcampalani||Owned by:||mrusu|
|Keywords:||parametrized definitions||Cc:||dmisev, mrusu, pbaumann, abeccati|
Opening this ticket since I believe that parametrized CRSs should still return the target CRS when e.g. no parameters are set by the user and all the parameters are defined with a default value.
This way the same URI can be used for both template and customized CRS definition.
E.g. Having a template CRS for ANSI dates "http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0.1/ANSI_Date-template", this can be targeted by a parametrized CRS, say "http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0.1/ANSI_Date", offering the chance to customize the axis label from t to something else.
For instance, `"http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0.1/ANSI_Date?t=%22day%22"' would set the axis label to "day".
Now, by calling the parametrized CRS with no parameters SECORE returns the gml:ParametrizedCRS definition, whereas it would be best to return the ANSI_Date-template definition with default t label, so that the URI "http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0.1/ANSI_Date-template" must no be disclosed, avoiding confusion to the user.
Since still it must be possible to retrieve the raw definition (with XPaths, etc.) of the gml:ParametrizedCRS, we might think of a specific notation (just like with compouninds, or equality tests), as Dimitar suggested.
Change History (9)
comment:1 Changed 4 years ago by pcampalani
- Summary changed from SECORE distinct notation to retrieve real source of a parametrized CRS to SECORE distinct notation to retrieve raw definition of a parametrized CRS
comment:7 follow-up: ↓ 8 Changed 4 years ago by dmisev
- Resolution set to fixed
- Status changed from new to closed