Problem with longer route history is quickly the database size. The current (3 weeks was it?) data takes already a very big chunk. However if we'd store only parts of the data (not the full detailed history) then it might be easier to do. So what sort of data would you need in the long run, and how long you'd need to be able to view them?
well... i guess whats most relevant is the load per flight. i doubt its such a big amount of data:
Data: GW;AirlineID;Flight Number;Date;From;To;Y-Pax;C-Pax;F-Pax;L-Cargo;S-Cargo;H-Cargo
.) Everything else can be determined from these values, Id guess.
.) Pax and Cargo, I would save as absolute values: Nr of Pax, kg of Cargo, and not as Loadfactor, so if the plane is changed, one would still see the absolute values transported before and after).
.) The "From" and "To" Airports I would save because if the flight number is being used for a different destination, then of course it should not be displayed anymore.
.) If something minor is edited about the flight number (takeofftimes, blocked seats, etc.) the information should still be available in the historic context.
.) Would also be great since then its continuous for flights on different days that are separate routes (otherwise one can only see the data for the same-weekday-flight, for two weeks, which is rather little information to see any change).
Duration: in my opinion thats 2 or 3 years, after that, delete the data after that. so you could see a graph were one could see the effects of price changes, demand changes...
.) yes, its somewhere like 700 to 1000 lines per flight number.
.) Considering all alliances in GW2 have currently 700k routes, most of those probably separated by weekday, makes maybe 200k flight numbers. Multiply by 700 or 1000, that makes 500M to 700M lines per gameworld... ok, it is a lot
.) maybe half a year?
