Making sense of coordinate systems in retrieved data from a CSW

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I am invoking a CSW server (Catalog Service for the Web) and I am trying to draw the bounding box of each record in the front end of my application.



One of the problems is that the coordinate system of the bounding box is not always in EPSG. What I recieve is something like this:



<ows:BoundingBox crs="urn:x-ogc:def:crs:EPSG:6.11:4326" dimensions="2">
<ows:LowerCorner>-1.7 -10.3</ows:LowerCorner>
<ows:UpperCorner>5.4 5.1</ows:UpperCorner>
</ows:BoundingBox>


So the coordinate system information is condensed in a string like this:



urn:x-ogc:def:crs:EPSG:6.11:4326


But this string does not always make sense. For instance, sometimes I recieve strings like this:



urn:ogc:def:crs:::Lambert Azimuthal Projection


Is there a way to transform these coordinate system identifiers into WKT (well known text)? Doing so one can programmatically assign a coordinate system to these strings.










share|improve this question









New contributor




hjbello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.















  • 1




    Do you know what the server is? Because the 2nd one is probably a bug
    – Ian Turton♦
    Oct 1 at 8:57










  • Yes, the second comes from a geonetwork server. The first from a geoserver.
    – hjbello
    Oct 1 at 10:09














up vote
1
down vote

favorite












I am invoking a CSW server (Catalog Service for the Web) and I am trying to draw the bounding box of each record in the front end of my application.



One of the problems is that the coordinate system of the bounding box is not always in EPSG. What I recieve is something like this:



<ows:BoundingBox crs="urn:x-ogc:def:crs:EPSG:6.11:4326" dimensions="2">
<ows:LowerCorner>-1.7 -10.3</ows:LowerCorner>
<ows:UpperCorner>5.4 5.1</ows:UpperCorner>
</ows:BoundingBox>


So the coordinate system information is condensed in a string like this:



urn:x-ogc:def:crs:EPSG:6.11:4326


But this string does not always make sense. For instance, sometimes I recieve strings like this:



urn:ogc:def:crs:::Lambert Azimuthal Projection


Is there a way to transform these coordinate system identifiers into WKT (well known text)? Doing so one can programmatically assign a coordinate system to these strings.










share|improve this question









New contributor




hjbello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.















  • 1




    Do you know what the server is? Because the 2nd one is probably a bug
    – Ian Turton♦
    Oct 1 at 8:57










  • Yes, the second comes from a geonetwork server. The first from a geoserver.
    – hjbello
    Oct 1 at 10:09












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I am invoking a CSW server (Catalog Service for the Web) and I am trying to draw the bounding box of each record in the front end of my application.



One of the problems is that the coordinate system of the bounding box is not always in EPSG. What I recieve is something like this:



<ows:BoundingBox crs="urn:x-ogc:def:crs:EPSG:6.11:4326" dimensions="2">
<ows:LowerCorner>-1.7 -10.3</ows:LowerCorner>
<ows:UpperCorner>5.4 5.1</ows:UpperCorner>
</ows:BoundingBox>


So the coordinate system information is condensed in a string like this:



urn:x-ogc:def:crs:EPSG:6.11:4326


But this string does not always make sense. For instance, sometimes I recieve strings like this:



urn:ogc:def:crs:::Lambert Azimuthal Projection


Is there a way to transform these coordinate system identifiers into WKT (well known text)? Doing so one can programmatically assign a coordinate system to these strings.










share|improve this question









New contributor




hjbello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











I am invoking a CSW server (Catalog Service for the Web) and I am trying to draw the bounding box of each record in the front end of my application.



One of the problems is that the coordinate system of the bounding box is not always in EPSG. What I recieve is something like this:



<ows:BoundingBox crs="urn:x-ogc:def:crs:EPSG:6.11:4326" dimensions="2">
<ows:LowerCorner>-1.7 -10.3</ows:LowerCorner>
<ows:UpperCorner>5.4 5.1</ows:UpperCorner>
</ows:BoundingBox>


So the coordinate system information is condensed in a string like this:



urn:x-ogc:def:crs:EPSG:6.11:4326


But this string does not always make sense. For instance, sometimes I recieve strings like this:



urn:ogc:def:crs:::Lambert Azimuthal Projection


Is there a way to transform these coordinate system identifiers into WKT (well known text)? Doing so one can programmatically assign a coordinate system to these strings.







coordinate-system coordinates extents csw






share|improve this question









New contributor




hjbello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




hjbello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited Oct 1 at 12:07









Vince

14.1k32445




14.1k32445






New contributor




hjbello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Oct 1 at 8:17









hjbello

1084




1084




New contributor




hjbello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





hjbello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






hjbello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.







  • 1




    Do you know what the server is? Because the 2nd one is probably a bug
    – Ian Turton♦
    Oct 1 at 8:57










  • Yes, the second comes from a geonetwork server. The first from a geoserver.
    – hjbello
    Oct 1 at 10:09












  • 1




    Do you know what the server is? Because the 2nd one is probably a bug
    – Ian Turton♦
    Oct 1 at 8:57










  • Yes, the second comes from a geonetwork server. The first from a geoserver.
    – hjbello
    Oct 1 at 10:09







