Differing results between shapefile and mapshaper conversion about shapefile

[mbostock]

It looks like the winding order of these polygons is wrong (according to GeoJSON’s expectations):

https://observablehq.com/d/3263eaf199936bc7

It’s possible that MapShaper is correcting that for you, but this shapefile parser doesn’t do that. You should be able to fix this by reversing the coordinates of the some of the polygons and fixing the polygon-hole associations. But like #59 this isn’t really a bug in the parser, it’s just messy data that the parser isn’t fixing for you.

[mbostock]

If I have a moment I’ll see if there’s something smarter we can do with the input to correct the winding order. Thanks for including the test data.

[rdmurphy]

Gotcha. 👍 That makes sense. I'll make sure that's cleared up in post-processing when I'm using shapefile. Got it work already with an extra pass with geojson-rewind: https://observablehq.com/d/4868d7d5d3d0732a

Thank you for taking a look! 👋

[mbostock]

Folding into #64.