Relative Content

Tag Archive for mysql-8.0

“Publishing geom data from MySQL 8 in GeoServer with latitude values outside the (-90, 90) range.”

When I publish geometry data in mysql8 using geoserver 2.26.0, the order of latitude and longitude is (latitude, longitude) instead of (longitude,latitude ). The reason is that when mysql8 stores geographic data, the longitude and latitude are stored in the (latitude, longitude) order. As a result, the geoserver identifies the range.x identifies the range of mysql mid-latitudes.y identifies the range of longitudes. This occurs after srid is added when mysql inserts wkt data. Has anyone ever encountered a similar problem? How is it solved? Can you help me.

“Publishing geom data from MySQL 8 in GeoServer with latitude values outside the (-90, 90) range.”

When I publish geometry data in mysql8 using geoserver 2.26.0, the order of latitude and longitude is (latitude, longitude) instead of (longitude,latitude ). The reason is that when mysql8 stores geographic data, the longitude and latitude are stored in the (latitude, longitude) order. As a result, the geoserver identifies the range.x identifies the range of mysql mid-latitudes.y identifies the range of longitudes. This occurs after srid is added when mysql inserts wkt data. Has anyone ever encountered a similar problem? How is it solved? Can you help me.