Ignacio Vera

Actually, my understanding is that we only enable concurrency when the result is exact, so this is unexpected. @craigtaverner I am going to take this one.

Oh yes, you are totally right. Points are counter-clockwise, e.g the signed area is positive.

can we keep explicit `== false` checks instead of less readable `!`?

Yes we are super interested, need to find the time (and in my case, some python skills :))

A mvt request is very similar to a search request except it requires 4 mandatory parameters. One is the field where the geo data is, and the other three is...

An example of how this would look like in the geoshape track is: ``` { "name": "mvt-search-hits", "operation-type": "mvt", "index": "osm*", "field": "shape", "z" : 2, "x" : 2, "y"...