Opened 11 years ago
Closed 11 years ago
#539 closed enhancement (fixed)
Add required OGC CRS defs in SECORE for systemtests
Reported by: | Piero Campalani | Owned by: | Piero Campalani |
---|---|---|---|
Priority: | major | Milestone: | 9.0 |
Component: | secore | Version: | development |
Keywords: | user dictionary definitions | Cc: | |
Complexity: | Medium |
Description
Now that SECORE has a separate dictionary for user-defined non-EPSG definitions (./etc/gml/UserDictionary.xml
), it should be filled with some CRS definitions that are currently used for the systemtests, i.e. ANSI date, Temporal and Index.
All the URIs that are contained in such definitions should be parametrized so that the configured public host is showed in the definitions: URNs can be used as a first solution, so that they get translated to URIs uppon db initialization.
This holds for both gml:identifier
elements and target-CRS links.
With this solution the db initialization (some first browser query on the db tree) should be made calling the resolver with its public domain.
Change History (4)
comment:1 by , 11 years ago
Status: | new → accepted |
---|
comment:2 by , 11 years ago
comment:4 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Ticket fixed in changeset:957dee4 and changeset:d71bf75.
Now SECORE includes the following
$ cd ./applications/secore/secore-core/etc $ tar xzvf gml.tar.gz $ sed -n 's/<.*identifier.*>\(\(.*\):crs:\(.*\)\)<\/.*identifier>/\1/p' gml/UserDictionary.xml | tr -d ' ' | sort urn:ogc:def:crs:AUTO:1.3:42001 urn:ogc:def:crs:OGC::AnsiDate urn:ogc:def:crs:OGC::.AnsiDate-template urn:ogc:def:crs:OGC::Index1D urn:ogc:def:crs:OGC::.Index1D-template urn:ogc:def:crs:OGC::Index2D urn:ogc:def:crs:OGC::.Index2D-template urn:ogc:def:crs:OGC::Index3D urn:ogc:def:crs:OGC::.Index3D-template urn:ogc:def:crs:OGC::Temporal urn:ogc:def:crs:OGC::.Temporal-template
Adding the required defs to the local SECORE allows not to refer to Kahlua server for those definitions that are ingested in the new schema and that are necessary for migration and systemtest.
The
global_const.sql
script will insert a parametrized SECORE url which can then be replaced by Petascope with the ("first", see #545) configured SECORE url in thepetascope.properties
file.This is the more convenient solution by now.