Question

Reprojection not working


Badge +10

I am trying to reproject this feature in order to view it on bing MAP, but its not working,

those features should be located In Dammam City in Saudi Arabia


6 replies

Userlevel 5
Badge +26

Apparently the original data claims to be in UTM84-39N, which is in fact the correct UTM zone for Dammam.

Even when I specify this in the Reprojector (and the CSMapReprojector for that matter) and set the destination to EPSG:3857 instead of the deprecated EPSG:900913 the data ends up near the Maldives.

The most logical explanation is that the coordinates are not in the system that they claim to be or that there's a unit error.

Badge +10

@redgeographics

Thanks , is there any way to fix it ?

Userlevel 5
Badge +26

@redgeographics

Thanks , is there any way to fix it ?

If you know what the correct coordinates for features in Dammam in UTM84-39N are you can check the original data in the Data Inspector (don't set a background map) and see what the difference is. If it appears to be a factor of 10 (or 100 or 1000) off it's most likely different metric units being used. If it's something else then you'll have to know which other units can potentially be used in Saudi Arabia.

 

 

Badge +10

image-1-1.pngimage-3.png@redgeographic-s

we did remove the bing map from the inspector and show UTM84-39N

we did test it on arc MAP and its on the right location please see the attached img

Userlevel 2
Badge +17

Hi @boubcher,

The X and Y coordinates seem to swapped in your data. Please use a CoordinateSwapper transformer with Swap Type set to 'X <-> Y' to restore the correct coordinate order.

This coordinate swapping can happen if the data is originally imported from GML, or created from a surveyor's CSV file (they tend to put latitude first).

Badge +10

Hi @boubcher,

The X and Y coordinates seem to swapped in your data. Please use a CoordinateSwapper transformer with Swap Type set to 'X <-> Y' to restore the correct coordinate order.

This coordinate swapping can happen if the data is originally imported from GML, or created from a surveyor's CSV file (they tend to put latitude first).

it did work for the shapefile

 

the same data is exposed and WFS and have the same issue but when we use the swapper it didn't work, is there any reason why ?

 

Reply