Opened 7 months ago

Closed 7 months ago

#1428 closed defect (fixed)

SECORE_Cannot add new CRS by URN

Reported by: bphamhuu Owned by: bphamhuu
Priority: major Milestone: 9.3
Component: secore Version: development
Keywords: SECORE URN invalid Cc: dmisev
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 follow-up: Changed 7 months ago by pbaumann

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

comment:2 in reply to: ↑ 1 Changed 7 months ago by bphamhuu

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 Changed 7 months ago by pbaumann

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

comment:4 Changed 7 months ago by dmisev

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 Changed 7 months ago by bphamhuu

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

patch was applied, close ticket.

Note: See TracTickets for help on using tickets.