-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Export/Add geometry columns doesn't work as expected #16331
Comments
Author Name: Alexander Bruy (@alexbruy) Fixed in changeset "1294190e7709b50e0a1238ab9fcbf1cff2bc971c".
|
Author Name: Alexander Bruy (@alexbruy)
|
Author Name: Salvatore Larosa (@slarosa) Hi Alex,
|
Author Name: vinayan Parameswaran (vinayan Parameswaran) It is creating the geometry columns. But the attribute table is not refreshed. When I remove and add the same layer once again, I can see the columns |
Author Name: Giovanni Manghi (@gioman) I would propose to close this, because the tools works, it is just the table that is not refreshed. This issue affects also other tools, so is a more general one and would deserve a feature ticket (like "add a reload button in table of attributes"). If you don't agree please reopen this ticket.
|
Author Name: Salvatore Larosa (@slarosa) Giovanni Manghi wrote:
Now (in 0878fca) it works as in 1.8, the fields map are refreshed. Which other tools are you refering to ? |
Author Name: Giovanni Manghi (@gioman) Salvatore Larosa wrote:
I can't remember now, but may be this patch fixed them too :) Let see if in the future we are able to spot this issue again in other tools, hopefully not. |
Author Name: Giovanni Manghi (@gioman) The "ftools" category is being removed from the tracker, changing the category of this ticket to "Processing/QGIS" to not leave the category orphaned. |
Author Name: Salvatore Larosa (@slarosa)
Original Redmine Issue: 7354
Affected QGIS version: master
Redmine category:processing/qgis
The geometry columns are not create on the original layer. unless you choose an output file!
The text was updated successfully, but these errors were encountered: