Steve Bennett
Steve Bennett
I've been finding this workflow a bit clumsy: 1. Add a point 2. Edit properties, such as color 3. Decide that actually I want all points on this layer to...
There are several mechanisms in Tippecanoe to determine which features to drop when necessary (smallest? densest? random?). For greater control, though, it would be handy to prepare the data to...
### Expected Behaviour 1. with `lineCap='round'`, round line caps ### Actual Behaviour 1. `lineCap` makes no difference 
``` { "description": "Home/end keys to cmd+left/right", "manipulators": [ { "from": { "key_code": "home", "modifiers": { "mandatory": [], "optional": [ "any" ] } }, "to": [ { "key_code": "left_arrow", "modifiers":...
I could not get this to give correct results. Instead, this library worked well for me: https://www.npmjs.com/package/simple-homography Note there's a mistake in the README, it should be: ``` let B...
### Exact URL of where the bug happened https://lichess.org/Wc7u092z/white#62 ### Steps to reproduce the bug 1. Learn from your mistakes (as stevage) 2. Skip the first mistake, which takes us...
It would be really convenient if you could do this: ``` ndjson-map '{...d, newProp: 3}' ``` It currently throws an error: ``` ndjson-map:expression ({...d, newProp: 3}) ^ SyntaxError: Unexpected token...
Currently the only way to know what variables are provided to the CLI expressions is to look up the web documentation. This PR gives a very brief description of each...
The current command line help text for ndjson-map isn't sufficient to use the tool (you don't know how "expression" should be constructed). Including a simple example that also shows how/why...
This works really well, thank you! It would be helpful to have a way of knowing the total feature count, in order to provide percentages to the user when processing...