Roadway links missing names (and freeway links missing route direction)

[lmz]

There are gaps in roadway links with the name missing which is a usability issue.

For freeways, need the route direction as well based on the route signing; e.g. 101 N vs 101 S. In TM1.5, this is done here: BayAreaMetro/TM1_2015_Base_Network@ba5089a

@yuqiww - would you mind summarizing how many are missing by facility type?
Also, this may have improved with Ranch tools

[yuqiww]

data: M:\Data\GIS layers\TM2_Networks\model_net.gdb\links

[yuqiww]

Three data sources have road "name" information: OSM, TomTom, SFCTA. In the current data (V12), only OSM "name" is kept in the Standard Network and Model Network. Names in TomTom and SFCTA data are dropped from the "links" table during Pipeline, but are processed (along with lanes data from these data sources) and stored at Lasso lookup tables, using this R script and "conflation_result.csv" (output of Pipeline step4 conflation with third-party).

Some links that are missing "name" in v12 links have names from TomTom and SFCTA, therefore bringing in these will fill some missing names. Two potential approaches:

1. keep 'name' from all sources during the Pipeline - this requires modify and rerun the Pipeline script
2. add 'name' from Lasso lookup tables back to Standard Network - this could be added as a step to 01-attribute-and-make-pickles.ipynb. Under this approach, two options of presenting the "name" data:
   1. (less processing, more raw info kept) adding TomTom and SFCTA names as two new fields, so three name fields in total, then clean it up in Model Network creation
   2. (more processing, less raw info kept) apply the "shorten name" method in this step to clean up the OSM names, then if it is NA, fill in using TomTom or SFCTA names

Note about the "shorten name" method: In Standard Network, road name still keep the list format from OSM conflation - a mix of strings and lists of strings. This comes from OSM SharedStreet conflation - when two OSM links are conflated to the same SharedStreet link, both OSM names will be kept in a string. "Shorten name" was called in Standard to Model network conversion to convert it to a string field.

[yuqiww]

This issue is partly resolve by methods.determine_road_name().