Hi I am a user of Geoserver. I have configured Geo Server with SDE plugin. I
am able to access all my SDE layers. I have successfully published my SDE
layers as well. From layers preview I have generated Google Earth KML file.
There I found an issue that layers projection is slightly shifted with an 50
meters distance.
My spatial reference was pointing to QND95 and EPSG:2932 or wkid is 2932.
For cross checking I have exported my feature classes into shape files and I
exported them POSTGIS Database using command shp2psql. After exporting I
have done the set_Transform command for all the tables that I exported.
I have configured postgresql in Geo Server and was successfully accessing
the postgis table.
That seems to be projecting in a correct way.
I am confused where exactly the problem lies. It should be considered as
major issue.
50 m sounds very specific. I would check the data at each stage and look for a difference in spatial reference system, or the definition of the spatial reference system between ArcSDE and GeoServer and Google Earth.
Hi I am a user of Geoserver. I have configured Geo Server with SDE plugin. I
am able to access all my SDE layers. I have successfully published my SDE
layers as well. From layers preview I have generated Google Earth KML file.
There I found an issue that layers projection is slightly shifted with an 50
meters distance.
My spatial reference was pointing to QND95 and EPSG:2932 or wkid is 2932.
For cross checking I have exported my feature classes into shape files and I
exported them POSTGIS Database using command shp2psql. After exporting I
have done the set_Transform command for all the tables that I exported.
I have configured postgresql in Geo Server and was successfully accessing
the postgis table.
That seems to be projecting in a correct way.
I am confused where exactly the problem lies. It should be considered as
major issue.
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
50 m sounds very specific. I would check the data at each stage and look
for a difference in spatial reference system, or the definition of the
spatial reference system between ArcSDE and GeoServer and Google Earth.