Petascope Coverage's CRS prefix should depend on configuration from petascope.properties

[Bang Pham Huu]

A coverage which is imported with SECORE configure as localhost:8080/def in petascope.properties.

However, later SECORE is configured as localhost:8081/def and restarts Petascope, it will use a mixed up CRS like this for this coverage

http://localhost:8081/def/crs-compound?
1=http://localhost:8080/def/crs/EPSG/0/32633&
2=http://localhost:8080/def/crs/OGC/0/AnsiDate

with localhost:8080/def cannot access so this will throw an exception in Petascope.

Coverage's crs should be

http://localhost:8081/def/crs-compound?
1=http://localhost:8081/def/crs/EPSG/0/32633&
2=http://localhost:8081/def/crs/OGC/0/AnsiDate