POST
|
You probably ran into some bug from an old version of Display GTFS Route Shapes that was fixed at some point. That tool is now deprecated anyway. For future readers of this post: Use the GTFS Shapes To Features tool available in core ArcGIS Pro if you want the same functionality.
... View more
yesterday
|
0
|
0
|
12
|
POST
|
Hello Patrick. I looked at your network, and I think I know what the problem is. The WalkTime cost attribute included in the network by default (created from the provided template) is not really meant to be used to model walking only. I realize this is a bit misleading. Essentially it is there to help create a reasonable walk time estimate for use in the transit calculations and so you can accumulate the total walking time used in your transit journeys. For this reason, it calculates the walk time along transit lines (LineVariantElements) and StopConnectors as 0. If you use the WalkTime cost attribute directly, it sees the transit lines as free to use, so your routes will be all weird. If you want to use this network to model walking, you can do one of two things. 1) Cheat. Use your transit travel mode, but just don't set a time of day. The transit lines will never have any service and will be effectively restricted, and so all calculations will default back to walking. 2) Continue along the route you're currently on, but fix your walking travel mode. The easiest thing is to create a restriction attribute that makes LineVariantElements and StopConnectors restricted all the time and make sure this restriction is turned on for your Walking travel mode.
... View more
|
1
|
1
|
5
|
POST
|
Hello. There doesn't seem to be anything wrong with your LineVariantElements. The GTFS To Network Dataset Transit Sources tool generates a straight line between each pair of connected transit stops. If your system doesn't have long-haul commuter routes from the suburbs to downtown, for example, you won't get long spiky lines. Instead, you'll just get a straight line that goes for a few blocks between stops. If you zoom in close, I'm sure you'll see that the lines do not actually follow all the curves in the streets and are probably offset from the street centerlines. Whatever problem you're experiencing likely comes after this point, but I cannot quite tell from your description what's really going on. If you're following the tutorial, you should have been able to create your network dataset from the provided template. Did that work? If so, that should have automatically created the network dataset with an impedance attribute that uses the "Public Transit" evaluator for LineVariantElements, and thus uses the public transit schedules for calculating travel times. Please describe further the problem you're experiencing, and I'll do my best to help you sort it out.
... View more
|
0
|
0
|
8
|
POST
|
To map the frequency of public transit service, you can use the Count Trips on Lines tool in the BetterBusBuffers toolbox: http://esri.github.io/public-transit-tools/BetterBusBuffers.html However, this tool will not map the frequency of bus service on the streets. The lines produced by the tool are simple straight lines connecting adjacent stops. I have not found a good way to match these lines to the underlying street features, unfortunately.
... View more
a week ago
|
0
|
0
|
27
|
POST
|
Did you ever find a solution to this problem? Another user reported a similar issue to me, and I still cannot reproduce it.
... View more
2 weeks ago
|
0
|
0
|
11
|
POST
|
Hello June. It looks like Digital Transport For Africa made a copy of my GitHub repo a long time ago. I don't recommend using anything you find there. First of all, this is the authoritative version of the Add GTFS to a Network Dataset toolbox is here: http://esri.github.io/public-transit-tools/AddGTFStoaNetworkDataset.html. Note that this toolbox is now deprecated anyway, even if you get the latest version. I no longer recommend that people use this, and I do not provide extensive tech support anymore for it. Second, that toolbox does not work in ArcGIS Pro. If you want to do analysis with public transit data in ArcGIS Pro, you do not need any additional, downloadable tools. The functionality is now available out of the box. Learn more here: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/network-analysis-with-public-transit-data.htm The best way to get started is to follow this tutorial: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/create-and-use-a-network-dataset-with-public-transit-data.htm Note that the tutorial includes some data and a network dataset template as well, but it's designed specifically to work for ArcGIS Pro. Hope this clarifies things!
... View more
2 weeks ago
|
0
|
0
|
35
|
POST
|
So far I have not been able to reproduce the original problem. Question: When you did the “Connect the transit stops to the streets” part of the tutorial, for Input Streets Features parameter in the tool, did you select the Streets feature class in the target feature dataset? Or did you accidentally select the one in the original location?
... View more
2 weeks ago
|
0
|
1
|
43
|
POST
|
Hello Scott. I'm sorry for your trouble, but the good news is that there's an easy fix for you. For some reason, your street data did not end up with vertices at the locations where the StopsOnStreets intersect them: Without vertices at those locations, travelers cannot travel between the streets and the transit lines, hence why the transit lines are never being used. Vertices should be automatically created when you run the Connect Network Dataset Transit Sources To Streets tool. I will investigate further to see why this didn't happen. However, regardless of what happened in the first place, there is an easy way for you to fix your network. 1) If you made any changes to your network's configuration (I don't think you did...), run the Create Template From Network Dataset tool to preserve your network's configuration into a file. Skip this step if you didn't make any changes in that case you can just use the existing template that comes with the tutorial (the one you already used). 2) Delete your network dataset. 3) Run the Integrate geoprocessing tool with the inputs configured as follows: The Integrate tool will create vertices at the intersections of the input feature classes. Setting the XY Tolerance to 0 ensures that your input features will not be moved at all. 4) Re-create your network dataset using the template. 5) Run Build Network to re-build your network. After this procedure, I was able to see the vertices in the expected location, and the network used the transit lines. Assuming you're able to get up and running successfully and you have some time, could you tell me the following to help me investigate the cause of the original problem? What version of ArcGIS Pro are you using? Did you follow the tutorial steps exactly (using your own data), or did you deviate from that and do something else? Are you able to share your GTFS data with me so I can run some tests?
... View more
2 weeks ago
|
0
|
2
|
49
|
POST
|
The Location-Allocation solver cannot display the actual paths taken through the network from Facilities to Demand Points, even though it uses the network paths under the hood. It's just a limitation of the solver and is done this way to improve performance. If you want to display the actual paths taken for visualization purposes, you will need to use the Demand Points and chosen facilities as input stops for a Route analysis (or maybe Closest Facility) and solve that analysis. If the chosen facilities are reliably the closest to each demand point, or you only have one chosen facility, Closest Facility is the easiest thing to do. Otherwise, you can use Route, and you must load a copy of the facility for each demand point. You need to use the RouteName field to designate a unique identifier for each Demand Point/Facility pair to ensure that a separate route is generated between each demand point and its associated facility.
... View more
2 weeks ago
|
0
|
0
|
24
|
POST
|
This page explain the output of the Copy Traversed Source Features tool: https://pro.arcgis.com/en/pro-app/latest/tool-reference/network-analyst/copy-traversed-source-features-output.htm If the routes do not travel over edges, junctions, or turns, then the associated output table will be empty.
... View more
3 weeks ago
|
0
|
1
|
57
|
Online Status |
Offline
|
Date Last Visited |
yesterday
|