creating config and fixing non-eisting elements in any-to-epip, when …

skinkie / reference

Personal repository where I collect working examples to understand inner workings while building PyNeTExConv

GNU Affero General Public License v3.0

0 stars 1 forks source link

creating config and fixing non-eisting elements in any-to-epip, when … #24

Open ue71603 opened 1 month ago

ue71603 commented 1 month ago

…coming from GTFS

started with a configuration file (as we don't have the same configuration)
Some elements don't exist when doing import.py GtfsNeTex.py then any-to-EPIP. They are now optional. Perhaps this is not what you want.

Tested it with flixbus:

ue71603 commented 1 month ago

need still to test blablacarbus... there seems to be a bug somewhere...

skinkie commented 1 month ago

I don't think we will continue with any to epip. I think the process wil be something like anytodb. Then some epip validation magic. And then dbtoepip. For things you would know a priori what you would need in can be optimised.

ue71603 commented 6 days ago

@skinkie the pr is out of synch, but we need something like that. Otherwise I always have to patch stuff, before I can make it work. I don't in a linux environment and I don't have your directory structre. I would really want to steer this from a config file.