<?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: Network Analyst not solving for actual Closest Facility in ArcGIS Network Analyst Questions</title>
    <link>https://community.esri.com/t5/arcgis-network-analyst-questions/network-analyst-not-solving-for-actual-closest/m-p/16380#M206</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nvmind. Found out the flaw. There was an overlapping Express route on the built network to the south, which was a very long segment whose length was fully counted in the impedance. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 06 May 2018 00:49:13 GMT</pubDate>
    <dc:creator>MalcolmLittle</dc:creator>
    <dc:date>2018-05-06T00:49:13Z</dc:date>
    <item>
      <title>Network Analyst not solving for actual Closest Facility</title>
      <link>https://community.esri.com/t5/arcgis-network-analyst-questions/network-analyst-not-solving-for-actual-closest/m-p/16378#M204</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm running a Closest Facility function within Network Analyst. I'm looking for the shortest route from Incidents to Facilities. After loading the datasets and running it under mostly default options, a few of the output choices are obviously incorrect: see attached picture of one example where the closest chosen is incorrect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What could be causing such incorrect choices within the analysis?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 May 2018 22:47:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-network-analyst-questions/network-analyst-not-solving-for-actual-closest/m-p/16378#M204</guid>
      <dc:creator>MalcolmLittle</dc:creator>
      <dc:date>2018-05-05T22:47:45Z</dc:date>
    </item>
    <item>
      <title>Re: Network Analyst not solving for actual Closest Facility</title>
      <link>https://community.esri.com/t5/arcgis-network-analyst-questions/network-analyst-not-solving-for-actual-closest/m-p/16379#M205</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are going to have to elaborate on 'mostly defaults'.&lt;/P&gt;&lt;P&gt;why are the facilities so far from the network?&lt;/P&gt;&lt;P&gt;has the network been checked for flaws?&lt;/P&gt;&lt;P&gt;any limitations on the network? (one-way, turn restrictions etc)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 May 2018 23:25:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-network-analyst-questions/network-analyst-not-solving-for-actual-closest/m-p/16379#M205</guid>
      <dc:creator>DanPatterson_Retired</dc:creator>
      <dc:date>2018-05-05T23:25:23Z</dc:date>
    </item>
    <item>
      <title>Re: Network Analyst not solving for actual Closest Facility</title>
      <link>https://community.esri.com/t5/arcgis-network-analyst-questions/network-analyst-not-solving-for-actual-closest/m-p/16380#M206</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nvmind. Found out the flaw. There was an overlapping Express route on the built network to the south, which was a very long segment whose length was fully counted in the impedance. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 06 May 2018 00:49:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-network-analyst-questions/network-analyst-not-solving-for-actual-closest/m-p/16380#M206</guid>
      <dc:creator>MalcolmLittle</dc:creator>
      <dc:date>2018-05-06T00:49:13Z</dc:date>
    </item>
  </channel>
</rss>

