If you're experiencing difficulty importing a transport network, you may need to reduce its file size or correct invalid coordinates
File Size
When transport networks are not importing successfully into Podaris this can commonly be due to overly large file sizes.
The maximum file size for service imports is 250MB; in instances where the network file exceeds or comes very close to exceeding this limit, unnecessary trips or routes should be removed from the feed.
Sometimes file size can be reduced by cutting down the network to only the area needed. This can be done using GIS tools or you can contact us directly for support at support@podaris.com
Incorrect Coordinate Locations
If you have imported a network from a TransXChange (TXC) file and some of your stops are incorrectly located this could be for a few reasons:
- The coordinates are invalid - TXC data can sometimes have incorrect or invalid coordinate entries for stops, such as latitude and longitudes incorrectly marked as an OS Grid CRS
- The stops do not have coordinates - in instances where stops in the TXC file do not have coordinates, Podaris looks up the coordinates from NapTAN - if not enough information is given in the TXC to identify the stop in NapTAN or the information doesn’t match that in NapTAN (for example the name of a stop has changed but not been updated in one of the sources) then this coordinate lookup process may not work.
- The stops are not in NapTAN - as with the point above, if the TXC contains new stops for which the coordinates need to be identified in NapTAN, this can fail in cases where the new stops are not yet included in NapTAN.
The solution to this generally requires a manual fix. This is usually either:
- Manually fixing the data, or
- Manually moving the stop locations in Podaris
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