1




1




Do you know what the server is? Because the 2nd one is probably a bug
– Ian Turton♦
Oct 1 at 8:57




Do you know what the server is? Because the 2nd one is probably a bug
– Ian Turton♦
Oct 1 at 8:57












Yes, the second comes from a geonetwork server. The first from a geoserver.
– hjbello
Oct 1 at 10:09




Yes, the second comes from a geonetwork server. The first from a geoserver.
– hjbello
Oct 1 at 10:09










1 Answer
1






active

oldest

votes

















up vote
2
down vote



accepted










OGC URNs are defined and described in OGC Document 07-092r1, the first one you have encountered is telling you that your data is in EPSG:4326 as defined in version 6.11 of the EPSG database (that is lat,lon).



The second one looks like either a major bug in GeoNetwork or (more likely) a user data input issue where some one has typed "Lambert Azimuthal Projection" into a box that was expecting an EPSG numeric code.






share|improve this answer




















  • Thank you very much! The link you provide explains how to extract all the parameters necessary to understand the coordinate system urn:ogc:def:objectType:authority:version:code:value1:value2
    – hjbello
    Oct 1 at 10:53











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "79"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);






hjbello is a new contributor. Be nice, and check out our Code of Conduct.









 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f297517%2fmaking-sense-of-coordinate-systems-in-retrieved-data-from-a-csw%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
2
down vote



accepted










OGC URNs are defined and described in OGC Document 07-092r1, the first one you have encountered is telling you that your data is in EPSG:4326 as defined in version 6.11 of the EPSG database (that is lat,lon).



The second one looks like either a major bug in GeoNetwork or (more likely) a user data input issue where some one has typed "Lambert Azimuthal Projection" into a box that was expecting an EPSG numeric code.






share|improve this answer




















  • Thank you very much! The link you provide explains how to extract all the parameters necessary to understand the coordinate system urn:ogc:def:objectType:authority:version:code:value1:value2
    – hjbello
    Oct 1 at 10:53















up vote
2
down vote



accepted










OGC URNs are defined and described in OGC Document 07-092r1, the first one you have encountered is telling you that your data is in EPSG:4326 as defined in version 6.11 of the EPSG database (that is lat,lon).



The second one looks like either a major bug in GeoNetwork or (more likely) a user data input issue where some one has typed "Lambert Azimuthal Projection" into a box that was expecting an EPSG numeric code.






share|improve this answer




















  • Thank you very much! The link you provide explains how to extract all the parameters necessary to understand the coordinate system urn:ogc:def:objectType:authority:version:code:value1:value2
    – hjbello
    Oct 1 at 10:53













up vote
2
down vote



accepted







up vote
2
down vote



accepted






OGC URNs are defined and described in OGC Document 07-092r1, the first one you have encountered is telling you that your data is in EPSG:4326 as defined in version 6.11 of the EPSG database (that is lat,lon).



The second one looks like either a major bug in GeoNetwork or (more likely) a user data input issue where some one has typed "Lambert Azimuthal Projection" into a box that was expecting an EPSG numeric code.






share|improve this answer












OGC URNs are defined and described in OGC Document 07-092r1, the first one you have encountered is telling you that your data is in EPSG:4326 as defined in version 6.11 of the EPSG database (that is lat,lon).



The second one looks like either a major bug in GeoNetwork or (more likely) a user data input issue where some one has typed "Lambert Azimuthal Projection" into a box that was expecting an EPSG numeric code.







share|improve this answer












share|improve this answer



share|improve this answer










answered Oct 1 at 10:31









Ian Turton♦

45.3k543105




45.3k543105











  • Thank you very much! The link you provide explains how to extract all the parameters necessary to understand the coordinate system urn:ogc:def:objectType:authority:version:code:value1:value2
    – hjbello
    Oct 1 at 10:53

















  • Thank you very much! The link you provide explains how to extract all the parameters necessary to understand the coordinate system urn:ogc:def:objectType:authority:version:code:value1:value2
    – hjbello
    Oct 1 at 10:53
















Thank you very much! The link you provide explains how to extract all the parameters necessary to understand the coordinate system urn:ogc:def:objectType:authority:version:code:value1:value2
– hjbello
Oct 1 at 10:53





Thank you very much! The link you provide explains how to extract all the parameters necessary to understand the coordinate system urn:ogc:def:objectType:authority:version:code:value1:value2
– hjbello
Oct 1 at 10:53











hjbello is a new contributor. Be nice, and check out our Code of Conduct.









 

draft saved


draft discarded


















hjbello is a new contributor. Be nice, and check out our Code of Conduct.












hjbello is a new contributor. Be nice, and check out our Code of Conduct.











hjbello is a new contributor. Be nice, and check out our Code of Conduct.













 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f297517%2fmaking-sense-of-coordinate-systems-in-retrieved-data-from-a-csw%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?