Closed gregallensworth closed 6 years ago
building -- reworked some SQL functions, to expose the building
field. The buildings have no name information, but the building
at least indicates what the building is used for, e.g. "church" or "school"
poi -- This already had the name
fields worked into the functions and schema, and exposed via vectiles as well. I have set up tooltips for all poi
features used in the current style.
place -- Already done; this is the large place/region labels e.g. "Seattle"
transportation -- Did some DB hacks to add a name
field to this layer; updated the gh-pages
demo as well
water -- easy peasey. 14 views, all from the same dataset. Now they have hover effects.
parks -- cannot The source layers do not have name information:
osm_park_polygon_gen8
osm_park_polygon_gen7
osm_park_polygon_gen6
osm_park_polygon_gen5
osm_park_polygon_gen4
osm_park_polygon_gen3
osm_park_polygon_gen2
osm_park_polygon_gen1
osm_park_polygon
Expanding on #1 so as to make the best of #4
Labels are displayed as the
XXX_name
layer, e.g.waterway_name
andlayer_transportation_name
These are point layers generated by the OSM import tools, into wholly-new Db tables such aslayer_transportation_name
However, the geometry-only layers such as
water
andwaterway
andtransportation
have minimal SQL queries for just the geometry This means that mouse-and-tooltip and click-info behaviors do not work properly -- no attributes are included.Add at least the
name
field to these layers:There may be more in the future, but for the immediate dataset this would be an improvement.