<?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: NextDownID = -1 but not outlet in Water Resources Questions</title>
    <link>https://community.esri.com/t5/water-resources-questions/nextdownid-1-but-not-outlet/m-p/715678#M3654</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have found the problem. It has something to do with my installation of Arc Hydro (ArcGIS 9.3.1) becasue when I ran my data on another computer and it worked just fine!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 09 Jul 2013 17:19:11 GMT</pubDate>
    <dc:creator>BastianSchmidt</dc:creator>
    <dc:date>2013-07-09T17:19:11Z</dc:date>
    <item>
      <title>NextDownID = -1 but not outlet</title>
      <link>https://community.esri.com/t5/water-resources-questions/nextdownid-1-but-not-outlet/m-p/715672#M3648</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I've built my network; set my flow direction; asigned HydroIDs to my pts, net_junctions &amp;amp; lines; run the From/To nodes for the lines; and lastly NextDownID for the lines. I have 57 line segments with -1 as the NextDownID. I only have one true outlet for the network. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have no disconnections in the network when I run a trace.&amp;nbsp; All of the From/To Node fields are populated and have the correct HydroID for the next downstream segment. The segments with the -1's are not endpoints but a segment within the total stream length. Unfortunately, this is a fairly large network and takes four hours to run the NextDownID, so it's not an easy test for fixes unless I break out a portion of the network and test on it. I have disconnected the network, stripped out all Hydro/JunctionIDs, and rerun from scratch to see if I missed a step.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any suggestions are appreciated!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 May 2013 14:12:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/water-resources-questions/nextdownid-1-but-not-outlet/m-p/715672#M3648</guid>
      <dc:creator>MichelleTischler</dc:creator>
      <dc:date>2013-05-29T14:12:10Z</dc:date>
    </item>
    <item>
      <title>Re: NextDownID = -1 but not outlet</title>
      <link>https://community.esri.com/t5/water-resources-questions/nextdownid-1-but-not-outlet/m-p/715673#M3649</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;-1 gets assigned to the lines having a TO_NODE that is not assigned to any FROM_NODE. If you look at your lines having NEXTDOWNID=-1 and check their TO_NODE field, can you find other lines having these values in their FROM_NODE field?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Christine Dartiguenave&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Esri Water Resources Team&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 May 2013 22:39:34 GMT</pubDate>
      <guid>https://community.esri.com/t5/water-resources-questions/nextdownid-1-but-not-outlet/m-p/715673#M3649</guid>
      <dc:creator>ChristineDartiguenave</dc:creator>
      <dc:date>2013-05-29T22:39:34Z</dc:date>
    </item>
    <item>
      <title>Re: NextDownID = -1 but not outlet</title>
      <link>https://community.esri.com/t5/water-resources-questions/nextdownid-1-but-not-outlet/m-p/715674#M3650</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am experiencing a slightly different yet similar problem with the NextDownID. The entire field (i.e all records) are calculated as -1. I am trying to experimentally introduce "links" into the network (i.e. extra links inbetween confluence points, or non-confluence links) at the raster level. This seems to work upto the NextDownID generation process. My DrainageLines have TO_ and FROM_NODES and they do match up (i.e. the TO_NODE = the FROM NODE of the next downstream line).&amp;nbsp; Is there any other conditions that might result in -1 being calulated for all DrainageLines?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jul 2013 18:16:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/water-resources-questions/nextdownid-1-but-not-outlet/m-p/715674#M3650</guid>
      <dc:creator>BastianSchmidt</dc:creator>
      <dc:date>2013-07-02T18:16:53Z</dc:date>
    </item>
    <item>
      <title>Re: NextDownID = -1 but not outlet</title>
      <link>https://community.esri.com/t5/water-resources-questions/nextdownid-1-but-not-outlet/m-p/715675#M3651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;What is the type of the FROM_NODE and TO_NODE fields?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If you copy the stream feature class and build a join between the original stream and the new feature class using FROM_NODE/TO_NODE, are the records successfully joined?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Christine Dartiguenave&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Esri Water Resources Team&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jul 2013 14:28:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/water-resources-questions/nextdownid-1-but-not-outlet/m-p/715675#M3651</guid>
      <dc:creator>ChristineDartiguenave</dc:creator>
      <dc:date>2013-07-03T14:28:05Z</dc:date>
    </item>
    <item>
      <title>Re: NextDownID = -1 but not outlet</title>
      <link>https://community.esri.com/t5/water-resources-questions/nextdownid-1-but-not-outlet/m-p/715676#M3652</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Christine,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The TO_ and FROM_NODE fields are of the LONG [Integer] data type. The "Join" test you suggested is also successful. I have also written an MS-Excel macro to perform the NextDownID attribution and it works with a few exception where network discontinuities exist.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jul 2013 15:11:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/water-resources-questions/nextdownid-1-but-not-outlet/m-p/715676#M3652</guid>
      <dc:creator>BastianSchmidt</dc:creator>
      <dc:date>2013-07-03T15:11:48Z</dc:date>
    </item>
    <item>
      <title>Re: NextDownID = -1 but not outlet</title>
      <link>https://community.esri.com/t5/water-resources-questions/nextdownid-1-but-not-outlet/m-p/715677#M3653</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I would need to check your data to try to figure out what is going on. Can you post it?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Christine&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jul 2013 21:19:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/water-resources-questions/nextdownid-1-but-not-outlet/m-p/715677#M3653</guid>
      <dc:creator>ChristineDartiguenave</dc:creator>
      <dc:date>2013-07-03T21:19:27Z</dc:date>
    </item>
    <item>
      <title>Re: NextDownID = -1 but not outlet</title>
      <link>https://community.esri.com/t5/water-resources-questions/nextdownid-1-but-not-outlet/m-p/715678#M3654</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have found the problem. It has something to do with my installation of Arc Hydro (ArcGIS 9.3.1) becasue when I ran my data on another computer and it worked just fine!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Jul 2013 17:19:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/water-resources-questions/nextdownid-1-but-not-outlet/m-p/715678#M3654</guid>
      <dc:creator>BastianSchmidt</dc:creator>
      <dc:date>2013-07-09T17:19:11Z</dc:date>
    </item>
  </channel>
</rss>

