Opened 4 years ago

Closed 4 years ago

#677 closed defect (fixed)

Petascope not to rely on a static set of supported naming authorities

Reported by: pcampalani Owned by: pcampalani
Priority: major Milestone: 9.0.x
Component: petascope Version: development
Keywords: supported authorities Cc: dmisev
Complexity: Trivial

Description

Validity of a CRS URI should not rely on a static set of supported authorities (like currently implemented: EPSG, ISO, OGC, AUTO), and neither on the supported authorities returned from the configured resolver (./def/crs/): other authorities might have been deployed on different resolvers, so in the end we either refer to an official document of official CRS naming authorities or to an official set of resolvers.

While thinking of a solution here, I suggest to disable the current constraint, nonetheless to support planetary CRS definitions not provided by the current set of supported authorities.

Change History (2)

comment:1 Changed 4 years ago by pcampalani

  • Status changed from new to accepted

comment:2 Changed 4 years ago by pcampalani

  • Resolution set to fixed
  • Status changed from accepted to closed

Constraint on authorities has been commented out in changeset:0da1d6f.

SECORE users can define their own authorities if they want to provide definitions of CRS not provided by other authorities elsewhere. Providing a valid GML definition to which the URI resolves to is enough. We have a direct application of this within the EarthServer project, where CRSs for planetary objects are being defined under their own non-official authority.

Note: See TracTickets for help on using tickets.