Approach

Inputs

  • HERE links shapfile

    • Attributes of relevance:

      • LINK_ID (link ID)
      • REF_IN_ID (reference node ID)
      • NREF_IN_ID (nonreference node ID)
      • DIR_TRAVEL (b=both, t=to reference node, f=from reference node)

  • HERE link pattern lookup tables (60 minute)

    • Attributes of relevance:

      • LINK_PVID (link ID)
      • TRAVEL_DIRECTION (TRUE=to reference node, FALSE=from reference node)
      • W (Wednesday pattern profile, joins to PATTERN_ID)

  • HERE speed profile lookup table (60 minute, mph)

    • Attributes of relevance:

      • PATTERN_ID (joins to W, or any day of week)
      • H17_00 (mph for 5pm)

Analysis

  • Join Link Lookup-Speed Lookup - Left join speed profile lookup (5pm mph value) to link pattern lookup (for Wednesday)

    • This results in Wednesday 5pm mph value for each link (2 rows per link if both directions, 1 row per link of T or F)

  • Join Link Shapefile to Joined Speed-Link Lookup – Right join link lookup table w/ speed information to link shapefile by LINK_PVID/LINK_ID

    • This brings in speed attribute for each link, and duplicates links that appear more than once due to bi-directional service
    • QC check-confirmed that HERE link shapefile DIR_TRAVEL attributes (“T” and “F”) match TRAVEL_DIRECTION (TRUE, FALSE) attributes from link lookup table

  • Modify link attributes for one-way network building

    • In rows where DIR_TRAVEL is “B”(for both directions), value is changed to “T” or “F” to match TRUE or FALSE corresponding value from lookup table

      • All edges are either “to” or “from” perspective, no “both” links exist.

    • To simplify ArcPro network build, all “to” perspectives are changed to “from” perspectives, and the values in the corresponding REF_IN_ID and NREF_IN_ID columns are switched.

      • This creates a shapefile of edges that are all one direction of travel in the same direction.
      • Note, the mapped version below does not include this step, so that it was possible to offset lines.

Resting Network Proof of Concept

  1. Renaissance Planning, ↩︎