fix order of 3D features in query results (fix #7883) #7953
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes #7883, a bug where a query returned 3D features after 2D features even if they were rendered above them. Query results should be returned in the order the features are rendered.
The fix is somewhat tricky because the order of features can get complicated:
This sorts features in the order they are rendered and adds a query test to make sure that is the case.
Launch Checklist