Latest Contributions by MelindaMorang

‎01-21-2019

No, it doesn't work that way, unfortunately. The Step 1 tool creates in addition to the transit lines and stops, a SQLite database containing the GTFS schedules and other information necessary for the transit evaluator to work later. If this database doesn't get created, then the Step 2 tool will fail, and you won't be able to use the transit evaluator in the network dataset either because it won't be able to look up the schedules. Unfortunately, the tool was designed explicitly and exclusively for use with GTFS data...

‎01-19-2019

I'm so sorry this entire process has been so full of problems. This is a really weird error. That line in the code is just looping through the rows in your Stops table, and it's reading the Shape field and the stop_id field and using the location_type field to filter only the parent stations. Does your Stops table have all these fields (Shape is just the geometry, so if it shows up as points on the map, you're good for that one). I don't know how you could have gotten this far if you didn't have stop_id, so I'm guessing location_type might be the culprit. I guess if you don't have that field, you could just add a text field called location_type to the Stops feature class, and then the tool should work.

‎01-18-2019

This error message is the key to identifying the problem: Execute: "C:\Program Files (x86)\Common Files\ArcGIS\bin\ESRIRegAsm.exe" "C:\Program Files (x86)\ArcGIS\Desktop10.5\ArcToolbox\Toolboxes\EvaluatorFiles\TransitEvaluator.dll" /p:Desktop /s Registration of TransitEvaluator.dll was not successful. When you install the tool, there is a dll called TransitEvaluator.dll which must be "registered" with ArcMap so that ArcMap knows that it can use this dll. It's like telling ArcMap, "hey, here's a new dll that's part of you now.". (This dll contains the special transit evaluator necessary for using network datasets that contain transit data.) ArcMap comes with a utility, ESRIRegAsm.exe, which takes care of registering new dlls. However, in this case, for some reason the registration process is failing, and I don't know why, and I don't know how to find out why. This type of problem is very frustrating! It's almost always some quirk of the user's machine set-up or their installation of ArcMap. I don't know what to suggest except a couple of probably not-too-helpful things: 1) Do you have another computer with ArcMap you can use instead? Maybe another machine won't have the same error. 2) Do you have the ability to re-install ArcMap on your machine or to upgrade to the latest release (10.6.1) of ArcMap? The tool should work correctly on 10.5, but since it's not, it might be worth trying something else.

‎01-18-2019

Sorry, you said that before, and I didn't read carefully enough. I'd like to see if there is more error text than what you pasted above. When you run the installer, after you get the error and click OK, click Show details. Some of the error text may be cut off or not shown. Right-click in the message window and choose "Copy Details To Clipboard" and paste the full message here so I can try to see what's wrong. Or, let me know if that's what you already did. Do you have administrative privileges on your machine? It could be that you don't have the necessary privileges to install something and copy files to C:\Program Files(x86).

‎01-18-2019

Ooooooohhhhhhh, you downloaded the github version. That version doesn't work as is. The github version is meant exclusively for people who actually want to look at and play with the code. I think there's explanatory text somewhere that says that, but probably not in an obvious enough way. If you just want to use the tool for analysis, you should download the released version from arcgis.com: http://arcg.is/10jXez. It comes with an installer that will configure all the toolboxes properly on your machine.

‎01-17-2019

The script tool seems to have lost the reference to its python script, probably because you moved the toolbox .tbx file without moving the associated .py script. See public-transit-tools/TroubleshootingGuide.md at master · Esri/public-transit-tools · GitHub

‎01-17-2019

Yes, I think so. The use of calendar.txt and calendar_dates.txt is kind of flexible. Some agencies use calendar_dates.txt only for exceptions, such as holidays or planned maintenance, but others use it to explicitly turn on service every day. Some, I suppose, do a mixture of these two. The GTFS specification allows any of these situations, and you have to understand how your data is constructed so that you can choose the correct analysis settings. This is understandably a common area of confusion for many users.

‎01-16-2019

