For unknown route_type values, use int instead of str

When the user's data has route_type values that don't match the ones listed in the GTFS spec, my code sets the route_type to 100 as just a random value to track them. It was setting it to a string value, '100', instead of an integer, and this caused these routes to get ignored later when generating polylines.
Esri · Oct 22, 2018 · 7f53a07 · 7f53a07
1 parent e4d81b9
commit 7f53a07
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/generate-GTFS-shapes/scripts/Step1_MakeShapesFC.py b/generate-GTFS-shapes/scripts/Step1_MakeShapesFC.py
@@ -1303,7 +1303,7 @@ def get_route_info():
             route_type = route[5]
             route_type_text = route_type_dict[int(route_type)]
         except:
-            route_type = '100'
+            route_type = 100
             route_type_text = "Other / Type not specified"
         RouteDict[route[0]] = [route[1], route[2], route[3], route[4], route_type,
                                  route[6], route[7], route[8],
@@ -1411,4 +1411,4 @@ def append_existing_shape_to_fc(shape, StopsCursor, route=None):
     # Add the polyline feature to the output feature class
     StopsCursor.insertRow((polyline, shape, route,
                             route_short_name, route_long_name, route_desc,
-                            route_type, route_type_text,))
+                            route_type, route_type_text,))