Skip to main content
Question

GeometryExtractor WKT output splitting out multipolygons onto separate lines


joshuajames1979
Contributor
Forum|alt.badge.img+7

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

3 replies

nielsgerrits
VIP
Forum|alt.badge.img+54

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


joshuajames1979
Contributor
Forum|alt.badge.img+7

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.


joshuajames1979
Contributor
Forum|alt.badge.img+7
joshuajames1979 wrote:

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.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings