BLOG
|
Dede I will need a bit more info to help... could you send me a screenshot of the tool with the parameters you used to run it? You can send it directly to me at bgerlt@esri.com. If you are using Impassable features it may be that you have created a situation where your Impassable features prevent any valid paths between between the many Destination Features and the single Source Feature.
... View more
02-15-2023
11:44 AM
|
0
|
0
|
6605
|
BLOG
|
@JimWooten I have updated the tool to be a bit more compatible with ArcGIS Pro 3.0. The tool will run with only a Basic ArcGIS Pro base license and a Spatial Analyst extension. If you choose to use the Create smoothed output option then a Standard or Advanced base license will be required in addition to the Spatial Analyst extension. I look forward to feedback and comments. Thanks Bob
... View more
12-15-2022
05:15 PM
|
0
|
0
|
7015
|
BLOG
|
Jim, @JimWooten I hope to make time to post an update to the tool this week. At that point I will also check the minimum license level required to verify if it more than Basic with Spatial Analyst extension. The tool should not require the Spatial Statistics extension but it will require the Spatial Analyst extension. Bob
... View more
12-14-2022
11:12 AM
|
0
|
0
|
7061
|
BLOG
|
Nate, @nathandb Thanks for using the tool and for your comments. In paragraph 5 above, I attempt to explain how to use Impedance features. If you would like to have the lines "mostly" avoid the cities then you need to create buffers around them and specify those buffers as input "Impedance" features. As Impedance features the lines will generally avoid the buffers but in some cases, where a less costly path is unavailable, the lines will pass through the buffers as in the Northeast section of the US example. If you make the buffers "Impassable" then you will make those features unreachable and so a solution will not be possible. Generally "Impassable" features should not directly correspond to Source or Destinations but might be used to control the location of output lines. For instance the US boundary LINES between Mexico and Canada could be used as "Impassable" feature to prevent lines passing through those countries. This might happen if you included Alaska as part of the input. Your question about the thickness of the lines caused me to reread the blog and realize I did not explain how to get the thicker lines as the distributive quantity increases. I think I must have covered it in a previous blog or in the tool comments but not in this version. To make the lines increase in width you must symbolize the lines using the Graduated or Proportional line symbols in the Symbology pane, use the distributed quantity field, e.g. Tax dollars or People, as the symbolization Field. Adjust the number of Classes, break Method, Template, Minimum and Maximum to get the line sizes you prefer. Watch for some edits to the blog as well as a new version of the tool coming soon. Thanks Bob
... View more
12-14-2022
10:35 AM
|
0
|
0
|
7068
|
BLOG
|
The distributed quantity field needs to be an integer field. (Long or Short). This sounds like an interesting project. The refugee field is already an integer field you can reach out directly to me at bgerlt@esri.com. It has been a while since I published the tool so it may need an update. Best, Bob
... View more
04-19-2022
06:47 AM
|
0
|
0
|
8526
|
BLOG
|
Maren I believe what might be happening is that you have opened the ArcMap version of the tool but are trying to use the tool in ArcGIS Pro. This link: https://geoxc.maps.arcgis.com/home/item.html?id=46a5ce17daa146e29aa60bc3535d3833 will get you to the version of the tool that will work with ArcGIS Pro. Please let me know if this does not resolve your issue. Thanks Bob
... View more
04-18-2022
03:39 PM
|
1
|
0
|
8545
|
BLOG
|
Mo If I understand your question, you might be able to directly use the Hydrology tools in Spatial Analyst. Those are the same tools I use in the DFL tool to create flowlines. There are a number of tools in Pro for creating surfaces which is what you need as input to the Flow Accumulation tool and then eventually the Stream To Feature tool. Topo to Raster would provide a way to use the existing lines as input to the surface creation process. Create TIN, Edit TIN, and Raster to TIN are tools that may also help. If your features do not represent a conventional streams but you want things to flow to them you can use Euclidean Distance or Distance Accumulation or Cost Distance to create an "artificial" surface that gains elevation as it moves away from your existing lines. This surface can than be used as input to the Hydrology tools. The general workflow would be something like 1. Distance Accumulation based on distance from existing lines, 2. Flow Direction, 3. Flow Accumulation using output from Flow direction. 4. Stream to Feature. Distance Accumulation and Euclidean Distance both provide for an optional Direction output so you could skip the Flow Direction step above. Here is a much description of the process I outline above. Hope this helps, Bob
... View more
08-24-2021
09:36 AM
|
0
|
0
|
10275
|
POST
|
Stephan For some reason I missed your question. I suspect the problem has to do with the size of your input raster and the size of the neighborhood. The combination makes for a really large footprint in memory due to the way the numpy ndimage.generic_filter works and the fact that I am applying an in memory loop that, for practical purposes, is about Image rows X Image columns X neighborhood width X neighborhood height X size in bytes of your pixel values. In your case this is 9238 x 9271 x 167 x 167 x 2 = 4.4G... I think. This is a fair amount of RAM and depending on OS version and available memory could be the problem. Try running the tool with a neighborhood of 5x5 as a test. If this works you can start scaling up the neighborhood until it breaks. The other solution would be to reduce the resolution of the source image. These ideas only apply if the issue is caused by running out of memory. I hope this helps.
... View more
08-16-2021
09:50 AM
|
0
|
0
|
1703
|
BLOG
|
Bartosz The behavior you are seeing is usually due the fact that there are not connections possible between the source and destinations. This may be caused by use of barrier features that obstruct the path between the source feature and destinations. It may also be caused by projection issues but I believe the code checks for that situation. Let me know if this suggestion does not help you get things working and we can keep troubleshooting. Best Bob
... View more
02-10-2021
12:54 PM
|
1
|
0
|
12491
|
POST
|
I believe you might want to use the Hydrology Toolset. Here is a good link describing the process to accomplish what I believe you are trying to do. Deriving runoff characteristics—Help | ArcGIS Desktop
... View more
08-09-2019
11:32 AM
|
1
|
0
|
1486
|
BLOG
|
Diversity Tools is a bit of an experimental python toolbox that currently contains only a single tool, Focal Diversity. The tool can calculate two diversity indexes for rectangular focal areas based on a single band raster input. The Shannon Diversity Index, often referred to as Shannon-Weaver or Shannon-Wiener Index and Simpsons Index of Diversity or Inverse Simpsons Index are both popular diversity indexes in ecology applications and are commonly used to provide a measure of species or habitat diversity for non-overlapping areas. Like the Centrality Analysis Tools published last year, Diversity Tools is based on work performed during the Green Infrastructure project a few years back. The ArcGIS Focal Statistics tool, available with Spatial Analyst, calculates several statistics for raster focal neighborhoods, including variety, but not diversity. Both Focal Statistics with the Variety option and Focal Diversity calculate a value for the central pixel in a sliding rectangular window based on the unique values within the focal window. Unlike Focal Statistics, Focal Diversity does not require a Spatial Analyst license. . I look forward to hearing of your use cases and suggestions for improvements. I am already thinking about a Zonal Diversity tool similar to Zonal Statistics if there is interest.
... View more
03-29-2019
11:10 AM
|
5
|
1
|
6382
|
POST
|
Blog for how to do it within ArcGIS Pro: https://community.esri.com/groups/applications-prototype-lab/blog/2019/03/05/distributive-flow-maps-for-pro Actual GP toolbox location: http://apl.maps.arcgis.com/home/item.html?id=f3aeafd89ae54fa1842c9e81e26025dc Blog for how to do it in ArcMap: https://community.esri.com/groups/applications-prototype-lab/blog/2013/08/26/flow-map-version-2 Actual GP toolbox location: https://www.arcgis.com/home/item.html?id=04fa6ed8746b451892f339011aaf989d These toolboxes work the same way. You can model flow of goods, planes, passengers, money or whatever from one location to many or from many to one. The quantity of goods are encoded on the "many" features. The single feature whether it is the source or destination is just starting or ending point. The tools names the single location the Source and the many locations the Destinations but it works either way.
... View more
03-06-2019
11:23 AM
|
0
|
0
|
1125
|
BLOG
|
A new version of the Distributive Flow Lines (DFL) tool is now available. (Dec 15 , 2022) updating compatibility to ArcGIS Pro 3.0. A couple of enhancements were made and some code cleanup. The tool now uses the new Distance Accumulation tool. If you want to use the tool in ArcMap, the previous version of the DFL and the previous blog are still available. The previous blog also contains a little background on distributive flow maps and some details about the internal workings of the tool. Here I will focus on how to use the new Pro tool and a couple details about the inputs and flow “direction”. The example in this blog shows the flow of federal education tax dollars from Washington D.C. to the lower 48 state capitals. If you would like to follow along, the tool and test data used to produce the maps in this blog are available at the first link above. Note: To use the tool you need ArcGIS Pro and the Spatial Analyst extension. If you do not have access to a Spatial Analyst license, a 30-day no cost trial can be obtained through the Esri Marketplace. The tool will with a base license level of Basic. If you want to use the Create smoothed output option available in the tool then a Standard or Advanced base license will be required. Usually, flow maps depict the flow of something from a single source to many destinations. They can also show stuff flowing from many destinations to a single source. The DFL tool can be used for both cases. Within the interface the point of convergence is named Source Feature. Behind the scenes the “something” always flows from the Destinations to the Source. This is because the tool uses ArcGIS hydrology GP tools and the flow lines are more akin to a stream network with the mouth of the largest stream terminating at the Source node. The Source Feature is just the location where the flow lines will terminate and does not need to have any specific fields describing the “something” flowing through the network. Figure 1: New Distributive Flow Lines Tool The Destination Features in Figure 1 must have an integer field indicating the amount of “stuff” received from the Source. In Figure 1, the Source Feature, DC Point, is a point feature over Washington DC. StateCaps represents the lower 48 state capitals. Edu_Dollars is a field in the StateCaps feature class representing federal education tax dollars supplied to the states. Figure 2, below, is the output generated based on the inputs in Figure 1. Figure 2: Output based on Figure1 input values. California and Nevada flow southward to avoid the red barrier. Note: The tool output lines will automatically be added to the map with a Single Symbol style. To make the output have lines with increasing thickness it is necessary to change the symbology of the features using the Symbology pane. The output features will contain a field with the same name as the input Distributed quantity field from the Destination features. Use this field as the symbology Field. Additionally you will want to experiment with the Method, Classes, Minimum size, Maximum size and Template input parameters in the Symbology pane to achieve the effect you like. In previous versions of the DFL, the optional inputs, Impassable Features and Impedance Features, also caused some confusion because they are similar but treated much differently by the tool. Both provide some control over where the flow lines will be placed. In Figure 2, the large red line in the western half of the US is the Impassable Features input. The blue buffers around the capitals are the Impedance Features input. Impassable features will not be crossed or touched by flow lines. They will be slightly buffered and the lines will appear to flow around them. The Impedance Features may be crossed by flow lines but in most cases the tool will also avoid these features unless there is no other less “expensive” path toward the Source Feature. Figure 3 represents the output where no Impassable Features are specified. Note the flow lines from California and Nevada change from southward to northward. Figure 3: Impedance Features input specified but no Impassable Feature input. Now flowlines generally go around the intermediate state capitals. Tip: It is not necessary to turn on, or even add the Impedance and Impassible features to the map. They are shown here for clarity. Depending on the application of the tool you may wish to show them because they are significant to the story you are trying to communicate, but often they are just used for aesthetic purposes to control the shape of the output and have nothing to do with the story being told. In Figure 4 below, neither Impassable nor Impedance features were specified. As you can see, flow lines pass through the intermediate state capitals. This is sometimes desired, but in the case of federal tax dollars, the dollars do not flow through intermediate states, so this might be confusing. Providing an Impedance feature reduces this confusion. If the buffers around the state capitals were specified as Impassable Features, the flow lines could not flow away from the states and no solution would be possible. Figure 4: Output generated without specifying Impassable or Impedance Features. California and Nevada flow northward. Flow lines flow through intermediate state capitals The output in Figure 5 below used the same inputs as Figure 4 except the “Split flow lines close to” parameter was changed from Destination to Source. The result is that California has a dedicated line all the way into Missouri, and several things change in the Northeast. This may be less aesthetically pleasing but does a better job of highlighting which individual states receive more tax dollars. Figure 5: Split flow lines close to Destinations, Neither Impedance nor Impassable features specified. Figure 6 is a closeup of what is going on in the Northeast. There are a few things worth pointing out. The first is the treatment of the Impedance Features, StateCaps_Buffer. Notice how the flow lines pass through the New York and Connecticut buffer features. This is happening because the direct route is less “expensive” than going around those buffers. Purple labels indicate where the values on the flow lines are coming from. The green flow line labels emphasize the additive nature when individual tributary flow lines converge as they get closer to the Source feature. Lastly, the Massachusetts flow line goes directly through Rhode Island. This is because it is located within the Rhode Island StateCaps_Buffer. This is a case where some manual editing may be needed to clarify that Massachusetts tax dollars are not flowing through Rhode Island. Figure 6: Note the flow line pass through the buffers around New York and Connecticut as well as Rhode Island. Also note the additive nature of the flow lines. I hope you will find the tool useful in creating flow maps or other creative applications. I also look forward to reading your comments, suggestions and use cases. If you missed the link to the tool and sample data, here it is again. Distributive Flow Lines for Pro.
... View more
03-05-2019
09:14 AM
|
10
|
28
|
24184
|
BLOG
|
Using the OriginFID and/or the DestinationFID fields you can do a GP Add Join or Join Field to add fields from the Origin or Destination feature classes. Once you have the fields added you can then symbolize those fields.
... View more
09-10-2018
10:53 AM
|
0
|
0
|
6256
|
BLOG
|
The map above shows some spider diagrams. These diagrams are useful for presenting spatial distribution, for example, customers for a retail outlet or the hometowns of university students. The lab was recently tasked with creating an automated spider diagram tool without using Business Analyst or Network Analyst. The result of our work is in the Spider Diagram Toolbox for use by either ArcGIS Pro or ArcGIS Desktop. Installation is fairly straight forward. After downloading the zip file, decompress and place the following files on your desktop.: SpiderDiagram.pyt, SpiderDiagram.pyt.xml, SpiderDiagram.Spider.pyt.xml, and SpiderDiagramReadme.pdf In ArcGIS PRO or ArcMap you may connect a folder to this the desktop folder so that you access these files. Running the tool is also easy. The tool dialog will prompt you for the origin and destination feature classes as well as the optional key fields that will link destination points to origin points. In the example below, the county seats are related to state capitals by the FIPS code. Result: Leave one or both key fields blank to connect each origin point to every destination point. Result: Which is the origin and which is the destination feature class? It really doesn’t matter for this tool – either way will work. If you want to symbolize the result with an arrow line symbol, know that the start point of each line is the location of points in the origin feature class. Script and article written by Mark Smith. Please direct comments to bgerlt-esristaff.
... View more
09-07-2018
04:01 PM
|
16
|
9
|
16832
|
Title | Kudos | Posted |
---|---|---|
1 | 04-18-2022 03:39 PM | |
1 | 02-10-2021 12:54 PM | |
1 | 08-09-2019 11:32 AM | |
5 | 03-29-2019 11:10 AM | |
10 | 03-05-2019 09:14 AM |
Online Status |
Offline
|
Date Last Visited |
02-15-2023
10:46 PM
|