#21269 closed defect (wontfix)
Select All and Drag-to-select isn't selecting everything on MapWithAI layer
Reported by: | Owned by: | taylor.smock | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Plugin mapwithai | Version: | |
Keywords: | Cc: |
Description
Using the MapWithAI plugin around Armidale, NSW, Australia.
If I try to Select-All with Ctrl-A, it does not select all automatically created ways. Every time I hit Ctrl-A a few more get selected, but it eventually stops without all being selected.
When I move the automatically created ways to the regular data layer (Shift-A), then Ctrl A works fine on the same ways.
I have similar problems with drag select - not all automatically created ways in the region get selected, but when moved to the regular data layer drag select works fine.
Attachments (0)
Change History (3)
comment:1 by , 3 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
follow-up: 3 comment:2 by , 3 years ago
Hmmm. I'm not using it to add all the layers, but to select all and then zoom to select to see if I've missed anything. Zoom to data works ok, but I find it hard to spot the changes sometimes.
comment:3 by , 3 years ago
Replying to anonymous:
Hmmm. I'm not using it to add all the layers, but to select all and then zoom to select to see if I've missed anything. Zoom to data works ok, but I find it hard to spot the changes sometimes.
Maybe if I had a gif or video of your workflow, I'd know what you were trying to do.
It sounds like you are doing something like the following:
1) ctrl-a (or cmd-a) to select "everything"
2) Zoom to selection
3) If viewport moved, stuff still exists
4) Find missing stuff (note: if you have the selection window visible, you can zoom to specific selected elements)
Believe it or not, this was a design decision.
Someone decided to select all buildings, ways, etc. in an area, and mass add them to OSM. In the interest of avoiding that, I implemented the behavior you see today. At this point, if someone is doing that, it is deliberate and not accidental. You should be seeing a popup in the lower-left corner when it happens.
It should be noted that many of the AI buildings are relatively low quality, which is one of the reasons why this feature was added. In my experience, it is often more trouble to modify an existing poorly drawn building than it is to create a new better drawn building.
The whole point of the MapWithAI data is to have a human (a) verify the object and then (b) add the object to OSM.
All that being said, I have thought about adding a special "Import User" class, where the user would (a) have to go through the import process and (b) specify the area that they are importing and the dataset they are importing from. At that point, that specific dataset in that specific area would have an "unlimited" max add.
This, unfortunately, is probably not going to be implemented anytime soon.
All that being said, I do have a workaround for users who do want to use the MapWithAI plugin for imports at this time, and I am willing to pm you on OSM if you have gone through the import process (I will be verifying this, and I will only be pm'ing the account identified in the import process as the import user).
EDIT: The changeset that forced me to create this limitation was on the order of 10's of thousands of nodes. One of the alternatives to the current behavior was to only allow single selection. Multi-selection was something that I felt would be more preferred over single-selection (i.e., only one building/road selected).