Erica Fischer

Yes, if you supply multiple `.json` source files, each will be placed in its own layer, or you can use the `-L` option to associate sources with layers, or you...

Tippecanoe does not have the ability to filter layers by attribute value. You would have do something like: ``` {"type":"Feature","tippecanoe":{"layer":"one"},"geometry":{"type":"Point","coordinates":[150,45]},"properties":{"value":8}} {"type":"Feature","tippecanoe":{"layer":"two"},"geometry":{"type":"Point","coordinates":[151,45]},"properties":{"value":10}} ``` to explicitly tag each feature with its layer.

I wrote the latest revision of the mbtiles spec, so I think TileServer is wrong, not tippecanoe, but if it doesn't like the `generator_options`, you can comment out this block...

You can use the `-T` option to set the location that is used for the temporary directory. It is `/tmp` if you don't specify.

I don't think I understand the problem, since the `tippecanoe` command succeeds without having to coalesce any features. Perhaps you need `--preserve-input-order` to make the polygons layer in the order...

Are you saying that you want to union all of the features that have the same `level` into one big MultiPolygon per `level` and then drastically simplify that geometry? Tippecanoe...

Specifically you probably want to use a GIS package or something like [turf](https://github.com/turfjs) to generate a buffer around each feature, and then union together the features that have the same...

The other thing along these lines that could be a problem is that `to_tile_scale()` converts from world coordinates to tile coordinates by shifting, which may do strange things with negative...

This will be fixed in https://github.com/felt/tippecanoe/pull/60

Thanks for the report. I will look into what can be done about this in https://github.com/felt/tippecanoe. Tippecanoe currently tries to keep entire polygons from being simplified away, but does not...