James Pae
James Pae
For a little more context; Index creation: `FT.CREATE vehicleIdx ON JSON PREFIX 1 vehicles:data: SCHEMA $.timestamp AS timestamp NUMERIC SORTABLE` roughly equivalent ft.search: `FT.SEARCH vehicleIdx "@timestamp:[0, +inf]" SORTBY "timestamp" DESC`
This is also a small bit of groundwork to make harmonizing the index types (as discussed in #600 ) a little less annoying.
thoughts? @lnicola
> I'm not sure I follow. GDAL doesn't know (or care) if you have a Vec-like growable buffer or not. You can pass in a pointer to the middle of...
We could start adding geometry types (shame `geo` is 2D-only) but that's... A lot :smile:
This might actually be a neat way to go about it if we want to avoid adding our own geometry types. Since `OGR_G_GetPoints` and `OGR_G_GetPointsZM` both simply ignore `null` data,...
> Only a little, right? It certainly beats having to cook up our own `geo_types`, so I guess I'm sold. For all the `XyzXyz`, `XxYyZz`, `ZzXxYy` etc combinations, a macro...
Very well, I'll be cooking with gas in the meantime.
@lnicola reasonably happy with this as a first go at it. Not sure how I'll go about strangely ordered coordinates (if that's even necessary) but feel free to take a...
Ok now I'm done fiddling (for real this time) so feel free to review @lnicola @weiznich whenever you have time / are feeling bored / 0.18 gets kicked through the...