Conversation
- or not legend/mapunit level constraint
This was
linked to
issues
Apr 30, 2026
Closed
…patial query" This reverts commit efc9d91.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fix for #466
Also, fixes warning due to primary key duplication with
fid_column_nameon a non-spatial table. This is a super annoying behavior, and probably we need a wrapper function aroundsf::read_sf()instead of all the ad hoc NULLing of keys that needs to be done to get the FGDB result to match GPKG.Also, adds tests to close long-standing issue #398