Opened 13 years ago
Closed 13 years ago
#3523 closed bug (wontfix)
export/add geometry columns does not work if shape is obtained from kml
Reported by: | lutra | Owned by: | dassau |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | Version 1.7.0 |
Component: | fTools | Version: | Trunk |
Keywords: | Cc: | ||
Must Fix for Release: | Yes | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
This is not always true, but there are cases where saving a shpefile from a KML leads to a vector where the "export/add geometry columns" produce X and Y columns with just zeros. Attached an example.
Attachments (1)
Change History (5)
by , 13 years ago
Attachment: | teste_shp.zip added |
---|
comment:1 by , 13 years ago
Component: | Python plugins and bindings → fTools |
---|
comment:2 by , 13 years ago
comment:3 by , 13 years ago
Owner: | changed from | to
---|
Well spotted. We can definitely close this ticket. I believe that it would also be better to add a note to the documentation. Saving the layer as singlepart it works ok.
comment:4 by , 13 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
If you examine attached shapefile with ogrinfo, you will see that it has MULTIPOINT geometry type
Single MULTIPOINT geometry can contain several points, so it is impossible to extract coordinates into one row. So I think this is invalid. Any objections to close ticket?