Fleet management sample database — MongoDB, embedded (192,735 rows)

Tables that belong to another are folded into it as arrays, so the documents read the way the application uses them. The rest are collections of their own, joined by key as in the flat version.

Load it:
  sh import.sh                    (into mongodb://localhost:27017)
  sh import.sh "<connection string>"

Or one collection at a time: mongoimport --db fleet-management --collection <name> --file <name>.ndjson

Collections:
  accidents — 40 documents, each with its accident_vehicles
  branches — 8 documents
  departments — 24 documents
  device_assignments — 300 documents
  driver_shifts — 5,000 documents
  drivers — 250 documents
  employees — 400 documents
  fuel_cards — 300 documents
  fuel_transactions — 3,000 documents
  gps_logs — 50,000 documents
  inspection_items — 12 documents
  inspections — 500 documents, each with its inspection_results
  insurance_claims — 30 documents
  insurance_policies — 300 documents
  maintenance_schedules — 300 documents
  maintenance_shops — 15 documents
  maintenance_tasks — 15 documents
  manufacturers — 8 documents
  models — 20 documents
  organizations — 1 documents
  parts — 150 documents
  parts_inventory — 450 documents
  roles — 6 documents
  routes — 120 documents
  telemetry_devices — 300 documents
  trips — 25,000 documents, each with its trip_stops
  vehicle_types — 6 documents
  vehicles — 300 documents
  vendors — 30 documents
  work_orders — 300 documents, each with its work_order_parts, its work_order_tasks

Folded in (no collection of their own):
  accident_vehicles — 50 rows, as the "accident_vehicles" array on accidents (its accident_id is the parent's _id)
  inspection_results — 4,000 rows, as the "inspection_results" array on inspections (its inspection_id is the parent's _id)
  trip_stops — 100,000 rows, as the "trip_stops" array on trips (its trip_id is the parent's _id)
  work_order_parts — 900 rows, as the "work_order_parts" array on work_orders (its work_order_id is the parent's _id)
  work_order_tasks — 600 rows, as the "work_order_tasks" array on work_orders (its work_order_id is the parent's _id)

Types: numeric columns are Decimal128, so totals stay exact; dates and timestamps are
Date values read as UTC (the data has no time zone); times and UUIDs are strings;
JSON columns are embedded objects.

Synthetic data, CC0-1.0, from databasesample.com. The same rows as the SQL and CSV files.
