Modify High Road logic to pull out airport lines out of minor roads

[nvkelso]

• What did you see? Airport runways appear as minor roads.
• What did you expect to see? They're import enough of a top level category runway and taxiway should be pulled out into a new aeroway kind, with runway and taxiway preserved as kind_detail.
• What map location are you having problems with? SFO airport south of San Francisco.

      aeroway: runway
      aeroway: taxiway

[nvkelso]

See:

• vector-datasource/yaml/roads.yaml

  Lines 366 to 388 in 1551301

  	#############################################################
  	#
  	# OSM aeroway
  	#
  	#############################################################
  	- filter:
  	aeroway: runway
  	min_zoom: 9
  	table: osm
  	output:
  	<<: *osm_highway_properties
  	<<: *osm_network_from_tags
  	kind: minor_road
  	aeroway: {col: aeroway}
  	- filter:
  	aeroway: taxiway
  	min_zoom: 11
  	table: osm
  	output:
  	<<: *osm_highway_properties
  	<<: *osm_network_from_tags
  	kind: minor_road
  	aeroway: {col: aeroway}

[nvkelso]

@nvkelso to add sort order recommendation.

[nvkelso]

The landuse polygons for runway and taxiway should sort immediately above the lines in the roads layer (so lowest is line, line, polygon, polygon to topmost). So many sort orders for the other road features will need to bump up.

[rmarianski]

Couple of questions:

Not sure I follow exactly what should happen for the sort_order. The landuse values are:

runway => 63
apron => 62
taxiway => 61

And in roads:

z>=15 (not tunnel)
runway => 427
taxiway => 426
z>=15 (tunnel)
runway => 327
taxiway => 326
z<15
runway => 377
taxiway => 376

The rest of the values in both roads and landuse are close in value to those. If we sort the aeroway landuse polygons immediately above, wouldn't we have to bump the other landuse values up as well too (by a few hundred)? And then probably the rest of the roads on top of that?

Additionally, should we continue to include the aeroway tag on roads features? Or is that now completely captured by the kind_detail? If we want to drop it, we might have similar opportunities for normalizing some of the other roads tags into a kind_detail.

[nvkelso]

Yes, we need to bump most the other road values up by 2 (zoom <15) and then 4 (zoom >= 15), and probably enable zoom ranges in landuse CSV.

Note: I think the above proposal is better than the alternative of putting the runway and taxiway road lines below the landuse in the landuse range. We've talked about dynamically re-sorting the landuse sort values (based on area) as a post-processing step, this probably complicates that.

Road kind_detail is covered in #719. We could probably remove the aeroway tag after that issue is completed (but may be harder for people to transition to Mapzen tiles from another provider).