-
-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added calculation of the bounding box across multiple geometry columns for PostgreSQL (3.6) #1731
base: main
Are you sure you want to change the base?
Added calculation of the bounding box across multiple geometry columns for PostgreSQL (3.6) #1731
Conversation
From #1732 (comment):
Use of ST_Collect instead of ST_Union: 9118ed2 Before (with ST_Union):
After (with ST_Collect):
bu_core3d_building contains only one row. |
The enhancement was successfully tested on a local infrastructure setup, using a PostgreSQL database containing data with multiple geometry columns. The test involved making the following deegree REST request to update the bounding box cache: Upon completion, the following output was generated, filling the relevant feature type with information regarding the bounding box:
A secondary test was conducted using identical data but stored in an Oracle database. The same REST request was issued to update the bounding box cache. As expected the bounding box cache remained unchanged, since the enhancement was specifically designed for PostgreSQL. |
Backport #1729