Bug report #7703
WKT import two problems
|Category:||Data Provider/Delimited Text|
|Affected QGIS version:||1.8.0||Regression?:||No|
|Operating System:||Mac OSX||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||worksforme|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||16614|
TEST.CSV id,wkt 1,"POLYGON((10 10,20 20,20 30,20 10))"
vector imports with correct values and individual points can be edited. But, no feature can be selected that was imported this way, so they can't be moved. New features added manually can be selected and moved normally. Maybe related, only wkt-created features fully contained within the view are shown, wkt-features that have even a small bit outside the view vanish; features added manually behave normally by showing the portion in the view. Layer editing capabilities are normal (full).
#2 Updated by John Sankey over 8 years ago
Two QGIS 1.8.0 users on Windows say neither of these problems occur with them. Seems as though it's specific to Mac. I've put up the files QGIS created at http://johnsankey.ca/QGISWKT.ZIP in hopes it will help. Also, I've found that the problem features aren't recognized by id, but the ones added by QGIS are.
#3 Updated by John Sankey over 8 years ago
I've now found that I can get stuff from WKT by pasting it into QuickWKT, then pasting the WKT-created feature into a QGIS-created layer. It has to be done one feature at a time, so is impractical for a dataset of any size. When the shape file created this way is loaded into QGIS as a new project, the coordinates show properly in the mouse tracking X,Y window (0-30 m) but the indicated scale is crazy: in the 3 million range. The print engine gets that crazy scale, but displays and prints the 0-30 m features properly.
WKT seems to be the only way numerical coordinate maps can be imported into QGIS. It's critical that at least one such method works. There are thousands of maps published only in numerical coordinate form - I have a dozen of mine from as long as 30 years ago that are still frozen in a Win3.1 system that only outputs true CSV: x,y<EOL>