<?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: Combine turn features in a network dataset in ArcGIS Network Analyst Questions</title>
    <link>https://community.esri.com/t5/arcgis-network-analyst-questions/combine-turn-features-in-a-network-dataset/m-p/624008#M5975</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;First, let me make sure I properly understand your situation. &lt;/SPAN&gt;&lt;BR /&gt;&lt;UL&gt;&lt;BR /&gt;&lt;LI&gt;You have a primary turns feature class (let's call this class "A") which you intend to represent "restricted turns" for cars.&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;You have a secondary turns feature class (let's call this class "B") which you intend to represent "allowed (i.e., non-restricted) turns" for cyclists.&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;The turn features from class B are a subset of turn features from class A.&lt;/LI&gt;&lt;BR /&gt;&lt;/UL&gt;&lt;BR /&gt;&lt;SPAN&gt;Is this correct? If so, then the answer to your question is: yes, you can support this intended functionality. However, not in the way in which you are likely thinking.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;One way to support this would be as follows:&lt;/SPAN&gt;&lt;BR /&gt;&lt;OL&gt;&lt;BR /&gt;&lt;LI&gt;On your primary turns feature class (class A), add a new field called something like "Cyclist_Restricted" to represent whether a cyclist is restricted by this turn. The field can be of type short integer, and will only hold the values of 1 or 0 to represent logical true or false, respectively. Default all field values to 1 for true.&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;For each turn feature in class A, if that turn feature also appears in class B, then change its "Cyclist_Restricted" field value to 0 (since you wish to "allow" these turns for cyclists, if they appear in class B).&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;Add the turns class A to your network dataset (do not add turns class B, as you will no longer need it).&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;Create two new restriction attributes on your network dataset: one called "Vehicles Restricted" and one called "Cyclists Restricted" (or something like that).&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;For the "Vehicles Restricted" attribute, for your turns class A, setup a constant evaluator with a value of "Restricted".&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;For the "Cyclists Restricted" attribute, for your turns class A, setup a field evaluator which reads the newly-added "Cyclist_Restricted" field of class A and returns "Traversable" (i.e., false) for a field value of 0 and "Restricted" (i.e., true) for a field value of 1.&lt;/LI&gt;&lt;BR /&gt;&lt;/OL&gt;&lt;BR /&gt;&lt;SPAN&gt;This allows you to use and manage only one turns feature class. Now, during your analysis, when you are solving a route for a vehicle, then you should make sure to turn on the "Vehicles Restricted" restriction attribute (while turning off the "Cyclists Restricted" attribute), and vice-versa when you are solving for a cyclist.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Does this help? Let me know if you have any further questions about this.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 01 Jun 2010 21:18:26 GMT</pubDate>
    <dc:creator>MichaelRice</dc:creator>
    <dc:date>2010-06-01T21:18:26Z</dc:date>
    <item>
      <title>Combine turn features in a network dataset</title>
      <link>https://community.esri.com/t5/arcgis-network-analyst-questions/combine-turn-features-in-a-network-dataset/m-p/624007#M5974</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Does anyone know if it is possible to combine two turn feature classes to obtain one condition for turning?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;My example: I have one turn feature class for cars. Another turn feature class for cyclists only contains features for situations where cyclists are excepted from the car's restriction. With other words: Cyclists are restricted for all turn feautures off the car's turn feature, but if a cyclist's turn feature exists on the some spot, the cyclists are allowed to turn.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there a solution with an evaluator script?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks in advance,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 May 2010 09:59:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-network-analyst-questions/combine-turn-features-in-a-network-dataset/m-p/624007#M5974</guid>
      <dc:creator>AxelJodry</dc:creator>
      <dc:date>2010-05-31T09:59:46Z</dc:date>
    </item>
    <item>
      <title>Re: Combine turn features in a network dataset</title>
      <link>https://community.esri.com/t5/arcgis-network-analyst-questions/combine-turn-features-in-a-network-dataset/m-p/624008#M5975</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;First, let me make sure I properly understand your situation. &lt;/SPAN&gt;&lt;BR /&gt;&lt;UL&gt;&lt;BR /&gt;&lt;LI&gt;You have a primary turns feature class (let's call this class "A") which you intend to represent "restricted turns" for cars.&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;You have a secondary turns feature class (let's call this class "B") which you intend to represent "allowed (i.e., non-restricted) turns" for cyclists.&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;The turn features from class B are a subset of turn features from class A.&lt;/LI&gt;&lt;BR /&gt;&lt;/UL&gt;&lt;BR /&gt;&lt;SPAN&gt;Is this correct? If so, then the answer to your question is: yes, you can support this intended functionality. However, not in the way in which you are likely thinking.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;One way to support this would be as follows:&lt;/SPAN&gt;&lt;BR /&gt;&lt;OL&gt;&lt;BR /&gt;&lt;LI&gt;On your primary turns feature class (class A), add a new field called something like "Cyclist_Restricted" to represent whether a cyclist is restricted by this turn. The field can be of type short integer, and will only hold the values of 1 or 0 to represent logical true or false, respectively. Default all field values to 1 for true.&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;For each turn feature in class A, if that turn feature also appears in class B, then change its "Cyclist_Restricted" field value to 0 (since you wish to "allow" these turns for cyclists, if they appear in class B).&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;Add the turns class A to your network dataset (do not add turns class B, as you will no longer need it).&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;Create two new restriction attributes on your network dataset: one called "Vehicles Restricted" and one called "Cyclists Restricted" (or something like that).&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;For the "Vehicles Restricted" attribute, for your turns class A, setup a constant evaluator with a value of "Restricted".&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;For the "Cyclists Restricted" attribute, for your turns class A, setup a field evaluator which reads the newly-added "Cyclist_Restricted" field of class A and returns "Traversable" (i.e., false) for a field value of 0 and "Restricted" (i.e., true) for a field value of 1.&lt;/LI&gt;&lt;BR /&gt;&lt;/OL&gt;&lt;BR /&gt;&lt;SPAN&gt;This allows you to use and manage only one turns feature class. Now, during your analysis, when you are solving a route for a vehicle, then you should make sure to turn on the "Vehicles Restricted" restriction attribute (while turning off the "Cyclists Restricted" attribute), and vice-versa when you are solving for a cyclist.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Does this help? Let me know if you have any further questions about this.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Jun 2010 21:18:26 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-network-analyst-questions/combine-turn-features-in-a-network-dataset/m-p/624008#M5975</guid>
      <dc:creator>MichaelRice</dc:creator>
      <dc:date>2010-06-01T21:18:26Z</dc:date>
    </item>
    <item>
      <title>Re: Combine turn features in a network dataset</title>
      <link>https://community.esri.com/t5/arcgis-network-analyst-questions/combine-turn-features-in-a-network-dataset/m-p/624009#M5976</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This is exactly wath I needed! I didn't realise I could add information to a turn table and use it in a condition.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Meanwhile, I discovered that if I have to turn features (from two different feature classes) on the same place, one is defined as a constant restricted turn and the other as a constant traversable turn, the additional value is traversable. Logically, i didn't expect it, but it suits me well in my case. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But I think that your method is working better and is easier to modify.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks a lot,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jun 2010 07:32:29 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-network-analyst-questions/combine-turn-features-in-a-network-dataset/m-p/624009#M5976</guid>
      <dc:creator>AxelJodry</dc:creator>
      <dc:date>2010-06-04T07:32:29Z</dc:date>
    </item>
  </channel>
</rss>

