Connection between unconnected polygons about earcut.hpp HOT 7 CLOSED

The best test case is always the offending polygon GeoJSON coordinates, although I can settle for just the vector tile and try to find extract it myself.

from earcut.hpp.

There's a script here that will autoreduce a test case given a vector tile URL and layer name.

from earcut.hpp.

@mourner GeoJSON as vector tile coordinates or as floating point WGS84?

from earcut.hpp.

@flippmoke screen coords as encoded. I'm investigating the issue.

from earcut.hpp.

@mourner how to get the screen coordinates or WGS84 using node-mapnik, if you need the WGS84 coordinates correct make sure you create the tile with the proper z,x,y

"use strict";

var fs = require('fs');
var mapnik = require('mapnik');

var data = fs.readFileSync("./this_tile_name.mvt");
var vtile = new mapnik.VectorTile(0,0,0);
vtile.setData(data);
// output as geojson
fs.writeFileSync('the_tile.geojson', vtile.toGeoJSONSync('__all__'));
// output contains tile coordinates (not geojson format)
fs.writeFileSync('the_tile.json', vtile.toJSON({decode_geometry:true}));

from earcut.hpp.

For the record, the tile is http://mapbox-streets.s3.amazonaws.com/00/vector-terrain-2.4.0/8/16/64.vector.pbf

@flippmoke thanks!

from earcut.hpp.

It turned out to be a bug in ring classification code. Fixed by mapbox/mapbox-gl-js@9369d51

from earcut.hpp.