#1171 closed defect (fixed)

WMS 1.3 should create a full extent WGS84 for CRSs that cannot be translated otherwise

Reported by: mdumitru Owned by: mdumitru
Priority: major Milestone: 10.0
Component: petascope Version: development
Keywords: Cc:
Complexity: Medium

Description

The WMS 1.3 standard requires that each layer should present the coordinates in a WGS84 coordinates approximation that can be used by search engines / metadata harvesters / etc (but not by clients displaying the data) that could not parse other CRS coordinates.

However, rasdaman supports all kind of CRSs through SECORE, some (like the mars or lunar ones) that do not have any semantically valid translation (different planets, WGS84 does not apply). For this types of CRSs we should just return the full extent instead of throwing an error on ingestion.

Change History (3)

comment:1 Changed 16 months ago by bphamhuu

@Alex: there is a problem in the function which converts other CRS to SECORE 4326 as you are using opengis to get definition (I'm not sure what you did here, but in case, I define a CRS in secore like http://localhost:8080/def/crs/PS/0/Bang" and use it in recipe to import WMS", this will throw error due to cannot find the CRS definition from opengis).

I think this is the real problem, that is why Ramiro cannot import because of his CRS definition is not available in opengis also.

http://212.201.45.10:8080/def/crs/PS/0/Mars-equirectangular

Error

(org.opengis.referencing.NoSuchAuthorityCodeException)
org.opengis.referencing.NoSuchAuthorityCodeException: Authority "PS" is unknown or
doesn't match the supplied hints. Maybe it is defined in an unreachable JAR file?

comment:2 Changed 16 months ago by bphamhuu

you also has pointed out the problem correctly, can I do this ticket? thanks.

comment:3 Changed 15 months ago by bphamhuu

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

the patch was accepted, close here, thanks.

Note: See TracTickets for help on using tickets.