Latest Contributions by MelindaMorang

‎03-22-2019

Did you switch your polygon type from Generalized to Detailed at some point? I just tried it, and Detailed gives me 0-20, but Generalized shows 0-[individual maximum]. This is probably a bug, which I will investigate further and log.

‎03-22-2019

Okay, sounds like you haven't identified an obvious change that caused the problem, so let's talk about what you're really trying to do and see if there's another way you can get the result you're looking for. From what you've said, it sounds like you are trying to assign territory to the closest fire station. In other words, you're not creating a 20-minute drive-time polygon around each fire station. Instead, you're setting the break value to 20 minutes, but you want it to return a polygon showing a maximum of 20 minutes, but if there's an area where those 20-minute drive-time polygons would overlap, just assign the area to the closest fire station. When this happens, the ToBreak generally will end up as something less than 20 minutes if your fire stations are pretty close together because there was nowhere that the fire station's service area got as far as the 20-minute break. It always ran into the service area of another fire station first. Do I understand this correctly? I guess before speculating further, make sure your Service Area polygon generation settings are correct. Check the information in the "The Polygon Generation tab" section under the "Multiple Facilities option" on the Service Area analysis documentation page. If the output described above is what you want, you should be using the "Not overlapping" option. Also, if you describe in more detail what you're really hoping to analyze, we might be able to find a better overall way to do it. Feel free to elaborate.

‎03-22-2019

Yes, you can use the Global Turn Delay Evaluator on your network dataset to establish a delay time for every intersection depending on the direction of turn (left, right, or straight): http://desktop.arcgis.com/en/arcmap/latest/extensions/network-analyst/global-turns-establishing-global-turns.htm

‎03-22-2019

You said the results have changed in the last month or so. Did you do any of the following: - Update your ArcGIS version - Edit your network dataset - Change your model or procedure Something must have changed in order for the results to have changed. Let's see if we can figure out what it was.

‎03-21-2019

Are you solving your service area against a local network dataset, or are you accessing the ArcGIS Online services to solve the service area through ArcMap?

‎02-28-2019

Can you add more specific details about the analysis you're trying to solve and what the error message says? Question 1: You said you're using ArcGIS Online. Are you using a location-allocation layer in the map that uses ArcGIS Online as the network data source and then hitting the Solve button on the ribbon or using the Solve geoprocessing tool? Or are you using the Ready-to-use services Solve Location Allocation tool? Question 2: Is that ALL the error message said, or was there more stuff up above that. Please paste the full text or add a screenshot. Question 3: How long did the analysis run before you got the error?

‎02-27-2019

If you're working with python PointGeometry objects, there's a method called angleAndDistanceTo that can be used to calculate the bearing from one point to the next. PointGeometry—ArcPy classes | ArcGIS Desktop

‎02-25-2019

No, I don't think that would work. In this case, the user knows the value he wants but needs a way to inject that value into the Network Analyst layer's properties. We just don't provide that capability in ModelBuilder.

‎02-25-2019

You can't update the Location-Allocation layer itself in Model Builder. However, this can be done in a python script quite easily using the GetSolverProperties function and then setting the facilitiesToFind property. If you prefer to use ModelBuilder, you can increase the efficiency of your model by pre-calculating the network locations of your facilities and demand points using the Calculate Locations tool. This tool defines how the points locate on the network dataset. Then, when you run Add Locations many times in your model, it doesn't have to calculate the locations again. Rather, it just uses the network locations stored in fields in the input points, and it should be fast.

‎02-22-2019

Hello Michael. For any set of points that will be loaded more than once into a network analysis layer, you can increase efficiency by first running the Calculate Locations tool: Calculate Locations—ArcGIS Pro | ArcGIS Desktop . This tool pre-calculates the network locations of each point. Then, when you run Add Locations, you can choose to use the existing network locations rather than the Add Locations tool re-calculating them from their geometry. So, you calculate the locations once instead of four times. I imagine you have a large number of inputs points and that's why it takes several minutes to run Add Locations. But, just to be sure, does your network dataset have a spatial index? Check your network and its source feature classes to be sure. If it doesn't have a spatial index, everything will go MUCH slower.

‎02-22-2019

Hi Sam. This work is currently in our plan for ArcGIS Pro 2.4. If we don’t hit any roadblocks (or polygon/line barriers that slow us down ) we should see it in the mid-year Pro release. If it slips for any reason, it should make it into ArcGIS Pro 2.5 scheduled for the end of the year. This note should be treated as an estimate, not a promise.

‎02-22-2019

I've attached a zip file containing the sample script. It's pretty outdated by this point and will have to be modified for your purposes. There are comments throughout which hopefully explain what each part is doing.

‎02-20-2019

Okay, good luck. I personally will only be at DevSummit on Friday morning, but various members of my team will be around all week if you have general Network Analyst questions.

‎02-20-2019

Robert, the customer is specifically asking about solving network analysis using the Add GTFS to a Network Dataset toolbox. A Service Area generated with a transit-enabled network dataset created with that toolbox will show the area reachable by transit and walking within a time limit. The customer wants to know if there's a way to limit the walking time separately from the overall travel time. For example, I'm willing to travel for an hour, but I won't walk more than 10 minutes. The other 50 minutes can be spent sitting on a bus. The answer to the question is no, the Add GTFS to a Network Dataset stuff (and the Network Analyst solvers) doesn't support this, as explained in my other comment.

‎02-20-2019

Unfortunately, although this feature is frequently requested, this is not really possible with the transit evaluator and Add GTFS to a Network Dataset toolbox, as mentioned in the "Limitations and weaknesses" section of the User's Guide. This problem is because of the way the Network Analyst solvers work under the hood. They do not have the ability to separately track and limit different states (walking vs. transit). For the Service Area Lines output only, you can kind of hack it to sort of do what you're asking. You should continue to use your transit travel time cost attribute as the impedance attribute. But, additionally, you should set the accumulate attributes to accumulate a walk time attribute. For streets, the walk time attribute should use the same evaluator calculation as the transit travel time attribute. However, for transit lines and the stop-street connectors, you should set the evaluator to a constant of 0. You could also choose to make this attribute calculate walking distance instead of time. When you accumulate this attribute, it will add time or distance whenever the streets are traversed (where the traveler is walking), but it will not add any impedance for travel along the transit lines and connectors. Then, you can eliminate all output Lines where the accumulated walk time or distance exceeds your threshold.

Online Status	Offline
Date Last Visited	‎06-12-2026 01:44 PM

My Ideas

Latest Contributions by MelindaMorang

Re: Values in Tobreak in Service Area Analysis

Re: Values in Tobreak in Service Area Analysis

Re: Network Analyst solving service area with wait times at traffic intersections.

Re: Values in Tobreak in Service Area Analysis

Re: Values in Tobreak in Service Area Analysis

Re: ERROR 030024: Solve returned a failure ArcGIS Pro

Re: Calculating bearing between 2 GPS points

Re: Looping over a location allocation layer in model builder:

Re: Looping over a location allocation layer in model builder:

Re: Efficiency of network analysis workflow?

Re: Creating a Network Dataset in ArcGIS Pro

Re: calculate accessibility matrix code

Re: Limit walking distance

Re: Limit walking distance

Re: Limit walking distance

Re: How do I fill in the blank areas where streets...

Re: Route Solver - Add Locations - Convert Model B...

Re: Route Solver - Add Locations - Convert Model B...

Re: Recover Network Dataset from Mobile Map Packag...

Re: Service Area Solve with Python