We currently drop properties that are lists (or any complex property including nested properties like found in Who's On First features) on conversion from native GeoJSON like format to MVT format.
The convention that is generally followed is to stringify the complex properties.
The following Tilezen properties would be affected:
roads layer lists:
all_networksall_shield_textsall_walking_networksall_walking_shield_textsall_bicycle_networksall_bicycle_shield_textsall_bus_networksall_bus_shield_texts
pois layer lists:
Each station has several (optional) lists of routes per transport type:
train_routes a list of train routes, generally above-ground and commuter or inter-city “heavy” rail.subway_routes a list of subway or underground routes, generally underground commuter rail.light_rail_routes a list of light rail or rapid-transit passenger train routes.tram_routes a list of tram routes.
We currently drop properties that are lists (or any complex property including nested properties like found in Who's On First features) on conversion from native GeoJSON like format to MVT format.
The convention that is generally followed is to stringify the complex properties.
The following Tilezen properties would be affected:
roads layer lists:
all_networksall_shield_textsall_walking_networksall_walking_shield_textsall_bicycle_networksall_bicycle_shield_textsall_bus_networksall_bus_shield_textspois layer lists:
Each station has several (optional) lists of routes per transport type:
train_routesa list of train routes, generally above-ground and commuter or inter-city “heavy” rail.subway_routesa list of subway or underground routes, generally underground commuter rail.light_rail_routesa list of light rail or rapid-transit passenger train routes.tram_routesa list of tram routes.