Latest Contributions by MelindaMorang

I looked at your model, and I noticed that you are creating the network dataset in the model.  This is a bit unusual, particularly using the Create Network Dataset tool, since (as you pointed out in one of your other questions), you can't adjust any of the network dataset properties.  Normally, you should manually create your network dataset with all the desired configurations.  Once it's created, you don't need to do it again.  You can just use it in the model (or set it up as a parameter so the user of the model can optionally select a different network dataset if desired). Alternatively, if you need to create a different network dataset in the model itself (maybe for a different city or region?), you could use the Create Network Dataset From Template tool to ensure you're creating a network with all the desired configurations (which you should set up in advance when creating the template). In summary, I don't think it makes sense to create the network from scratch and build it every time you run the model.  It's possible that this is causing the discrepancy with what you're doing in the map because you're testing with a different network dataset or something. I don't really know how to help you, and I think at this point you might have better luck calling Esri Support or whichever distributor handles Support cases for your country.  A Support analyst can spend more time with you understanding your workflow and diagnosing and troubleshooting problems. ... View more

Can you tell me what you're really trying to do?  What is the goal of your analysis? I don't really know how to answer this question, but maybe if you tell me what you're actually trying to do, I can advise on a good approach, and then this question will become irrelevant. ... View more

You should map the population to the Weight field. The Location-Allocation tutorial has an example of this: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/location-allocation-tutorial.htm  ... View more

The Cutoffs for Service Area always refers to the impedance (also called "cost") attribute being used by the travel mode that is used for the analysis.  Any network analysis always optimizes the cost attribute specified as the Impedance attribute of the travel mode.  The Time Cost and Distance Cost may be used for secondary things, like accumulating additional measurements and generating directions.  But the Impedance attribute is the important one. This documentation explains the various travel mode properties, including Impedance, Time Cost, and Distance Cost: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/travel-modes.htm  ... View more

It's there!  It's called "Mode". It's disabled for your layer because your network does not have any preconfigured travel modes defined. ... View more

It's based on the ToBreak field.  The word "Cutoff", shown in the Table of Contents, is the name of the symbol class and is used for display only. ... View more

That's correct.  You can only configure network dataset properties in the Pro UI.  You can't change them from Model Builder or Python. If you need to edit your network in an automated process, one thing you can do is create a set of network dataset XML templates with the variations of properties you want.  In Model Builder, you can use the Create Network Dataset From Template tool to create the network with the desired template.  However, this approach requires creating a limited set of templates in advance using the Pro UI to configure the attributes. https://pro.arcgis.com/en/pro-app/latest/tool-reference/network-analyst/create-network-dataset-from-template.htm  Maybe if you explain further what you're really trying to do, I can better advise on the approach to take. ... View more

That's correct.  A travel mode is a collection of settings intended to model a particular mode of travel, such as driving a car, walking, or driving an oversized truck.  In the ArcGIS Pro UI, for a particular layer, you can customize your travel mode by changing the various travel mode settings, such as the cost attribute and the restrictions.  However, we don't have that flexibility in Model Builder.  What you should do instead is add the desired travel modes in advance to your network dataset.  Set up the modes you want as permanently saved travel modes in the network, and then your model can select the desired mode at the time you run the model. https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/create-travel-mode.htm  ... View more

Hello Jamal. It's difficult to determine what's really happening from these screenshots.  It looks to me like the results might be the same but with different symbology and different draw order.  I suggest you check the attribute tables of the resulting Polygons layers and check whether they are the same.  You can use the Feature Compare tool to compare the attributes and geometry exactly. ... View more

I'm not sure what you mean about the 5000 incident limit.  If you're using a local network dataset on disk, there should be no limit to the number of incidents or facilities you can load, but 5000 is the limit if you're using the ArcGIS Online service as the network data source.  Did you accidentally use the service instead of your desired network dataset? (Note that this would not explain your performance issue, since Add Locations just appends the inputs and does not calculate anything when the network data source is a service.) Like Jay said, we probably can't help you much without your data or an official Support case. ... View more

Hi Russel.  I think I can help you out with this.  I think there are ways to accomplish what you're trying to do, although they may require adjusting your scripts. First, you are highly encouraged to migrate your scripts to use the Python solver objects in arcpy.nax instead of continuing to use Make Layer, Add Locations, and Solve in Python scripts.  You can still do the workflow that way (and I'm assuming you're migrating from ArcMap), but this is slower and generally harder to work with. Either way, I believe this is generally the workflow you need to do: Use the Calculate Locations tool to precalculate the network locations of your inputs using a travel mode where the edges aren't restricted.  This will be to determine the specific, authoritative locations you want to use for all inputs. Set up your analysis and settings (by creating a layer or instantiating a solver object). If using arcpy.nax, set the allowAutoRelocate property to False. Load locations using the precalculated network location fields. If using a layer, set the Allow automatic relocating at solve time parameter in the Add Locations tool to False.  This updates the layer's properties to turn off the auto-relocate behavior.  The tool will use the exact locations it is given, even if the edges are restricted. Solve the analysis. Change the travel mode and solve again as needed. The last section on this page may help you understand what's going on: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/precalculate-network-locations.htm#ESRI_SECTION1_E0E69D4E4A144E08B0E9997597BA7B6B Please keep asking questions if you have them.  I'm pretty sure we can figure this out with the software as implemented, but if it turns out not, we are definitely open to considering some changes or enhancements. ... View more

Hi Peter. Regarding question 1: Correct, by default, the tool does not generate line geometry in the outputs, as my research indicated that most users didn't need the lines and are mostly interested in the table.  But you can override this default behavior.  In the location where you saved the toolbox files, find the file called od_config.py and change line 35 to  "lineShapeType": arcpy.nax.LineShapeType.StraightLine, Note that with OD Cost Matrix, your only options are straight lines or no lines.  The driving time and distance is calculated along the network, but the output geometry can only either be straight lines representing the connections or no lines (this is the same as with layers).   I'm not sure about question 2.  How do you know the distances are incorrect, or in what way are they incorrect?  It won't be related to your projection or coordinate system.  That should just work.  More likely would be some incorrect mapping between the Origin and Destination IDs and the values in the Lines table, either on your end or in the tool's code.  The tool's code has been tested and should be okay, although I do see that you're using Pro 2.9.  We made some fixes to the arcpy.nax solver objects in 3.0 (I think...hard to remember) to resolve some issues with relating IDs in the outputs.  It's conceivable that you're running into an older Pro bug that is now resolved.  But that's just a guess, so let's rule out anything on your end before we go down that rabbit hole.  But if you have the ability to update your software, that will never hurt! ... View more