db design #2
Description
Linus,
From the openraildata-talk forum you say;
I'm just writing a quick script to put the routeing guide data into a database where I can get to understand it a bit more
My first thoughts are that the database design is going to be v. important. Certainly for me it will be. Having just had a quick look through what's available at http://data.atoc.org/routeing-guide I can see that what's available is exactly what I'm looking for and have been waiting for. A long-standing project of mine has been to add journey planner capability to my websites. I've held back for various reasons and I've been reluctant to go with the 'off-the-shelf' version available from NR. I can see now that with this NRG data I can use it as a base for my own JP project. So to cut a long story short, there's more than one way to skin a cat, as is there to create a database! Is it an idea to collaborate on the db design?
I should add I'm still not exactly sure what this github project is aiming to achieve other than from the title, Routeing Guide Tests. I know your focus has usually been towards ticketing. I'll also add though that I've still to look through it in detail. Anyhow, like I say, I'm happy to help and have already learned a bit. Let me know your thoughts.
Cheers,
Mike