wkt: No attributes in inspector and in writer

jdh wrote:

One issue you might find is that if you try and read the csv directly, the multipolygon coordinates are also separated by a comma, and would be become different columns. Putting quotes around it solves that problem.

 

 

Otherwise I don't see a real issue, other than ensuring the encoding is correct.

 

csvwkt.fmwt

@jdh: Thanks for the example code that greatly helped me a big step further. It turned out the missing quotes were causing that error. Now that I have changed my csv-file accordingly, both geometry and attributes get imported.

 

 

However - all attributes get imported as strings, in spite of me providing a csvt-file, indicating the correct data types!

 

 

As far as my research goes, this is a known problem with the ogr 1.x version library. I have imported my files successfully with ogr2ogr v. 2.x, but unfortunately this is not an option in my current project.

 

 

erik_jan wrote:

A few questions arise:

Did you set the CSV reader to have field names on the first row?

Did you convert (GeometryReplacer) the WKT attribute to a geometry?

Are the Shape attributes exactly the same as the CSV attributes (case sensitive)?

@erik_jan_: I thought I had done those first two points correctly, but it turned out the quotes were missing. Re. the shape attributes: I want to create the shape dynamically - and it turns out that there is still a problem with the data types ahead.