Skip to main content
  • EN

Hi there. I am outputting SQL data into a CSV into well known text. Some of these features are polygons and others are multipolygons. I am finding in the output some multipolygon WKT strings are spilling over into other fields which throws everything out. I'm not sure the field length is exceeding the maximum length for a CSV but is there anything I can do to keep it all on one line or is this a problem with multipolygons?

 

I'm using a GeometryExtractor to convert to WTK, then a couple of StringReplacers to remove Z and change the SRID from 0 to 3857 so the csv can be brought into Power BI. Most are appearing fine.

 

Regards,

 

Josh

I would use a 2DForcer before the GeometryExtractor to remove Z, maybe the string replacement is corrupting the WKT?

Thanks for that. I saw your previous message about the delimiter. You might be right as it is splitting where the commas should be. I changed the delimiter to # however and when I open the CSV I still need to change text to columns for the first lot of columns with # but the WKT field is still split up by the commas.

Thanks for that. I saw your previous message about the delimiter. You might be right as it is splitting where the commas should be. I changed the delimiter to # however and when I open the CSV I still need to change text to columns for the first lot of columns with # but the WKT field is still split up by the commas.

All good. I imported into Excel using the # and it all works.

Reply


Community Stats

30,120
Posts
114,322
Replies
37,749
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.