GTFS to Network Dataset Tool Error 03206

RylandLu

When I try to convert 11 GTFS datasets into a regional transit network dataset using the GTFS to Network Dataset tool, the attached error message shows up. It is a lot of GTFS datasets to work with but I managed to use the tool just yesterday with the same number of datasets. I only changed two of the GTFS datasets since yesterday (one only had two minor changes to the Stops file), so I don't think it's the data, but I can send the two new GTFS files just in case.

I need to have an analysis completed by Monday. If there is an issue with the tool, how promptly could this be worked out?

MelindaMorang

From the error message, it looks like the problem is probably with the route_type field in routes.txt. However, the June2025_Rail dataset you attached is fine, and the tool runs correctly with it on my machine. I would check your other routes.txt files from other datasets for one where route_type is null or something like that.

If you find it, please share the data! I'd love to fix the tool so it provides a better error message. (Fixing the tool will happen on the Pro release cycle and can't be done and released to users quickly, so we need to find the error in your data and correct it so you can get your work done.)

View solution in original post

RylandLu

Here are the GTFS documents I made changes to. Made changes to Routes.txt, Calendar.txt, Stops.txt, Trips.txt and Stoptimes.txt in the June2025_Rail folder. And just made stops.txt in another GTFS folder (too large to attach all).

MelindaMorang

From the error message, it looks like the problem is probably with the route_type field in routes.txt. However, the June2025_Rail dataset you attached is fine, and the tool runs correctly with it on my machine. I would check your other routes.txt files from other datasets for one where route_type is null or something like that.

If you find it, please share the data! I'd love to fix the tool so it provides a better error message. (Fixing the tool will happen on the Pro release cycle and can't be done and released to users quickly, so we need to find the error in your data and correct it so you can get your work done.)

RylandLu

Thanks Melinda!! I will check the route_type fields to see if there are any strange values.

Best,
Ryland

MelindaMorang

@RylandLu It seems like you must have found the culprit. Any chance you can share the bad routes.txt file with me so I can improve the error message on our side?

RylandLu

Hi Melinda,

Unfortunately, I saved over the text and excel files I was working off of. The crux of the issue, if I recall, was having a period instead of a comma for one of the comma separators in the attached .txt file.

Best,
Ryland

MelindaMorang

Oh, I think that makes sense. The route_type field probably got something like 3.1 instead of 3, so it was read as a double instead of an int. I'll see if I can reproduce that problem and make the error better.

RylandLu

Thanks Melinda!

I did have another issue getting analyses of access and travel time between three of the stops on the new rail line I "constructed" in the network. Meant to post last week but this fell through the cracks. I will create a separate ticket for this.