Digitize doesn't delete records in the attribute table when merging features.

[hcho]

I'm not sure if this is an intended behavior of the vector digitizer. I had 130 features in a vector map and digitized to delete and merge some features into one. After all this, I expected only one record in the attribute table, but I still had the 130 (pg driver). Merging multiple features didn't ask me which record to assign to the new feature, so it kind of makes sense that the digitizer didn't do anything to the attribute table because it doesn't know which one to take. Am I supposed to manually manipulate the attribute table?

I didn't try other tools, but do others do the same thing?

Thanks. Huidae

[mlennert]

Replying to hcho:

I'm not sure if this is an intended behavior of the vector digitizer. I had 130 features in a vector map and digitized to delete and merge some features into one. After all this, I expected only one record in the attribute table, but I still had the 130 (pg driver). Merging multiple features didn't ask me which record to assign to the new feature, so it kind of makes sense that the digitizer didn't do anything to the attribute table because it doesn't know which one to take. Am I supposed to manually manipulate the attribute table?

I'm not sure this really is a bug. How could GRASS know which attributes should be kept and which not ? It might be that all attributes are actually important, even if in a specific map some cat values are not present. This is a legacy of the cat value as the only attribute in the old vector formats. I would guess that most people don't use this approach much, but some might, so I wouldn't change this.

I propose to close this bug as invalid.