Trace Network in ArcGIS Pro 2.6

Video Transcript
Download Video
Right-click and save to download

Detailed Description

Hayley Thompson - USGS Hydrography Researcher (NGTOC, Topographic Applied Research Section (TARS)) gives a gentle introduction to the Trace Network in ArcGIS Pro 2.6 and how you can use it with NHD data.

Topics include:

  • What is Trace Network.
  • Creating and enabling a Trace Network
  • Performing a simple trace using Trace Network
  • Additional information
  • Resources and questions

Links to supportive resources:

Details

Date Taken:

Length: 00:50:22

Location Taken: Reston, VA, US

Transcript

Actually, I think we will go ahead and get started. And hopefully everybody seeing the. Age then sharing right now. The newsletter for. This past month or last couple of months actually just went out. Should have it in your email. I wanted to talk just a little bit about that before we get into our main presentation for the day, so we've just changed the way that we're handling both the newsletter an the calendar invitations for this call the advisory call. And we're using a listserv for it now, so you'll be able to manage your own subscriptions to to the newsletter in this advisory call calendar invitations. Through this listserv. So there are couple of ways you can get to it. You can get to it from this link here in the newsletter that just went out today. And it will take you to this page. If you got the invitation for this calendar, the calendar invitation for this, and let's see, I'm getting a bunch of background noise, so I'm going to meet all. And. That way will hopefully not not get the. Background noise. Anyway, so if you want to add yourself to the newsletter list, you can do that here on this on this page. Just put in your email address and your name here. If you want to unsubscribe, you can do that here as well. You can just put your email in here and and hit the unsubscribe button. And you be unsubscribed from the list. We used to maintain the the list for the advisory call and for the newsletter separately, but with this change changing over to this listserv, it's only going to be one list, so you'll just get you'll get the calendar invitations and the newsletter once a month on once a month, each on this on this listserv. I would suggest that you not use the digest option, so there's really no need for you to know. We added everybody to the list. Everybody that was on our list already. We've added everyone to this listserv, assigned you a random password. You can request that password through this form, but there's really no need for you to have that password. The only. Thing you really need to be able to do is unsubscribe if you want to stop getting the emails in the calendar invites. I suggest not using. There is a digest option that will pause and not send you the email right away. It'll only send it once a day or once a week, depending on how you how you set that, but we don't send a lot of emails to this list. It's going to be really just a couple a month. You know an email for the newsletter and once a month for the advisory call and the calendar invitations and we want you to be able to get the calendar invitations updated. For example, if we need to send out an update right away on the day of the call, we wouldn't want you to miss that because you had set it to digest mode, so that's that's that the newsletter is out. And it's a new format with. With this new look and feel, there's an article here that you can read about more about that, and it will also describe how to do the subscriptions. There's this page which you can link to here, which I've already opened here, which is the newsletter page. This will always be where you can go to get the most current newsletter. You can also see the archived previous versions of the newsletter. We've got archive going all the way back, I think to 2001, so we have almost 20 years here of the newsletters from from the NHD program. An oh I wanted to mention the subscribe button here with the email with the little envelope on it. You can subscribe and that'll that'll take you back to that page that I just showed you. And that's that's just manage in that list serve. You can also subscribe with RSS, but we don't recommend that you do that because that won't put you on our mailing list. And you won't. You won't get the calendar invitations for the advisor call or anything. If you do that, if you know what RSS is all about. That presumably works, but no guarantees. None of us really use that so. Know how to... how to manage RSS so it's there but You're on your own there. I also just mentioned here you can you can see you can get all our emails, an connection information. The general email for support is NHD@usgs.gov or if you can reach out to one of us individually. If you if you want to. And so that's all I wanted to cover about this. To begin with, I'm going to stop sharing my screen. And yes, Hi. There's a question in the chat kind of relevant to this topic. I don't know if you want to address that now or later. OK, sure, but from Danielle and so for this. Yeah, right. So yes, when we added everyone to the list from our from our old list which was on this spreadsheet. The software of assigned everybody a password. We don't know what the password is. If you want to find out, you can go into that listserv and On that, On that page you can find out, but there really isn't much need for you to do that. Because the only thing the password would let you do would be just set options to digest mode, which is not really recommending that you do that. But if you if you go in here, put your email in here, one of the options you get is to have it send you your password. It will send the password in free text in an email, so it's not secure. So we don't really recommend that you do that, but that's that will be the way it works. It's a very pretty simple thing. OK, and with that Hayley Hayley Thompson is going to give our presentation today. Hayley, you can go ahead and share your screen. So Hayley's going to talk about the Trace network in Arcgis Pro. We had a presentation about from ESRI a few months ago. It was sort of still not. It was still in beta at that time and Hayley's going to give you sort of just a very easy introduction to the Trace network in Arcgis Pro. How that works and how you can use it within NHD data. So Hayley, you might have to unmute yourself or you can go ahead. Alright, can you hear me and see my screen? Yes. Hi everybody as Al mentioned, my name is Hayley Thompson. I am a Hydrography Researcher in the Topographic Applied Research Section at the National Geospatial Technical Operations Center. And that is quite a mouthful. But today, as Al mentioned also, I'm going to be giving you a look today at how to utilize Trace Network build and perform a simple trace using one of our NHD datasets. It's just a quick outline of the main topics I'm going to go over today. First, I'm going to give you a definition of what is Trace Network. We're going to go over, how to create and enable a trace network, and then perform a simple trace as well as any additional information and resources. And finally, I believe we should have time at the end for any questions anyone might have. Now quick disclaimer here. USGS product names. Disclaimer down here at the bottom. Any use of trade, firm or product names is for descriptive purposes only and does not imply endorsement by the US government. And before we get too far into how to build and enable and then run the trace network I want to give you this simple definition here. So Trace Network is a tool box that was released in the ArcGIS Pro version 2.6 that is used to return selected features based on connectivity or traversability from specified starting points in a network. So overall this tool box is supposed to allow users to analyze pass within a network. This is an example of the trace here. So this process of creating, enabling and tracing it can be fairly easy and there are two main avenues a user can go about when choosing to create a trace network, so you can do this by converting a geometric network to a trace network or by creating a trace network from scratch. So is especially useful as a lot of our product's currently for the NHD and NHD Plus High Resolution are still being distributed with geometric networks, so it's very easy in Arcgis Pro especially to just be able to convert that. And use it as a trace network without having to delete and recreate. However, both of these methods do exist within Arcgis Pro 2.6 and will continue to exist onward for this forseeable future, as far as we're aware. So regardless of which Avenue you choose to create a trace network from, you then have to enable network topology before being able to trace, and I'll show you kind of why that's important in a later slide and then the last step is to trace the network. And again I will also be showing you how to do that in a later slide. So these are just the essentials in creating a trace network. You will see that there are other tools available here. We're not really going to be covering them in this demonstration. However, if you want to create a more complex network, you can do so by adding in details such as network attributes and setting flow direction. After creating a trace network, what do you get? So this slide here demonstrates the network utilities as feature classes in your map that are a result of creating a trace network, and these layers are very informative in a lot of ways, so you get a point error layer which manages any errors within any point feature class that you include in your trace network. I do not have any point feature classes included in my Network I'm going to be using in this demonstration, however, I did want to point out that this can be a useful tool in. This will appear on your map if you choose to use so and have meters. We also have the line error layer which manages any errors within any line feature class in a network; System. Junctions which show all points where two or more vertices meet between two different segments of the network. So any flow line that touches another flow line you will get one of these system junctions. And finally you also have Dirty Areas which when you enable the network dirty areas are generated for features where the geometry edits have been made after creating a trace network. Or where errors exist in either your point or line error feature classes. So this is the first stage after you would run either creating a trace network from scratch or converting a trace network. This will. This will be what appears in your map and this is a reminder that you have not yet enabled network topology on your trace network. So at this stage The Dirty area that purple box. is not specific to the errors as it is intended to kind of be, but is instead of the full extent of the map. And this is also the stage where after you create trace network, if you wanted a more complex network you could add in network attributes or if you have any geometry errors that need to be addressed or you would like to modify the geometry of your network in any way, you would do that before you enable the geometry of your network. So after enabling a network and creating it, you get this kind of layout here. This is what you'll see. It will zoom in to your VPU you or your NHD data set and you will also start to see if you have any line errors or point error features as well as the smaller dirty areas such as right here which surround any errors that you might have. So what I'm showing in this subset of this whole network here is one of the line errors and dirty area combinations that I have as a result of creating an enabling my network. This error is an example of one of the side. I would say side effects. It's kind of a byproduct of using Trace network with NHD or NHDPlus high resolution products and in your attribute table which if we have time at the end I can show you in greater detail what this looks like in a Pro session. Mine was acting up a little bit this morning so I wanted to make sure I could show you this time so I included it here and this is what's going to be called a duplicate vertex error. It is the most common one you'll see. Trace Network with the NHD or NHDPlus high resolution products. It is not a really true error on the part of either Trace network or the NHD or NHDPlus High Resolution products. It relates to the database tolerances that ESRI has and the database tolerances that we use when creating our data. So if you were to zoom in and I can show you this at the end as well, it would appear as if there was a duplicate vertice right on this end point right here. It is not. They're just too close together. These vertexes for that trace network tool to accurately distinguish them from each other. There is a way to instead of having to go in and edit each of these, to trace around them and that's what I'm going to be showing you today. So before I show you that I would like to show you how to set up a simple trace. So before we use the trace tool within the Trace network toolbox. We do have to add a starting point to the map or starting points depending on which kind of trace you would like to use, which can be accessed on a trace network toolbar up at the top here. This toolbar is automatically added to an Arcgis Pro session and can be accessed when you have an active trace network in your map. so you don't have to worry about adding this in as a separate step. If you have a trace network in your job drawing order of your map, this tool box will automatically be available. So the first thing you do is there is this option here for trace locations up here at the top. select that and this window here pops up. And from there he choose the add features option and select somewhere on the map. So the user can add as many starting points on a map as you would like to trace at any location on a line segment. It's not particularly picky where you put these starting points. Just note that even if you place it in the middle of a line segment or like I did hear it and put it directly on this this junction. Um? It will still trace that entire flow line in your trace once you get to that step. I also do want to note here that also in trace locations there is an option to use barrier's. I'm not going to be using any barriers in this trace, but. This is a good example of how you might want to create any more complex network, such as if a damn existed and you didn't want to trace. Let's say you were starting up here upstream, but that damn existed right here and you didn't want to include that section. You could place a barrier and then trace the section would be excluded. It would recognize that barrier. So last step before tracing is using the trace tool itself. So once you've established the starting points, you're going to go and open the trace tool from the Trace network tool box and then you would go. This is the geoprocessing window that you would see over here on the right. And you're going to verify or add in inputs here, so all of these are default. It automatically recognizes if you have a trace network in your window. If you do have multiple, you do want to verify that it has selected the correct one. There are four types of traces you can perform for the purposes of this, I'm going to use downstream, but you can also use upstream connected or shortest path. No, they said they were going to downstream for this trace. For starting point, this is a default. You set this up in the previous step. It's a temporary file that is automatically placed into the tool based on which starting points you choose from the map and additionally it does the same thing for barriers. If you placed any barriers, it automatically has this temporary file and will. add to the tool for you. There are some advanced options. I'll show you them a little bit later on. We're not going to go in how to trace with them necessarily. But I will show you kind of what some options are. If you do want to create a more complex network. And then the last step down here at the bottom you would just run the tool. So with that error feature in mind and that data set that I showed you earlier, this is the first thing that you would get. So if there are any errors as part of the trace, this error message here will pop up and say one or more dirty areas were discovered and that trace will appear to fail. So in order to trace through these errors anyway, there is an option that was added called validate consistency. So by default this box is checked, but if you wanted to trace through these errors anyway, there's are known errors within the NHD and NHDPlus High Resolution data set when using Trace network you would have to uncheck that box and then those errors would be ignored. So once I uncheck that box, rerun the step that trace is successful, you see it trace downstream from my starting point up here and the data is now included. Again, this is by default checked on, so one of the first steps or one of the last steps before running the Trace tool would be to uncheck that box if you know that you have a known error, you're going to be tracing through. So as I mentioned, there are some more advanced options you can use when performing a trace. I'm not going to be showing you how to use those unless we have time and interest. Maybe at the end we can get into them a little bit more, but. Um? There again, a couple of these advanced options so we have function barriers. A good use for function barrier might be if you want to restrict how far the trace can travel. You only want to know a set distance downstream or upstream. That's where you would set it here under condition barriers. Or if you want to know a maximum value that you would like to stop that if you were to hit you could also set that here. Functions specifies whether a calculation will be applied to that trace results. This is useful looking at things like minimum or maximum values. This is just a specific attribute within the full trace network. We have output conditions specifies the type of features that will be returned based on the network attribute, such as a name or type of attributes. These are combined. You can use multiple of these at the same time with and/or functions and then result types. By default automatically you will get a selection. In your feature classes, this is different than geometric network where you have to convert it into a selection. It's automatically a selection. Now in ArcPro you can decide to change this to an aggregated geometry if you would like to, and that would be done in this result type section. Some of these do need network attributes in order to use these. I know I did not show you how to set those up. If there's interest, we can go through that process if we have time at the end, but I did want to focus mostly on simple tracing. So I did also want to include a tip here if you are interested in some of these more advanced more complex networks in ArcPro 2.6 now in the join Field option. Let's say you wanted to use a value added attribute in our NHDPlus high resolution data set. That is, since that's a separate table. Unfortunately for Trace network you do have to add that to your feature class. The NHD flow line feature class ahead of time. And if anybody's interested in more value, added attributes are, please let me know after the presentation and I can send you some information, some links to on how to learn more about those. But since you do have to add them in ahead of time, something that I found useful when performing traces this transfer fields option within the join fields. Normally, in order to add those in you have to join them and to make them more permanent you would have to export any feature class. Now you can just choose to transfer whatever fields you would like. Example I'm using the DivDASqkm  which is one of our VAAs. And instead of joining you hit run and it will just transfer that field based on an identifier. I just thought that was a helpful tip and that can be used for more than just trace networks, so I wanted to point that out here. Last thing I want to mention before we take any questions or revisit any of these topics is they did put out ESRI did put out this blog post back on July 15th. It's very informative, has looked information and videos on how to use Trace network within Arcgis Pro 2.6. I've linked it to this slide. Here I can send out the link as well. It's very useful and going back and learning how to use the tool. So now I can take any questions. If anybody has any related to performing simple tracing trace network with the NHD. Hey Hayley. Several questions in the chat, so I'm going to kind of go through those and ask them. You can answer those. Some of them have been answered already in the chat so. Let's see, the first question was about licensing and see Greg Cocks answered that that it's it's the network analyst license, isn't required. You can use this under both standard and advanced ArcGIS Pro. Yes, so you do need a actually a standard advanced license in order to use Trace network. So, so you do not a what was it? Is it Arcview or? That's old, I guess. No, you shouldn't need any network additional network analyst if you have a standard advanced license, you'll have access to this tool box. OK, yeah. Let's see another question that was asked was about setting the flow direction. Let's see I don't think you showed that in your. In your slide, but maybe you could show that. If you have time to do a demo here little bit. See. I'm so my running actually creating it was taking a long time so that's why I didn't do a live demo. But I do have a session open with that data set that I was using. This is simply to use to. Let me go ahead and input here. For line feature classes, I don't have much. I haven't used this very much, but for my from my knowledge of it, you can simply. It's mostly just flipping it like if you wanted to go with the digitized direction. If I were to put arrows on this, you would see the digitized direction is going this way. This tool is just meant to. If you wouldn't want it to go this way, you can just flip it. I haven't used inner determinant or indeterminant direction, so I don't have much knowledge on that, but I have been able to flip it successfully. I don't have any examples of. Necessarily what I would use that for with the  NHD if anybody else does, feel free to share, but. That's just that's part of what they wanted to include. Is the option to do that. So I think if you. I think if you convert the existing geometric network it it will already be set right. The flow direction will already be set to with digitized. Yes, it automatically does with digitized. You don't have to set this as part of the process, it's only if. Maybe you see an error in how your flow is happening, which I have not observed with any of our products that I've tested so far, or for some reason you do want to flip it. That's the only time you would use this. If you have a cause too, but it doesn't, it doesn't require this in order to build the trace network. OK. OK, so another question that came up was about or actually just a comment that Greg Cocks added. That said that he wrote a script to remove the duplicate vertices. In that that you know, that can be. That can be done. I'll say that we're looking at this from, you know, sort of programmatic standpoint whether we whether we can do this on the NHD itself so that you don't have to mess with it. But if you are interested in you have an immediate need, then get with Greg and. He can provide you just. Informal, undocumented code, not something we're supporting. And I will say ESRI also has a script as well. It doesn't get rid of them for you, but it will find them for you, and I can find and that's publicly accessible to everybody and it's on there. One of their informational pages I can find that in link that as well, so if anybody is interested in having that, that's publicly released, OK, great. So another question came through as asking about barriers. It says do you have to manually apply each barrier or can you apply them automatically based on an attribute of some sort? So you should be able to. There was away when we were testing this originally, so if you have a feature class you can use this function add selected if you have like a point feature class already in your map. Again, I haven't had as much cause to play around with this as much as I would have liked yet, so I'm not sure. I don't think it has to be part of your trace network in order to work, but just be aware that it might, but I'm pretty confident that if like an NHD point feature class or something with wall like dams or any kind of walls, you should just be able to select them from your feature class and hit this and have them automatically be barriers. And the same was starting points as well. So it's probably I haven't tried that particular thing, but it probably has to be something a feature that's actually participating in the network. So the specific question was asked about dams, and so we don't have those features in the geometric network in the NHD, so they wouldn't. Automatically be participating in the network. But you should be able to do a spatial select to get those onto the flow line. That they would they would be next to and that way you'd be able to do. Just set it, set up barriers that way. And there's a link in the chat that Greg Cocks added to one of the. I think it's a blog post or help. For ArcGISPro that will talk about that more. Next question is, do you know if ESRI is making progress and allowing the trace tool to be published through Portal or ArcGIS Online? So I I did ask them about that. I've been involved in helping test the NHD on this and they said that is a future enhancement. It's not currently released yet. So I, uh, they're from my knowledge planning on that. That's just in a future release of this tool. And 2.6 potentially 2.7. That is what I remember hearing, but I would. I would take that I guess with a grain of salt. It just depends on what happens. Let's see one more clarification about licensing. It's from Greg says it's not in the basic license level, so if you have ArcGIS with ArcGISPro with the basic license, this wouldn't work. Yeah, unfortunately you need to have standard advanced license to use Trace network. Right, OK? Let's see. Do you have advice? If Pro doesn't allow you to add starting points, I think that I think we've already answered that question. We think you can add them in pretty easily. Or some misunderstanding that question. you should be able if you're adding a like a mass amount of them and for some reason this add select is not working my, I guess my advice would be to try adding it to a trace network and then trying to do that. But unfortunately if it doesn't work they will, which it should. It will have to be manual and that's that's a fairly simple process it long, but unfortunately. Again, I haven't had as much opportunity yet to play around with that as I would have liked. OK, another question in determinant that's I think related to flow direction would be useful for canals or artificial paths is the question. I can take that if you don't. if you would, if you would like to. I don't think I'm understanding that. Yeah, so you could use in determinant on canals if you didn't want to route flow through those features. Often in the NHD the direction of flow on canals isn't known. So yeah, that would be a good use of the indeterminant flow, Flow direction option in setting up your network. I wouldn't advise doing it on our official paths. Artificial paths are it's one of these. It's a name that we used for. Flow Path is going through water bodies and you definitely would want to trace in most most circumstances. I can imagine. You would definitely want the traces to go through. On artificial paths. Uh, next question. Will this work on CONUS for all versions of NHDPlus? Hayley, have you got some experience or some knowledge about running this on all of NHDPlus or all of CONUS NHD, right? Yes, so the short answer is yes, it should work, but the difficulty there is so we've been able to run it once successfully on CONUS, but it does require a huge, Like base of memory on your C drive or wherever you have Arcgis Pro installed. As we recommends for CONUS at least a minimum of 200 gigabytes of free space on the drive where your ArcPro session is installed, that's a huge ask for someone generally to have, so we've only been able to do it once successfully at our testing events with ESRI. And we haven't had the space available and machines we've tried to run it on to run successfully in House yet. So you can. I've been able to do it and I've been able to successfully. Um? Trace small sections of the network on it, but you do have to have that huge memory bank and you also have to be patient with it. It takes a very long time to run. It took a couple days, generally two or it took about a day to build it and then a day to trace a small section of it. It didn't crash, it didn't fail, you just had to be patient. But the other good news is you can build it on large datasets. You can build it on statewide datasets. You do have to still have a little bit of memory bank, but nowhere near like 200 gigabytes. I was able to successfully build it and trace it on California, which is one of our largest state level data sets in under an hour. So, and I was able to get most of California traced, for example so. While you can, I don't necessarily recommend it. Building it on CONUS, but if you have the space to do so, feel free to go ahead. Yeah I would. I would add to that that that's one of the reasons why we have value added attributes in NHDPlus. That you can do, and we've got documentation on this and we've put on a couple of webinars about this in the past. How do use those VAAs to do network traces and the nice thing about those? Is there simple database queries so they work on any size database which whatever size package of the NHDPlus you have? So if you've got the CONUS- wide NHDPlus either version. Two or soon NHDPlus Hi Res which I should talk about in a minute. Then it would be possible to use the value added attributes to do that, and it's probably going to perform better. Next question, can a flowline be clicked to make it a barrier? As far as I know no. Barriers have to be points. You can put it at the end of a flow line if you don't want to exclude that flowline cause in-traces it. It automatically, no matter where you put the point on it, it's going to include that whole flow line. So if you have a barrier like let's say you wanted to put one here and trace it, it should not include that flow line, it should. Just be discontinued. That should be the stopping point for it, if that makes sense. But no, I don't. You can't use a whole flowline. Unfortunately as a barrier. OK, next in. In the chat is just a comment. Greg Cocks added that he's using 2.7 beta and doesn't see an export to ArcGIS online yet. Uh, so. That's not to say that it may not make it into 2.7, but it's not in there in the current beta. If I'm if I'm right, Greg, I think you 2.7 beta hasn't been released to the public yet. It's part of an early adopter community, so we might not be seeing it yet as Al mentioned, but it might be. Will keep an eye on it. There's one question and I don't know if we can get into debugging, but do you see the question there from Ellen about. It's Pro won't allow her to start adding points at all- starting points. Either manually or using a file. The. No, go ahead. I'm sorry I have a question or suggestion there. I know if you when you built your trace network where you able to enable it after you built it, I can show you what I mean 'cause they won't let you put on that starting Version where The Dirty areas around the whole map view it won't let you put any starting points until after you use the Enable network topology tool in the toolbox. So. If you haven't done that, do that and then try it. If you have. I have not had that problem, but I can dig back into my notes to see if any of the other people that were testing this with on the NHD had had that problem. Yeah, in a suggestion from Danielle to check on projections that might, that might also cause problems, like if you have multiple projections. The NHD is is is in geometric decimal degrees, right? So like if your other points that you were trying to matchup were not in geographic that could potentially cause this issue, I think. Let's see Greg Cocks noted in the chat that he ran national with a 20 minute, 29 million full lines in one minutes. But he's got a whole lot of memory. 48 gigabytes, actually, that's better than what we're expecting. That is better. Maybe Greg just has the magic touch with the national? Yeah yeah. Yeah, so it wouldn't run on a smaller virtual machine. Another thing that I've. Seen, but let's see. You know something that can really affect speed is whether you have solid state drive or. A hard drive for your install disc in, like a lot of laptops I know. Or coming with solid state drives as their their C drive, right? And sometimes those will be really fast because as a solid state drive is going to be a lot faster than a hard drive. And that can make quite a difference when you're doing something like this. Let's see. That's all of the questions did Hayley did you? Are you going to do some? Live demo or you sort of already done it. I was using the slides mostly as a demo. My Proc session, no matter how small of a data set I was choosing, was taking a long time to build this morning when I was running through it. I have  this up here in case anybody mostly just had any questions or to show kind of what to look for. I can show you really quick actually to look for in terms of the duplicate vertices if you have that issue and have the interest in resolving it even though there's a way around it, I don't necessarily recommend doing this, But if you're interested in finding them way I would suggest doing it. Will see if it will cooperate with me today is by selecting the area of issue here and editing the vertices. So as you can see. This is the next one, and two are here from this very close viewpoint. Again, we're at 1 to 127. The next closest flowline is all the way over here, but if you were to continue zooming in, this is what the actual, not necessarily issue is, but this is what's being flagged at the duplicate vertices or these two points here. So. Deleting one of these won't necessarily change the overall geometry of the flow line. If they're that close together, it's really high resolution, but I don't recommend doing this, mostly because this editing process there can be multiple of these along one stretch of a flow line. A lot of different errors. They're not the easiest define without zooming in super quickly or using a script Python script, or, I believe is what  ESRI provided. And and also I would be careful about editing these as well, 'cause there is a potential to introduce a gap may be imperceptible between the inflow point of this one and this flow line here and then. That will also inhibit your trace so well. This is what they look like. Close up. I really I recommend using the validate consistency check box in the tool to just trace through them. Regardless, I don't recommend going in there and trying to fix this. It's it's a big we're looking at it right now. Ways we might be able to potentially resolve this, but I don't recommend a user unless you have the time and interest to do so. Take on doing this in your datasets. Yeah, it's not. It's pretty easy to just uncheck that validate. Validation box and You know, just. See, yeah yeah, it's just validate consistency box. It's default checked in order to trace through it, you would just uncheck it and then run the trace and it will trace through all of those. And the only other error you might see that won't affect your trace is on islands. I don't think I have it in this data set, but it's where. See maybe I can just Al are you ok with me drawing this in paint really quick? Are you alright with that? Just to show what it might look like, you're OK. Very rudimentary, but I don't have that island. I don't think in this dataset, so the only other one that you might see is a self intersecting flowline and you're only going to see this in areas with islands. Excuse my really rough looking island that looks kind of like a hedgehog, but would be an island with no other flow. It's just the outline of the island. You shouldn't have any issues tracing with this in your data set, but you might also see that pop up as well when using Trace network in your line error feature class just show up as a liner and. A dirty dirty area, but it won't cause you any issues. His odds are you're not tracing these anyway, so just be aware that could also be something you might see and the NHD or NHDPlus high resolution data set. OK, any other questions for Hayley? I have one more thing Hayley. If you don't mind, I'm gonna share my screen again. Absolutely, I'll stop sharing. I just you know I forgot in the very beginning to. Emphasize The Big Lead story on the on the newsletter. This month is that we are finished with NHDPlus HR for beta for all of CONUS. Uh, I think we mentioned it on last month's advisory call. It actually happened the day that we had this call 3 weeks ago that we finally got the last data set from the Great Lakes to put in, so we have all of CONUS Now in NHDPlusHR Beta. All there and plus we have Hawaii, Puerto Rico, the Pacific Island Territories, and several units in Alaska done as well. So we do plan to do a data release this fall sometimes soon. Can't tell you exactly how soon, but probably within the next month or two. We plan to do a national data release of all of the NHDPlus HR. It's going to be all in one great big geodatabase, one file geodatabase. It will have everything that's current as of that date. You know as a right now. So everything you see in blue here will be in that data set. It will all be consistent, so we will make sure that all of the value added attributes have been updated in upstream and downstream direction, so it's all consistent internally. And we plan to do these data releases periodically. You know, roughly on a kind of annual basis, but but will really be kind of looking at the data and what what condition it's in. Before we do that, but will be making data releases of the whole national data set. So if you want to do work on the NHD- PlusHR on so for like national projects, this will be the datasets you really probably want to focus on. We're going to publish it. It will get a DOI, I forget what that stands for now, but it's a like a unique number that identifies that particular data set and version of the data set. From from now on and forever more. Digital Object Identifier I think is what that's called, so we will be doing this over the next couple months probably, and will have that data set available. So if if you have a need for the national data set of NHDPlusHR altogether. And then that data set is coming soon. And I just wanted to let people know about that. And if you have a, if you have a. I don't know if we'll be able to build the trace network on it. We may be able to, I'm I won't promise that yet, but we might even be able to build that in to that data release. Let's see, that's all that I had today.