GitLab

* modernize geojson-vt into a ES module

* try commiting yarn.lock

* reshuffle coverage scripts a bit

* add src to files

* explode multilinestrings on line metrics

* refactor tile creation

* track line metrics when clipping

* fix typo in line metrics

* fix one more silly bug

* clean up clipping code

* minor fix for non-lineMetrics sources

* add a line metrics test

* fix metrics for wrapped lines, more tests

* minor tests cleanup

* rename line metric properties

* improve test coverage more

* prefix clip_start/end properties

The missing comma within the object literal would cause copy-and-pasting the example to throw a syntax error.

changelog is now maintained over https://github.com/mapbox/geojson-vt/releases

* WIP flat array refactor (preprocess stage)

* refactor more type conversions

* flat conversion refactoring

* more convert cleanup

* rewrite clipping for flat geometry

* more flat geom code

* more flat geom

* simplify clip

* more clip simplification

* minor fixes

* fix transformed coords

* add back world wrapping

* remove solid square heuristics

they are mostly premature optimization that only makes the implementation more complex

* various clipping fixes

* some fixes

* conversion fixes

* simplify tile.js

* lots of fixes

* fix remaining tests and bugs

* remove leftover

* Describe how to exhaustively pre-generate all tiles

* clarify that `tileCoords` contains tile coordinates, not tiles

* Support for topojson in example

* Add topojson global

* start at supporting far away worlds

* test 3 world limit

* rename and lint

It's not strictly required, but it's useful metadata, and part of the recommended license template text (see http://choosealicense.com/licenses/isc/ and https://opensource.org/licenses/isc-license)

Save empty tiles at the bottom of the pyramid, per https://github.com/mapbox/geojson-vt-cpp/pull/47#discussion_r68474205 (#65)

ignore features with null geometry

As per the GeoJSON spec, "A feature object must have a member with
the name "geometry". The value of the geometry member is a geometry
object as defined above or a JSON null value." [1]

[1] http://geojson.org/geojson-spec.html#feature-objects

Previously when there was a null geometry there would be a JS error
in trying to access feature.geometry.type.

this is for consistency; it would be nicer to take buffer into account
but we can handle this later, not a big deal.

Turns out this is an extremely rare use case and the public method is
easy to misuse, so let’s move this code to external repo, just reusing
the files from the repo.