We could be querying a Geoserver or ArcGis server for WFS features (v1.1.0). However I'm finding that Geoserver takes the envelope bounds in LONG LAT and Arcgis takes them in LAT LONG. The use of srsName="EPSG:..." doesn't seem to have any affect on the input coordinates.
Is this a known situation and is there any reliable solution to cater for this? I see a GEOSERVER ows:keyword for Geoserver but Arcgis doesn't have anything like this. I think this would be unreliable. They each have different endpoints (wfs verses WFSServer) though this too is unreliable.
This is a significant issue though I can't see anyone else has had this problem so I feel I must be missing something obvious. Or no one else is trying to hit more than one type of geospatial data servers.
Is this a known problem?
For example.
Geoserver server - http://geossdi.dmp.wa.gov.au:80/services/wfs
POST -
gsml:collarLocation/gsml:BoreholeCollar/gsml:location 37.0 -55.0 229.0 12.0 ArcGis server - http://www.ga.gov.au/gis/services/topography/National_Onshore_Gas_Pipelines/MapServer/WFSServer?
Post -
SHAPE -55.0 37.012.0 229.0
أكثر...
Is this a known situation and is there any reliable solution to cater for this? I see a GEOSERVER ows:keyword for Geoserver but Arcgis doesn't have anything like this. I think this would be unreliable. They each have different endpoints (wfs verses WFSServer) though this too is unreliable.
This is a significant issue though I can't see anyone else has had this problem so I feel I must be missing something obvious. Or no one else is trying to hit more than one type of geospatial data servers.
Is this a known problem?
For example.
Geoserver server - http://geossdi.dmp.wa.gov.au:80/services/wfs
POST -
gsml:collarLocation/gsml:BoreholeCollar/gsml:location 37.0 -55.0 229.0 12.0 ArcGis server - http://www.ga.gov.au/gis/services/topography/National_Onshore_Gas_Pipelines/MapServer/WFSServer?
Post -
SHAPE -55.0 37.012.0 229.0
أكثر...