Latest Contributions by MelindaMorang

The clue here is in the error message: GTFS table stops contains at least one row with the wrong number of fields. Fields: [u'stop_id', u'stop_code', u'stop_name', u'stop_desc', u'stop_lat', u'stop_lon', u'zone_id', u'stop_url', u'location_type', u'parent_station', u'stop_timezone', u'wheelchair_boarding']; Row: (u'SpainRenfeLongDistance:71801', u'', u'Barcelona-Sants', u'', u'41.379520', u'2.140624', u'SpainRenfeLongDistance:', u'', u'', u'', u'Europe/Madrid') I'm guessing you added the wheelchair_boarding field header but didn't add an additional "," to each row in the table.  So, the header row has one more field than the rows after that.  I can see how my previous instructions were unclear on that point.  Each row must have the same length (the length of the header row), so since you added a field to the headers, you need to add a blank space to each of the data rows.  You don't need to add a value for wheelchair_boarding, but there must be a space for it. ... View more

Hi Alex.  The problem turned out to be a bug in the script where it was unnecessarily trying to convert the stop_id to a string, and for your particular data, it was throwing that Unicode decode error because it was trying to convert the string to ASCII. I have fixed the problem.  You can download a fresh version of the toolbox here: http://arcg.is/0yr9fr  Or, you can just download this one file and replace your local copy with the downloaded version: public-transit-tools/BBB_CountTripsAtStops.py at master · Esri/public-transit-tools · GitHub  In case anyone is reading this thread in the future, Alex's problem was unrelated to the original question posted here, even though they had similar error messages. ... View more

I'm glad that worked.  I don't understand why you got the error either. ... View more

I downloaded the data from your link (Fahrplandaten Februar 2019).  I was not able to even run it through the Preprocess GTFS tool because I get the following error: stop_id "de:05112:16284:0:3" in E:\GTFS\Dusseldorf\stops.txt contains an invalid non-numerical value for the stop_lat field: "". Please double-check all lat/lon values in your stops.txt file. How did you get as far as you did? Did you modify the GTFS, and if so, can you post your modified version? ... View more

Okay, several things going on here... First, you should NOT expect the transit lines produced in Add GTFS to a Network Dataset to represent that actual streets or other paths taken by the transit lines in the system.  They are simply straight lines connecting stops and are meant to represent the logical connections between stops in the transit network, NOT for accurate visualization of the transit lines.  Display Route Shapes, on the other hand, specifically uses the GTFS shapes.txt file and turns those into features for visualization on the map.  Because GTFS has somewhat of a disconnection between shapes.txt and the files that represent the schedules, it's much much much easier for Add GTFS to a Network Dataset to just use straight lines. Next, after you corrected those problems with your network dataset's settings, did you run Build Network and re-run Get Network EIDs?  Without doing those things, the changes you made aren't fully baked into the network. Finally, the non-traversable error to be looks like one of two things: 1) Your network has some kind of restriction attribute set up, and some roads are actually restricted (non-traversable).  Perhaps the restriction is configured incorrectly. 2) You forgot to set up the layer's network location settings according to this section of the user's guide: public-transit-tools/UsersGuide.md at master · Esri/public-transit-tools · GitHub .  As a result, sometimes the input points are being located on transit lines, and bad things are happening. ... View more

Okay, so the actual problem is the license error from the Get Network EIDs tool.  The other error is expected since you didn't finish Get Network EIDs successfully. The Get Network EIDs tool is a python script tool which in turn launches an ArcObjects executable which queries the network dataset and logs some IDs in a database.  The ArcObjects executable is necessary because the network dataset query is available in ArcObjects but not in python.  The problem you're seeing is when that ArcObjects executable gets run.  For some reason, the executable is not able to check out the Network Analyst license even though you have it. Other people have reported a similar error message to me, but I haven't successfully determined the cause for any of them, and there's very little that I can do as a developer.  Esri Support can't help you with specific questions about the Add GTFS to a Network Dataset toolbox.  However, for the other users with this problem, we were able to reproduce it with a simple ArcObjects executable that does nothing except check out an ArcMap, Engine, or Server license (depending on the product installed) and then a Network Analyst license. It will print out something to the console indicating whether it succeeded or failed.  Since that is a generic problem, Esri Support (or Support at the distributor for your country) should be able to help you figure it out. Here's what to do: - Download and extract this simple ArcObjects executable and put it somewhere on your machine (preferably not on the Desktop): SimpleNALicenseCheckout.zip - Box  - Open a command window - Run the executable.  You will probably see it fail with the same error as the Get Network EIDs tool. - Call Esri Support, show them this GeoNet thread and the simple executable, and see if they can help. ... View more

Hello Terry. If your results seem to be never using the transit lines, please review the probably causes and solutions listed here: public-transit-tools/TroubleshootingGuide.md at master · Esri/public-transit-tools · GitHub  If that doesn't help, could you please clarify this comment? it gives me a non-traversable error What is the error message, and when/where did you see it? (Example: when you clicked Solve) Regarding your ultimate goal: Yes, this should be doable.  It's probably best if you have two separate networks, one for the older data and one for the newer data. ... View more

Could you clarify when you get this error?  Your subject line says it's when you run Get Network EIDs.  However, your screenshot shows the caching dialog, which appears only when configuring your network analysis layer or at Solve time. ... View more

Try turning on your Network Analyst extension license. In ArcMap: Customize menu -> Extensions -> check on Network Analyst ... View more

There's no easy way to automatically apply a turn restriction for a situation like that.  I wish there was! You might be able to find a way to generate turn features programmatically with a python script, but it doesn't seem particularly easy. ... View more

If you've used the Add GTFS to a Network Dataset toolbox to create your network (unclear from your question), then there is no way to limit the number of transfers, unfortunately.  If, however, you've created your network dataset in some other way, then, depending on how you've modeled those lines, there might be.  If each bus line/route is a separate line feature, you could possible make use of turn features to add a time delay when switching from one line to another.  This won't actually limit the number of transfers possible, but by incurring a time penalty, it will make routes with transfers less efficient. ... View more

Oh yeah, duh, sorry.  Joe is correct.  You just have the parameters in the reverse order of what they should be. ... View more

I don't see anything obviously wrong with your code.  What happens if you try running the tool manually in Pro?  Do you get the same errors?  If so, the problem is not within your script but something to do with your input data. ... View more