Latest Contributions by MelindaMorang

‎01-06-2020

This looks like a bug, and I can reproduce it (or something similar to it) in both ArcMap and ArcGIS Pro. I will log the bug so we can fix it. However, you need a workaround, since a fix won't be available in the short term. When I switch the output polygons to use Disks instead of Rings, the polygons seem correct, and the FromBreak and ToBreak fields show me what I expect. (In the case of Disks, the FromBreak is always 0). Can you use Disks for your workflow? If you really need Rings, you could generate Disks and then clip out the lower break value polygons using a different tool, although that wouldn't be terribly efficient.

‎01-06-2020

I'm still investigating this, but one thing I notice is that 9 minutes is 540 seconds, not 450 as you've written above. Could that be part of the problem?

‎01-06-2020

Hello Cody. Are you using ArcMap or ArcGIS Pro? Also, how are you specifying the chute time impedance?

‎12-31-2019

Duplicate of https://community.esri.com/message/899596-re-gtfs-data-with-streetmap-premium

‎12-31-2019

My guess is you have the non-editable, licensed version of Streetmap Premium, so you aren't allowed to copy the data. You should check with your Esri representative about licensing the editable version: Streetmap Premium Custom Roads. I'm not sure how the cost compares to the non-editable version of the product, but your Esri rep will know.

‎12-25-2019

This results from the NO_OVERLAP setting. When you generate non-overlapping (or Split) polygons, the Service Areas get generated around each facility up to the point where it meets the Service Area polygon of another facility and then stops. In the SIMPLE_POLYS case, the extra break values are indicating that those facilities didn't get all the way to the full extent of the specified break value before being truncated by the polygon from another facility. If you switch to OVERLAP, this problem will undoubtedly go away. I'm not sure why you don't see the same behavior for the Detailed case. It seems like you should, but no doubt it's a quirk of the algorithm. We have made some updates and improvements to the Service Area polygon generation algorithm in ArcGIS Pro, so I expect you would see more consistent results if you do your analysis there.

‎12-23-2019

Hi Simon. Unfortunately, Pro doesn't yet have any way to change any sort of network dataset symbology. It's something we're currently researching, though, so we're willing to hear your needs and ideas (and the same for anyone else reading this).

‎12-19-2019

No, there is not currently a way to separate the wait time from the transit time.

‎12-19-2019

When you create your Route layer in python, use the accumulate_attributes parameter to accumulate the WalkTime attribute. Make Route Analysis Layer—ArcGIS Pro | ArcGIS Desktop Keep in mind that the Total_PublicTransitTime will include the walking time, so to get the transit+wait time, subtract off the Total_WalkTime.

‎12-17-2019

Hi Jane. What do you mean by you "need two cost attributes to be combined"? If you created your network dataset using the template provided with the tutorial in the ArcGIS Pro documentation, then the "Public transit time" travel mode is already configured to calculate walk time along streets and transit time along transit lines. When you solve a network analysis problem (like a Route) using "Public transit time" as the travel mode, it finds the optimal solution by considering the time it takes to walk along streets and ride public transit. You don't need to configure anything specific.

‎12-13-2019

I'm not sure if this works in a Python notebook, but with arcpy in ArcMap or ArcGIS Pro, you can use the Copy Traversed Source Features tool to get what you want.

‎12-05-2019

Unfortunately no. This is because the choice of bus is made internally by the Public Transit evaluator, and there's no way to get that information out of the evaluator. The evaluator can only return one value, which is "what is the cost to traverse this network edge?".

‎12-02-2019

Hello Robin. I understand your need, but we unfortunately don't currently have anything like this in ArcGIS Pro. Your best bet currently is to find an external program that can edit your GTFS data and then create a separate network dataset for each scenario. You might try TransLoc Architect, although I'm not sure what support they currently have for Sweden.

‎11-22-2019

You haven't said whether you're using ArcMap or ArcGIS Pro. If you're using ArcMap, then I am not surprised you're getting a memory error. ArcMap is an older 32-bit application that cannot use your system's full memory resources. If this is the case for you, I suggest you upgrade to ArcGIS Pro and try solving the problem there. Pro is a newer 64-bit application that can handle large problems much better. If that doesn't work either, you might want to check out this DevSummit presentation about solving large network analysis problems: Solving Large Problems video Solving Large Problems downloads

‎11-19-2019

73.2 million is a lot of trips. Yeah, good idea to narrow it down... I don't recommend you go back to ArcMap. For your problem, there is nothing in ArcMap that Pro can't do, and Pro is much better at handling large amounts of data. Yes, you can use the Generate Service Areas tool to calculate walking-only Service Areas around the transit stops and then use a spatial join (or just Select By Location) to identify the origins and destinations that fall within the Service Area polygons. This works, although keep in mind that Service Area polygons are inexact "artistic" representations of the area covered, and the polygons themselves can look quite different depending on the settings used. A more precise answer can be achieved using the Generate Origin Destination Cost Matrix tool, which also uses the ArcGIS Online Services. You can put a cutoff of 0.25 miles in this tool, and it will calculate the walk distance between each transit stop and each of your origin/destination points. The results will only include those origins/destinations that fall within the 0.25-mile limit. However, with 73.2 million points, the problem becomes very huge for Generate Origin Destination Cost Matrix (and could burn lots of credits). If you go this route, I would recommend narrowing it down first by doing Select By Location to select only those origin/destination points that are within a 0.25-mile straight line distance of the bus stops. Straight line distance is guaranteed to be >= network distance, so anything outside of 0.25-mile straight line distance definitely won't be within a 0.25-mile network distance. Then, you can see how many points you have left over and calculate the credit usage for using Generate Origin Destination Cost Matrix vs Generate Service Areas. If you still have a very large number of origin/destination points, you might need to chunk up the problem when solving it. This video and sample script from a DevSummit presentation might help.

Online Status	Offline
Date Last Visited	Monday

My Ideas

Latest Contributions by MelindaMorang

Re: Model Builder: Fixing Service Area Polygon Attribution

Re: Model Builder: Fixing Service Area Polygon Attribution

Re: Model Builder: Fixing Service Area Polygon Attribution

Re: GTFS with StreetMap Premium

Re: GTFS Data with StreetMap Premium

Re: Service Area Break Values Modified?

Re: Change Symbology on SMP Traffic?

Re: How to set more than one cost attributes

Re: How to set more than one cost attributes

Re: How to set more than one cost attributes

Re: How to get the road segment IDs/ way IDs From the Route Result?

Re: Using GTFS for trips with specific times of origin and destination

Re: Modify GTFS to "simulate" new routes

Re: Location Allocation issue

Re: Building network of streets for generate service areas

Re: TransitNetwork for multimodal analysis?

Re: Network analyst public transit tool Prepare ti...

Re: Network analyst public transit tool Prepare ti...

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

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