Closed ue71603 closed 2 months ago
You can't make this robust, if the source data is not declaring things, or is mixing Latin-1 with UTF-8 or UTF-16. So lets first figure out what codec the original file is written in.
@skinkie is import.py generated? Or can I do changes there?
change import.py
with open('some.csv', newline='', encoding='utf-8') as f:
GTFS is not mandatory UTF-8. But it should be. and in Europe I think it must be: https://en.wikipedia.org/wiki/GTFS#:~:text=A%20GTFS%20feed%20is%20a,character%20encoding%20is%20UTF%2D8.
@skinkie is import.py generated? Or can I do changes there?
Manually created. But what I mentioned before, we still should have something that adds optional columns, or even entire tables iff missing.
GTFS is not mandatory UTF-8. But it should be. and in Europe I think it must be: https://en.wikipedia.org/wiki/GTFS#:~:text=A%20GTFS%20feed%20is%20a,character%20encoding%20is%20UTF%2D8.
Encoding is now resolved.
Using: https://transport.data.gouv.fr/resources/11681?id=11681&locale=en
I added a reasonable feed_info.txt
However, the run of GtfsNeTEx breaks due to a character problem. More robustness there is needed: