Skip to main content
Geographic Information Systems

Return to Question

Post Closed as "Duplicate" by Ian Turton geoserver
naming
Source Link
Vince
Vince
  • 20.3k
  • 16
  • 48
  • 65

Different Polygon Placement Between Geoserver Versionspolygon placement between GeoServer versions for the Same Datasame data

I have a database with a table containing 27700 geometry polygons on an Azure managed Postgres database.

I've also got two GeoserverGeoServer instances with layers created from that same table, but on one of these servers the geometry is a yard or two misaligned.

One of the servers (the misaligned one) is running GeoserverGeoServer 2.20.4 on an Azure VM. The other that aligns correctly is running GeoserverGeoServer 2.16.0 on a non-Azure third party VM.

I have checked the layers and every setting I can see is the same apart from the lat/long bounding box...when I compute it I get different results even though they point to the same data:

Misaligned instance: -9.30951997270238 49.766807272578696 2.688180228215253 60.7700088415435

Correct instance: -9.308765550924253 49.76680681042395 2.690697575377409 60.77002485806145

Both layers are set to native 27700. But are called with srs=EPSG:3857. Could

Could it be that the two servers are working to a different algorithm when converting to 3857? If so, does anyone know where this setting or algorithm can be accessed and changed?

Thanks C

Different Polygon Placement Between Geoserver Versions for the Same Data

I have a database with a table containing 27700 geometry polygons on an Azure managed Postgres database.

I've also got two Geoserver instances with layers created from that same table, but on one of these servers the geometry is a yard or two misaligned.

One of the servers (the misaligned one) is running Geoserver 2.20.4 on an Azure VM. The other that aligns correctly is running Geoserver 2.16.0 on a non-Azure third party VM.

I have checked the layers and every setting I can see is the same apart from the lat/long bounding box...when I compute it I get different results even though they point to the same data:

Misaligned instance: -9.30951997270238 49.766807272578696 2.688180228215253 60.7700088415435

Correct instance: -9.308765550924253 49.76680681042395 2.690697575377409 60.77002485806145

Both layers are set to native 27700. But are called with srs=EPSG:3857. Could it be that the two servers are working to a different algorithm when converting to 3857? If so, does anyone know where this setting or algorithm can be accessed and changed?

Thanks C

Different polygon placement between GeoServer versions for the same data

I have a database with a table containing 27700 geometry polygons on an Azure managed Postgres database.

I've also got two GeoServer instances with layers created from that same table, but on one of these servers the geometry is a yard or two misaligned.

One of the servers (the misaligned one) is running GeoServer 2.20.4 on an Azure VM. The other that aligns correctly is running GeoServer 2.16.0 on a non-Azure third party VM.

I have checked the layers and every setting I can see is the same apart from the lat/long bounding box...when I compute it I get different results even though they point to the same data:

Misaligned instance: -9.30951997270238 49.766807272578696 2.688180228215253 60.7700088415435

Correct instance: -9.308765550924253 49.76680681042395 2.690697575377409 60.77002485806145

Both layers are set to native 27700. But are called with srs=EPSG:3857.

Could it be that the two servers are working to a different algorithm when converting to 3857? If so, does anyone know where this setting or algorithm can be accessed and changed?

Source Link
Columbo
Columbo
  • 151
  • 4

Different Polygon Placement Between Geoserver Versions for the Same Data

I have a database with a table containing 27700 geometry polygons on an Azure managed Postgres database.

I've also got two Geoserver instances with layers created from that same table, but on one of these servers the geometry is a yard or two misaligned.

One of the servers (the misaligned one) is running Geoserver 2.20.4 on an Azure VM. The other that aligns correctly is running Geoserver 2.16.0 on a non-Azure third party VM.

I have checked the layers and every setting I can see is the same apart from the lat/long bounding box...when I compute it I get different results even though they point to the same data:

Misaligned instance: -9.30951997270238 49.766807272578696 2.688180228215253 60.7700088415435

Correct instance: -9.308765550924253 49.76680681042395 2.690697575377409 60.77002485806145

Both layers are set to native 27700. But are called with srs=EPSG:3857. Could it be that the two servers are working to a different algorithm when converting to 3857? If so, does anyone know where this setting or algorithm can be accessed and changed?

Thanks C