<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Capturing Lane Type information in Roads and Highways User Group (RHUG) Questions</title>
    <link>https://community.esri.com/t5/roads-and-highways-user-group-rhug-questions/capturing-lane-type-information/m-p/1131045#M591</link>
    <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/477457"&gt;@Colin_Schut&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This might not be what you are looking for but esri provides very good solutions.&lt;BR /&gt;&lt;A href="https://doc.arcgis.com/en/arcgis-solutions/latest/reference/introduction-to-road-network-data-management.htm" target="_blank"&gt;https://doc.arcgis.com/en/arcgis-solutions/latest/reference/introduction-to-road-network-data-management.htm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 05 Jan 2022 23:20:58 GMT</pubDate>
    <dc:creator>RickeyFight</dc:creator>
    <dc:date>2022-01-05T23:20:58Z</dc:date>
    <item>
      <title>Capturing Lane Type information</title>
      <link>https://community.esri.com/t5/roads-and-highways-user-group-rhug-questions/capturing-lane-type-information/m-p/1131039#M590</link>
      <description>&lt;P&gt;To date the only lane information we've tracked is the "number of lanes", which is an attribute for Canada's National Road Network but doesn't provide us with much value.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am wondering how best to model lane information in a simple way. The short term suggestion has been to add a comment field to the feature class, and while keeping in mind the vast majority of our network is two lane highways with the occasional passing lane, I still see major issues at intersections where the records aren't currently split and inaccuracies over time if we stuck with it.&lt;/P&gt;&lt;P&gt;I'm considering a cross sectional position table with attributes for Lanes like L1/L2/L3/L4 with the type of lane in each, and the number of lanes can then be derived. At least this way new records don't outdate adjacent records.&lt;/P&gt;&lt;P&gt;We will never have routes for each lane,&amp;nbsp; and having a feature class per lane would probably be overkill as well. How do you model this?&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jan 2022 22:58:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/roads-and-highways-user-group-rhug-questions/capturing-lane-type-information/m-p/1131039#M590</guid>
      <dc:creator>Colin_Schut</dc:creator>
      <dc:date>2022-01-05T22:58:37Z</dc:date>
    </item>
    <item>
      <title>Re: Capturing Lane Type information</title>
      <link>https://community.esri.com/t5/roads-and-highways-user-group-rhug-questions/capturing-lane-type-information/m-p/1131045#M591</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/477457"&gt;@Colin_Schut&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This might not be what you are looking for but esri provides very good solutions.&lt;BR /&gt;&lt;A href="https://doc.arcgis.com/en/arcgis-solutions/latest/reference/introduction-to-road-network-data-management.htm" target="_blank"&gt;https://doc.arcgis.com/en/arcgis-solutions/latest/reference/introduction-to-road-network-data-management.htm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jan 2022 23:20:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/roads-and-highways-user-group-rhug-questions/capturing-lane-type-information/m-p/1131045#M591</guid>
      <dc:creator>RickeyFight</dc:creator>
      <dc:date>2022-01-05T23:20:58Z</dc:date>
    </item>
    <item>
      <title>Re: Capturing Lane Type information</title>
      <link>https://community.esri.com/t5/roads-and-highways-user-group-rhug-questions/capturing-lane-type-information/m-p/1131140#M592</link>
      <description>&lt;P&gt;Colin,&lt;/P&gt;&lt;P&gt;We model that information as events and have split them out among many feature classes to account for the way each attribute can and do change for the level of detail we want. The bold is the feature class name and then fields for each. Lane miles is a post process calculated field in our publication data.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;LRSE_LaneWidth&lt;/STRONG&gt; LaneWidth&lt;BR /&gt;&lt;STRONG&gt;LRSE_Surface&lt;/STRONG&gt; SurfaceDetail SurfaceThickness SurfaceType SurfaceWidth&lt;BR /&gt;&lt;STRONG&gt;LRSE_ThroughLane&lt;/STRONG&gt; LaneMiles ThroughLaneCount&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;LRSE_LeftShoulder&lt;/STRONG&gt; LeftPavedShoulderWidth LeftShoulderWidth LeftShoulderType&lt;BR /&gt;&lt;STRONG&gt;LRSE_LeftTurnLane&lt;/STRONG&gt; LeftTurnLaneType LeftTurnLaneWidth&lt;BR /&gt;&lt;STRONG&gt;LRSE_RightShoulder&lt;/STRONG&gt; RightPavedShoulderWidth RightShoulderWidth RightShoulderType&lt;BR /&gt;&lt;STRONG&gt;LRSE_RightTurnLane&lt;/STRONG&gt; RightTurnLaneType RightTurnLaneWidth&lt;BR /&gt;&lt;STRONG&gt;LRSE_Median&lt;/STRONG&gt; MedianType MedianWidth&lt;BR /&gt;&lt;STRONG&gt;LRSE_Base&lt;/STRONG&gt; BaseDetail BaseThickness&lt;/P&gt;&lt;P&gt;Here is the link for the metadata for each field. &lt;A href="https://xfer.services.ncdot.gov/gisdot/DistDOTData/NCDOTRouteCharacteristicsFieldDescriptions.pdf" target="_blank"&gt;https://xfer.services.ncdot.gov/gisdot/DistDOTData/NCDOTRouteCharacteristicsFieldDescriptions.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Probably more then it seems you want to do but simple to us/me and basically what we have used for the past 15 years. We can discuss more in-depth you if want.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jan 2022 11:46:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/roads-and-highways-user-group-rhug-questions/capturing-lane-type-information/m-p/1131140#M592</guid>
      <dc:creator>RyanKoschatzky</dc:creator>
      <dc:date>2022-01-06T11:46:18Z</dc:date>
    </item>
  </channel>
</rss>

