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 is take 2 to make it possible to use the inbuilt-vector data (world map etc) to be used in PyQGIS etc:
First take was: #39175 There @nyalldawson proposed to do it not ogr-specific but on a higher level. This is my first attempt to do it as he described there: #39175 (review)
Not sure if that was what he meant. I think more code has to get rewritten here (as for example now a inbuilt-uri WITHOUT layername-part will not load AND not popup the 'choose layer dialog', because the vectorLayerPath is const...
Should I create a copy of it and use that in the whole function?
Or am I totally wrong anyway.
One argument why I like #39175 actually better is that (untill now) inbuild is only used with OGR provider (and it is/was a oneline change). But feel free to disagree/comment or stop me from trying :-)
Also note that my proposed plan B in #39175
actually does not work on Linux distro installs, because the gpkg in the resource is not readable by the average user apparently.