When we import the data instead of using column store let's do the same as we do for OpenStreetMap and import using hstore to store arbitrary tags (keys, values).
This would then be paired with moving more property normalization logic out of the JINJA and into the layer YAML.
jsonb_build_object(
'name', name,
'source', 'whosonfirst.mapzen.com',
'mz_n_photos', n_photos,
'area', area::bigint,
'min_zoom', min_zoom,
'max_zoom', max_zoom,
'is_landuse_aoi', CASE WHEN is_landuse_aoi = TRUE THEN TRUE END,
'kind', wof_np.placetype_string
) AS __places_properties__
Most if not all of that can then be migrated to the YAML.
Similar to #1357.
When we import the data instead of using column store let's do the same as we do for OpenStreetMap and import using hstore to store arbitrary tags (keys, values).
This would then be paired with moving more property normalization logic out of the JINJA and into the layer YAML.
For example:
Most if not all of that can then be migrated to the YAML.