Looking through the PostGIS docs I found some information on manually registering geometry columns: https://postgis.net/docs/using_postgis_dbmanagement.html#Manual_Register_Spatial_Column
From: Vera Green [mailto:vera.green...@gmail.com] Sent: Wednesday, 4 December 2019 12:48 PM To: GeoServer Mailing List List <geoserver-users@lists.sourceforge.net> Subject: [Geoserver-users] Native SRS Not Detected for layer from PG Store After Permission Update Hello, This issue is a bit of a ghost so I apologies for the long lead-up but it is necessary. I WAS having an issue where some (but not all) tables coming from a PostGIS database store did not automatically pick up the native SRS from the layer. It can be resolved by declaring the SRS manually however this causes issues downstream in our workflow where the layer is served as WMS to leaflet. Even though the Open Layers preview will show the data, the WMS will not. This issue can be resolved by setting PG permissions as per this post which offers an excellent PG permission setup recipe: https://stackoverflow.com/questions/41537825/restricted-postgresql-permissions-for-web-app/47955583#47955583 After completing this trust that the issue is no longer PG permissions! So finally the issue: After permissions are updated in PG GeoServer continues to NOT pick up the native SRS from the layer. Even after disconnecting and reconnecting to GeoServer. Even after connection from an incognito window to a new GeoServer session! Somewhere it is stored and locked. To resolve rename the table in PG (obviously not ideal and not always an option). Then GeoServer immediately sees the native SRS. So my question is, where is the layer information being locked up and how to refresh the connection between the PG data store and GeoServer? Versions: GeoServer: 2.15.0 PG 10 (postGIS 2.4) , 11 and 12 (postGIS 2.5) Browser: Chrome Thank you, Vera (PS, I am now taking some headache medication since I banged my head against the wall for so long with regard to this. If this can not be resolved at least I am hoping this post will help others work around it.) ________________________________ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission.
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
