Skip to content
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

Handling duplicate name/conflict #86

Open
antoniolocandro opened this issue Nov 8, 2022 · 1 comment
Open

Handling duplicate name/conflict #86

antoniolocandro opened this issue Nov 8, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@antoniolocandro
Copy link

if the kart repository already includes a layer that happens to have the same name as one you are importing the plugin shows only there is conflict but no way to handle it, ideally it would allow user to specify a non-conflicting name if wanted or cancel the operations

Steps:

  1. Add a layer to the dataset from any source for example 'airportheliport'
  2. Load a GPKG that also has a source 'airportheliport'

image

@antoniolocandro antoniolocandro added the bug Something isn't working label Nov 8, 2022
@pfw
Copy link
Contributor

pfw commented Nov 8, 2022

If you currently have a need to have two versions of the same dataset in a repo you can use the command line with something similar to this:

kart import postgresql://username:@localhost/data_gov_au mdb_boundaries:another

Which will import the mdb_boundaries table as a dataset with the name another. You can also import a GPKG in a similar way.

kart import GPKG:/Volumes/GIS/data.gov.au/mdb-boundaries.gpkg mdbboundaries:another

We'll also look at how we can best support that as an option in the plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants