Opened 13 years ago
Last modified 13 years ago
#731 new defect
CSW DC output should display valid CRS URN
Reported by: | tomkralidis | Owned by: | josegar74 |
---|---|---|---|
Priority: | major | Milestone: | v2.6.5 |
Component: | Catalog server | Version: | v2.6.4 |
Keywords: | Cc: |
Description
CSW DC output has the following snippet for spatial representation:
<ows:BoundingBox crs="urn:ogc:def:crs:::WGS 1984"> <ows:LowerCorner>-52.03125 21.796875</ows:LowerCorner> <ows:UpperCorner>-106.875 54.140625</ows:UpperCorner> </ows:BoundingBox>
Is urn:ogc:def:crs:::WGS 1984
a valid CRS? Since GN controls this output, it would be valuable to output a known and valid CRS (whether it's a EPSG code, URN, etc.), which honours axis order.
Examples:
<ows:BoundingBox crs="urn:ogc:def:crs:EPSG:6.11:4326"> <ows:LowerCorner>miny minx</ows:LowerCorner> <ows:UpperCorner>maxy maxx</ows:UpperCorner> </ows:BoundingBox> <ows:BoundingBox crs="EPSG:4326"> <ows:LowerCorner>minx miny</ows:LowerCorner> <ows:UpperCorner>maxx maxy</ows:UpperCorner> </ows:BoundingBox>
Change History (4)
comment:1 by , 13 years ago
Component: | General → Catalog server |
---|
comment:2 by , 13 years ago
comment:3 by , 13 years ago
FYI the metadata above was generated from the GN UI, which allows 'WGS 1984' as a projection when specifying the bounding coordinates of the metadata, so I'm guessing this should be updated in the UI area.
comment:4 by , 13 years ago
Owner: | changed from | to
---|
Note:
See TracTickets
for help on using tickets.
Update: the WGS 1984 comes from the ISO document which was inserted into the GN catalog via CSW Transaction (Insert). I updated the ISO document with the following snippet:
at which point the CRS is outputted correctly:
However a./ the axis order is off and b./ the x coordinates are swapped (related ticket #730).