Troubleshooting Transport Network Imports

File Size

When transport networks are not importing successfully into Podaris this can commonly be due to overly large file sizes. 

File size limits vary depending on the type of file you are uploading:

If your upload exceeds these limits, you will receive a "Too large" message in the upload panel before processing begins. If you need to import larger GTFS/TransXChange feeds or datasets, contact your Podaris support to adjust instance limits.

Pre-Upload Validation Errors

As soon as you select or drop a file into the asset library, Podaris inspects the file and provides immediate feedback on the file card before any data is uploaded.

Common validation messages and how to resolve them include:

• Too large: The file exceeds the maximum size limit for its format (see table above). You must simplify or compress the dataset before uploading.
• Coordinates in the wrong place: Typically indicates that the file uses a local or projected coordinate system instead of WGS 84 (EPSG:4326). Convert the file’s CRS to standard latitude/longitude coordinates in a GIS tool before re-uploading.
• No features Podaris can use: The file is empty, corrupt, or contains geometry types that Podaris cannot read. Inspect the file in a GIS desktop application to ensure it contains valid features.
  • Note: Podaris does not support multipart geometries. Multipart features are automatically flattened into single-part features upon import.

If you are unsure what might be wrong with the data, or would like help manually fixing it, please get in touch with us at support@podaris.com