Okay, so is there still a problem? It just sounds like the tool is finding all the service that has been "turned on" for the specific date and including that service in the counts.

‎01-16-2019

If your calendar_dates.txt file explicitly turns on service for many dates (exception type 1), then I would expect Count Trips at Stops to have much higher counts for an explicit date instead of a generic weekday. Can you post a link to the GTFS dataset so I can take a look?

‎01-04-2019

Hello Orlando. Yes, when you do network analysis (OD Cost Matrix, Route, etc.) with a GTFS-enabled Network Dataset created using the Add GTFS to a Network Dataset toolbox, the full schedule information for the transit system is used. The network includes the transit and the streets, and it automatically handles transfers between lines by allowing the traveler to walk along the streets to make connections between one bus and another, for instance. The transit schedules are used, so the wait times are automatically included in the analysis. The tools calculate the optimal route by finding the shortest travel time between two points. Unfortunately, the routes chosen do not always reflect the "best" route in reality. The results may include a very large number of transfers (which most travelers will not do) or a longer walking time than most travelers would be willing to do. There is no way to limit the number of transfers or the overall walking time, unfortunately. This is a limitation of Network Analyst itself. The Add GTFS to a Network Dataset tool requires GTFS data as an input. It can't work with just the line shapes because then the schedule information couldn't be used to create accurate travel time estimates. If you don't care about the schedules and the travel times for some reason, you could use just the shapes to create a network dataset as described in this tutorial.

‎12-06-2018

This is should actually be pretty easy for you since your data is already in a format that lends itself well to this. You need to load all the origins and destinations into the Route layer's Stops sublayer. When doing the load, just map the "Route Name" field to the Stops sublayer's "RouteName" property. An individual route will be created for each unique RouteName.

‎12-06-2018

Loading stops is doing more than just copying records into the Network Analysis layer. It's actually "locating" those points on the network, meaning that it has to determine which network edge or junction is the closest one and record that location. This process can take some time, particularly with large numbers of input points. If you have a large number of inputs and are going to use them many times in different analyses, the efficient way to handle the slowness is to first use the Calculate Locations tool to pre-calculate these network locations in advance. It saves the network location fields to the points layer. Then, when you load the points into any Network Analysis layer, you can choose to use the existing network location fields. In that case, it will load much faster because it doesn't need to perform the calculation again. It really is just copying the data and nothing else. However, if you make edits to your network dataset or decide to use different network restrictions, you will need to re-calculate your network location fields as they should be considered "stale" in that case. Another, less common, reason why loading locations may be slow is if your network dataset or your input points are missing a spatial index.

‎11-05-2018

It should still work. If you're unable to determine the problem, you'll probably need to contact Esri Support for help.

‎11-05-2018

What you want is the Copy Traversed Source Features tool. You can run this tool on a solved Network Analyst layer, and it will produce feature classes with information about the individual network edges and junctions that were traversed by the route.

‎10-31-2018

Could you tell me what your original filepath was? I'd like to fix the problem so that future users don't run into it, or report it as a bug to the team that owns the Add Field tool.

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

My Ideas

Latest Contributions by MelindaMorang

Re: Error in 'Generate Stop-Street Connector' Tool

Re: Error in 'Generate Stop-Street Connector' Tool

Re: Error in 'Generate Stop-Street Connector' Tool

Re: Error in 'Generate Stop-Street Connector' Tool

Re: Error in 'Generate Stop-Street Connector' Tool

Re: Error in 'Generate Stop-Street Connector' Tool

Re: Count trips at stops. Unexpected results

Re: Count trips at stops. Unexpected results

Re: Count trips at stops. Unexpected results

Re: OD Matrix cost (time) and transfers

Re: New Route network analysis to Solve for many paired origins and destinations

Re: Why does it take so long to load stops using Network Analyst?

Re: Question regarding network analysis in ArcGIS

Re: Question regarding network analysis in ArcGIS

Re: Unicode error running Count Trips at Stops

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