Igor Dykhta
Igor Dykhta
@ilyabo Should we upstream this part with labels?
Hi @TacticalGator, It looks like this isn’t supported at the moment. Tippecanoe (and the MVT spec) don’t have a native DATE/TIME type, and type handling currently happens before we receive...
@TacticalGator string filters with tilesets are definitely not supported. int - hm, should be supported.
https://cdn.unfolded.ai/indigo/hexify_v5/{z}/{x}/{y}.pbf https://r2-public.protomaps.com/protomaps-sample-datasets/cb_2018_us_zcta510_500k.pmtiles https://api.mapbox.com/v4/mapbox.mapbox-streets-v8/{z}/{x}/{y}.mvt?access_token=XXX https://r2-public.protomaps.com/protomaps-sample-datasets/nz-buildings-v3.pmtiles https://fsq-os-places-us-east-1.s3.us-east-1.amazonaws.com/release/vector-tiles/latest/fsq-os-places.pmtiles
Bool and int should definitely work. Seems like a bug.
If you can generate some interesting examples, I can add them to the docs.
@TacticalGator Not really. What do you think is the better way to handle this? Add non-standard type hints in the metadata, or add an optional UI to define change types?
Well, it won't be an automatic detection; instead, the user will need to provide additional information about the types, as we don't have sample data to infer the types from.
@TacticalGator Time sync is implemented. You can add several datasets with timestamp or dates(?). Then in filter you filter by that timestamp. And you should be able to add +...