Opened 8 years ago

Closed 8 years ago

#1428 closed defect (fixed)

SECORE_Cannot add new CRS by URN

Reported by: Bang Pham Huu Owned by: Bang Pham Huu
Priority: major Milestone: 9.3
Component: secore Version: development
Keywords: SECORE URN invalid Cc: Dimitar Misev
Complexity: Medium

Description

Current SECORE must use the resolved URN to URI (e.g: ​http://opengis.net/def/crs/EPSG/0/4326 instead of URN: urn:ogc:def:crs:AUTO:1.3:42001) in gml:identifier.

It has this error when add CRS definition

GML Identifier URI: urn:ogc:def:crs:AUTO:1.3:42001 is not valid.

Change History (5)

comment:1 by Peter Baumann, 8 years ago

so what is the proposed solution, maybe show by example?

in reply to:  1 comment:2 by Bang Pham Huu, 8 years ago

Replying to pbaumann:

so what is the proposed solution, maybe show by example?

before it only allows to add URL with separator: "/", e.g: ​http://localhost:8080/def/crs/EPSG/0/4326 is valid. I fixed it to allow to add URN with separator: ":" as well.

urn:ogc:def:crs:AUTO:1.3:42001

comment:3 by Peter Baumann, 8 years ago

still see no complete URL. What OGC rule is being implemented here?

comment:4 by Dimitar Misev, 8 years ago

I'm guessing a user adds a definition which has URN identifier instead of URL? It's not a bad idea to support it for backwards compatibility.

comment:5 by Bang Pham Huu, 8 years ago

Resolution: → fixed
Status: new → closed

patch was applied, close ticket.

Note: See TracTickets for help on using tickets.