grant-humphries / tm-map-tiles Goto Github PK

the dash array property needs to be adjusted at each zoom level for each street type

need to establish an order in this table so that things are rendered in the proper order

add hillshade at further lower zoom levels, it looks like rlis data won't be adequate for this because the coverage doesn't extend throughout the whole extract that we cover, so I need to look into USGS as a source. The process of acquiring and loading the data into postgis should be automated

--small parks should be filtered out higher zoom levels and possibly smoothed
--may want to use different shades of green for the various park types (natural='wood', leisure='park', etc.)

so that's:
service at z15
local at z13 & z14

should be layered in with streets, including on the bridge and tunnel layers

that is highway='raceway' these could be included or not, but as of now everything where highway is not null is rendered

some trails link up to these and it looks odd when they're excluded

The source for this NLCD which is free data via the government. I've worked out the colors for this to a certain extent on the system map, but I'll need a way to implement the gaussian blur technique that was used in illustrator. And again the acquisition and loading of the data (into PostGIS) needs to be automated

construction definitely needs to be rendered, proposed is more debatable, but osm default still has done some cool stuff with transparency on those

these behave similarly to the way trails do

It's broken and doesn't display properly in TileMill. This can like by handle when the larger extract is clipped by either osmosis or osmconvert

there's lots of detail like this in OSM and I'd like to make use of it. this stuff will begin to appear at higher zoom levels when landcover is phased out

check in with creative services and see what where they're at with the official TriMet icons

I've created an svg for the system map project that should work well for this

it looks weird without them mostly due to the grass that has been digitized around runways, plus having detail at the airport is appropriate to the purpose of this map

turning circle casing should be the same as the casing on other parts of the street. this also ties into the larger issue of creating variables for street casing not just for fill, this should simplify things, but giving them a clean look in the style sheet is somewhat difficult because the initial fill variables must be referenced meaning each variable assignment can take up a half a line or more

-include the key 'motorway_link' to identify motorway links that connect two freeway
-switch to hstore for tags not named in stylesheet, this could actually take care of the above issue as well