Has anyone else had problems with writing to an Inspire GML with CRS EPSG 3035? For me, the X and Y is switched causing my data to be rotated and over the UK (should be over the Netherlands).
Hi @clairestoddart,
Thanks for your question! Have you by chance tried setting the GML SRS Axis Order to reverse the X and Y? If you had it previously set to 1,2 you might need to set it to 2,1 instead. You can find this option in the writer parameters. Hope that helps!
Hi @clairestoddart,
Thanks for your question! Have you by chance tried setting the GML SRS Axis Order to reverse the X and Y? If you had it previously set to 1,2 you might need to set it to 2,1 instead. You can find this option in the writer parameters. Hope that helps!
Hi @jovitaatsafe,
Thank you for your answer!
The GML SRS Axis order was not set. Setting it to 1,2 does get rid of the rotation but then my question is why does the rotation occur when this setting is not set (or set to a default)? I have never used this setting before and this is the first time I have come across this. Could it be that the EPSG 3035 uses the incorrect default setting?
Hi @jovitaatsafe,
Thank you for your answer!
The GML SRS Axis order was not set. Setting it to 1,2 does get rid of the rotation but then my question is why does the rotation occur when this setting is not set (or set to a default)? I have never used this setting before and this is the first time I have come across this. Could it be that the EPSG 3035 uses the incorrect default setting?
Hi @clairestoddart,
From what I can gather on the topic, it sounds like FME will draw from the GML srsName, and this value should use the urn form of the SRS instead of the EPSG if you want the SRS to define the correct axis order to use. It'll look something like urn:ogc:def:crs:EPSG::3035 instead of the EPSG code, if you aren't already using the urn.
My colleague also pointed me to this part in the GML reader/writer doc: "If the srsName in the GML document is set to urn:ogc:def:crs:EPSG:6.6.4326, and you know that the coordinate order in the GML document is lon-lat and not lat-lon order, set this parameter to 1,2 so that the reader reads the data in lon-lat order." So that might be why you need to set the axis order, the data incoming is in a different order than the one being set. This gis stackexchange post may also be helpful.
I see you had submitted a case (C150910), and I've received it. Let me know if this clears things up for you, and if so I can close your case as well.