-
-
Notifications
You must be signed in to change notification settings - Fork 301
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
t.vect.export: GPKG support added #129
Conversation
With this method, each vector will be exported into a separate GPKG. Why not exporting all vectors of a single stvds into a single GPKG with |
That sounds reasonable. But I wouldn't know how to rewrite _export_vector_maps_as_gpkg() accordingly... |
In this case the importer must be aware of this format too. Hence, more
programming effort to get it to work. The current solution is fine in my
opinion.
Am Do., 12. Sept. 2019 um 14:56 Uhr schrieb Markus Metz <
notifications@github.com>:
… With this method, each vector will be exported into a separate GPKG. Why
not exporting all vectors of a single stvds into a single GPKG with v.out.ogr
-u?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#129?email_source=notifications&email_token=ACQPJDJVOIR42EVFNRPW3VTQJI4ALA5CNFSM4IWB6JO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6RY4BY#issuecomment-530812423>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACQPJDOWC465KVE4O6KLVHDQJI4ALANCNFSM4IWB6JOQ>
.
|
Can I merge or not yet? |
I agree with @huhabla that the current solution is fine. Putting all vectors into a single OGR datasource can make things more complicated. Fine with me to merge. |
Backported to relbr78 in 04b2790 |
No description provided.