BIVAS werkt met twee databases. Eén is gekoppeld aan de Charta Software omgeving (bivas.data) en wordt gebruikt om scenariobewerkingen te ondersteunen en de ander (een MySQL database) is bedoeld voor de opslag van alle data voor de berekeningen. Hier gaan we in op het ontwerp van de laatste.
Alle MySQL tabellen zijn MyISAM tabellen.
De tabellen
- appearance_types
- arc_types
- arc_usage_statistics_
- arc_usage_statistics_details_
- arc_vin_trajectory_connection
- arcs
- bridges
- bvms_arcs
- bvms_region_to_bivas_nodes
- calibration_values
- calibrations
- cemt_types
- construction_year_emission_factors
- counting_point_statistics_
- counting_points
- dams
- dangerous_goods_levels
- destination_trip_end_point_statistics_
- destination_trip_end_points
- emission_statistics_
- filtered_appearance_types
- filtered_cemt_types
- filtered_dangerous_goods_levels
- filtered_destination_trip_end_points
- filtered_load_types
- filtered_nstr_types
- filtered_origin_trip_end_points
- filtered_seasons
- filtered_ship_types
- filters
- fleet_mutation_scenarios
- fleet_mutation_values
- fuel_emission_factors
- growth_rate_values
- growth_rates
- infeasible_trips
- load_capacity_classes
- load_types
- locks
- mapped_arcs
- motor_replacement_profiles
- motor_replacement_values
- mutation_degree_values
- nodes
- nstr_types
- optimization_objectives
- origin_trip_end_point_statistics_
- origin_trip_end_points
- parameters
- reizenbestand
- replacement_distribution_values
- route_statistics_
- routes_
- scenario_statistics
- scenarios
- script_log
- seasonal_arc_properties
- seasons
- ship_cost_values
- ship_costs
- ship_speeds
- ship_type_efficiency_values
- ship_types
- substances
- supported_table_sets
- travel_costs
- trips
- trips_
- vin_restrictions
- waiting_time_statistics_