<?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 BUG: calculating Impedance Attributes in ArcGIS Network Analyst Questions</title>
    <link>https://community.esri.com/t5/arcgis-network-analyst-questions/bug-calculating-impedance-attributes/m-p/582164#M5603</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ArcMap 10.6&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We&amp;nbsp;are attempting to create a network with a variety a&amp;nbsp;of impedance attributes that are quite similar, but with a varying constant that is input to a formula. To do this we are making impedance attributes, then varying the constant for each attribute, from 0 to 100 in increments of 10. In total (with other attributes on the network) there are 86 impedance attributes/restrictions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We started off with the attribute calculation in Python. The bug is that Network Analyst&amp;nbsp;seems to&amp;nbsp;seriously mess up the calculation - see attached image, where the left land part shows the values calculated for a link by NA (R_000 through to R_100, while the right hand part shows the values calculated for the same link directly in Python (with 0.0 equivalent to R_000 and 1.0 equivalent to R_100, and intermediate values).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NA has calculated the first value correctly, but the second value (R_010)&amp;nbsp;is incorrectly calculated as 0, then the following results are somehow shifted - the result that should be for R_010 has been assigned to R_020, and so on, with the value of R_100 having the value that should belong to R_090. Over numerous trial and error iterations the issue/offset is inconsistent - in some builds there might be multiple attributes affected, rather than just one, and the actual effect can vary, from the erroneous values being set&amp;nbsp;to 0 or being set to some other, but incorrect value, such as 5.321651&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Moving the calculations from Python to VBS did not alter the issue. The only solution we have found is to create/edit the desired attributes, build the network, then add a pointless additional attribute with constant value, i.e. 0, and then build the network again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 10 Oct 2018 21:55:12 GMT</pubDate>
    <dc:creator>Stacy-Rendall</dc:creator>
    <dc:date>2018-10-10T21:55:12Z</dc:date>
    <item>
      <title>BUG: calculating Impedance Attributes</title>
      <link>https://community.esri.com/t5/arcgis-network-analyst-questions/bug-calculating-impedance-attributes/m-p/582164#M5603</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ArcMap 10.6&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We&amp;nbsp;are attempting to create a network with a variety a&amp;nbsp;of impedance attributes that are quite similar, but with a varying constant that is input to a formula. To do this we are making impedance attributes, then varying the constant for each attribute, from 0 to 100 in increments of 10. In total (with other attributes on the network) there are 86 impedance attributes/restrictions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We started off with the attribute calculation in Python. The bug is that Network Analyst&amp;nbsp;seems to&amp;nbsp;seriously mess up the calculation - see attached image, where the left land part shows the values calculated for a link by NA (R_000 through to R_100, while the right hand part shows the values calculated for the same link directly in Python (with 0.0 equivalent to R_000 and 1.0 equivalent to R_100, and intermediate values).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NA has calculated the first value correctly, but the second value (R_010)&amp;nbsp;is incorrectly calculated as 0, then the following results are somehow shifted - the result that should be for R_010 has been assigned to R_020, and so on, with the value of R_100 having the value that should belong to R_090. Over numerous trial and error iterations the issue/offset is inconsistent - in some builds there might be multiple attributes affected, rather than just one, and the actual effect can vary, from the erroneous values being set&amp;nbsp;to 0 or being set to some other, but incorrect value, such as 5.321651&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Moving the calculations from Python to VBS did not alter the issue. The only solution we have found is to create/edit the desired attributes, build the network, then add a pointless additional attribute with constant value, i.e. 0, and then build the network again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Oct 2018 21:55:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-network-analyst-questions/bug-calculating-impedance-attributes/m-p/582164#M5603</guid>
      <dc:creator>Stacy-Rendall</dc:creator>
      <dc:date>2018-10-10T21:55:12Z</dc:date>
    </item>
  </channel>
</rss>

