Latest Contributions by MelindaMorang

I think the problem is that when you call load() for your orders, you need to configure field mapping to ensure that the locations you calculated with Calculate Locations are actually used. Here is some documentation that might be useful, including code samples: https://pro.arcgis.com/en/pro-app/latest/arcpy/network-analyst/setting-analysis-inputs.htm#ESRI_SECTION2_7E253BC12E0C439E874232D0FD534FED I noticed in the call to CalculateLocations, you've applied a search query to the "GreeceRoadNetwork" source, but that source is set to NONE in search_criteria, so the query will not be used.  This isn't really a problem.  Just wanted to call your attention to it in case this isn't what you intended. vrp.searchSources=searchQuery  The problem could be in there, but I can't see in your script what the value of the searchQuery variable is. ... View more

If you're using an OD Cost Matrix layer, you can use the Add Field To Analysis Layer tool to add fields to the Origins and Destinations sublayers suitable for storying your ID.  When you run Add Locations to load your inputs, you can map your ID field to these new fields in the sublayers.  When you solve, you can do a join between the Lines sublayer and Origins or Destinations.  The OriginID field in Lines corresponds to the ObjectID field in Origins, and the DestinationID field corresponds to the ObjectID field in Destinations.  This should allow you to transfer the fields in whatever way you need. If you're using the arcpy.nax solver objects, the procedure is similar but depends on how you're loading inputs.  This is documented here: https://pro.arcgis.com/en/pro-app/latest/arcpy/network-analyst/setting-analysis-inputs.htm#ESRI_SECTION1_74EEA24F902D4ECB9C994A7A615C229F The schemas for the output classes and the relationships between them are described here: https://pro.arcgis.com/en/pro-app/latest/arcpy/network-analyst/origindestinationcostmatrix-output-data-types.htm  ... View more

To answer your specific question: No, you cannot modify network dataset properties in Python.  We don't have an API for that. But, I think there may be a couple of better option for you to solve this problem. If I've understood correctly, it seems like you need to be able to vary the numerical value associated with each mode based on product and month.  For example, Ferro_Novo (Along) is calculated using [some number] * [the length of the feature].  You are looking for a way to programmatically vary those numbers.  Is this correct? I think you may be able to solve this problem using attribute parameters.  Here is some documentation explaining what this is: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/use-parameters-with-network-attributes.htm I suggest that you create one attribute that just returns the shape length in the desired units (using a Field Script evaluator).  Then, create a second attribute for the cost you're calculating. Create attribute parameters for each of the numerical factors you need (not all 60 values you want...just one per unique factor that will serve as a variable that you will need to change).  Use a Function evaluator for each edge source that multiplies the shape attribute (the simple one I suggested you create) by the appropriate parameter to scale the value. You can then set up a travel mode for each of your 60 combinations, or, alternatively, you can dynamically create the travel modes in a Python script for running your analysis.  You can just update the attribute parameters according to the needs of the specific analysis. Here's the documentation for the TravelMode object in Python: https://pro.arcgis.com/en/pro-app/latest/arcpy/network-analyst/travelmode-nax.htm So, to summarize you will have something like this: Cost attribute 1: Length Evaluators use "Field Script" and are based on the [Shape] field Cost attribute 2: MyParameterizedCost Evaluators use "Function".  They are a function of [some attribute parameter] * Length Create an attribute parameter for your scale factor.  Let's say you have three different ones based on modes, ScaleA, ScaleB, and ScaleC.  Create each of these parameters and give them some default value (doesn't matter what).  Let's say 1, 2, and 3 So, the function evaluator for Ferro_Novo (Along) might look like ScaleA * Length. Travel mode: MyParameterizedTravelMode Create a travel mode that uses MyParameterizedCost as the impedance attribute Set the attribute parameter values to some specific values according to your desired scale factors for whatever this travel mode is intended to model (one of your 60 combinations) Then, either create 59 more travel modes, or use Python to dynamically create them from the base travel mode and just vary the attribute parameter values. I think that will work. Your other option (more what you were asking for) is to modify the network dataset XML template, but I don't recommend this, and the schema of that XML is not documented. ... View more

I don't completely understand your situation, but I'll try to answer your question. You will get a warning like "No "Destinations" found for "Location 59" in "Origins"." for each origin where no destinations were found within the cutoff.  If at least one destination was found for that origin, you won't get that warning for that origin. The "Partial solution found" message will occur if at least one origin found no destinations within the cutoff. From your pictures, it seems like your network and analysis configuration is working correctly.  If your goal is to find which origins found no destinations you can join the output Lines sublayer back to the Origins sublayer (the OriginID field in Lines corresponds to the ObjectID field in Origins) to transfer some field like Total_TravelTime (or whatever, for your network - doesn't really matter).  The rows with null values for this joined field are the origins that didn't find a destination.  (This seems more reliable than trying to parse the warning messages, if that's what you're trying to do.) ... View more

Hello.  Probably E1 and E2 are not connected because there is neither an endpoint nor a vertex at the location where E2's endpoint intersects with E1.  Any Vertex connectivity will not work if there is no vertex at that location. You can add vertices at the locations of all intersections by running the Integrate tool with a 0 XY tolerance.  (Be careful because that tool alters the input data - you might want to make a backup copy first.  Another thing to watch out for is if you overpasses and underpasses or other situations where you don't want the roads to connect at intersection points.) You will need to use Any Vertex connectivity for this configuration since the features will not be split at intersections but will simply have vertices. ... View more