Skip to content
This repository was archived by the owner on Dec 29, 2020. It is now read-only.

spaceModel.md

Latest commit

 

History

History
281 lines (203 loc) · 11.3 KB

spaceModel.md

File metadata and controls

281 lines (203 loc) · 11.3 KB

teched2018-cro2

TechEd 2018 Session Journey For Track CRO2

Extension Space model for cdsSpaceTrip

The space-model extends flight-model in order to represent journeys taken into space.

Space data model diagram

Entities for Read-Only Master Data

Entity AstronomicalBodies

Any astronomical body such as a planet or a moon that could act as a travel destination.

Definition

entity AstronomicalBodies {
  key ID             : Integer;
      Name           : String(100) @title: "Astronomical Body";
      SolarDistance  : Decimal(10, 8);
      SurfaceGravity : Decimal(10, 6);
      Arrivals       : Association to many SpaceRoutes on Arrivals.DestinationPlanet=$self;
      Departures     : Association to many SpaceRoutes on Departures.StartingPlanet=$self;
      Spaceports     : Association to many Spaceports  on Spaceports.OnPlanet=$self;
};

Structure

Field Name Key Description
ID Tick An arbitrary integer
Name Name of the astronomical body
SolarDistance The body's average distance from the Sun as measured in astronomical units (where 1.0 AU is the distance from the Earth to the Sun)
SurfaceGravity The fraction of Earth's gravity experienced on the surface of this body

Content

The runtime data is stored in file astrobodies.csv and currently lists only the 8 planets in our solar system, plus Pluto and the Earth's Moon.

Entity SpaceFlightCompanies

This entity performs the same role as Airlines in the base data model, but is used exclusively to represent companies operating launch vehicles suitable for Lunar space travel or beyond.

Definition

entity SpaceFlightCompanies {
  key ID            : Integer;
      Name          : String(100) @title: "Space Flight Company";
      OperatesFrom1 : Association to Spaceports;
      OperatesFrom2 : Association to Spaceports;
      OperatesFrom3 : Association to Spaceports;
};

Structure

Field Name Key Description
ID Tick An arbitrary integer
Name The name of the space flight company
OperatesFrom[1..3] The ID of the spaceport from which this space flight company operates

Content

The runtime data is stored in the file spaceflightcompanies.csv. There are currently only 7 companies worldwide capable of launching vehicles into Lunar orbit or beyond.

Entity Spaceports

This entity performs the same role as Airports in the base data model, but is used exclusively to represent launch sites for space flights.

These launch sites are not necessarily located on Earth.

Definition

entity Spaceports {
  key ID         : Integer;
      Name       : String(100) @title: "Spaceport";
      OnPlanet   : Association to AstronomicalBodies;
      Latitude   : Decimal(12, 9) ;
      Longitude  : Decimal(12, 9) ;
      OperatedBy : Association to many SpaceFlightCompanies
        on OperatedBy.OperatesFrom1=$self
        or OperatedBy.OperatesFrom2=$self
        or OperatedBy.OperatesFrom3=$self;
};

Structure

Field Name Key Description
ID Tick An arbitrary integer
Name The spaceport's name
OnPlanet The ID of the planet or moon on which this space port is located
Latitude The spaceports's latitude in decimal notation
Longitude The spaceports's longitude in decimal notation

Content

9 spaceports are currently listed. These spaceports can handle large space-vehicles capable of lunar or trans-lunar flight.

3 non-terrestrial Spaceports have been added:

  1. Tranquility Base on the Moon (the Apollo 11 landing site)
  2. Jezero Crater on Mars
  3. Columbia Crater on Mars

The last two spaceports are the proposed landing sites for NASA's Mars 2020 mission.

The runtime data is stored in the file spaceports.csv.

Entity Spaceroutes

Lists all the routes that involve some aspect of space travel. For ease of understanding, each space route can be grouped into one of four general categories:

  1. Surface launch of the vehicle into low planetary orbit
  2. From low planetary orbit, enter some type of transfer orbit (this will take you to your destination planet)
  3. Transition from transfer orbit into low planetary orbit
  4. Descent to planetary surface

Not all of these routes start or finish on the surface of a planet.

Definition

entity SpaceRoutes {
  key ID                       : Integer;
      Name                     : String(100) @title: "Space Route";
      StartingPlanet           : Association to AstronomicalBodies;
      DestinationPlanet        : Association to AstronomicalBodies;
      StartingSpaceport        : Association to Spaceports;
      DestinationSpaceport     : Association to Spaceports;
      StartsFromOrbit          : Boolean    default false;
      LandsOnDestinationPlanet : Boolean    default false;
};

Structure

Field Name Key Description Can be null?
ID Tick An arbitrary integer belonging to a number range
See below for details		 No
StartingPlanet The ID of the planet from which this route starts Yes
DestinationPlanet The ID of the planet on which this route ends No
StartingSpaceport The ID of the spaceport from which the vehicle is launched Yes
DestinationSpaceport The ID of the spaceport to which the vehicle returns Yes
StartsFromOrbit Does this route start on the surface from orbit No
LandsOnDestinationPlanet Does this route terminate on the destination planet No

The space route categories listed above are identified by the number ranges shown below. The key field for each route is then an arbitrary integer within the given number range:

SpaceRoute ID Route Category
000 - 099 Surface launch into low planetary orbit
100 - 199 Enter transfer orbit
200 - 299 Enter low planetary orbit
300 - 399 Descend to planetary surface

Content

As described in the introduction, a journey taken in space consists of multiple legs (or stages). Each leg is stored as a specific space route.

In the following tables, null fields have been left blank for visual clarity. (LEO = Low Earth Orbit)

Surface Launches (00 - 99)
ID Route Name Starting Planet Destination Planet Starting Spaceport Destination Spaceport Starts From Orbit? Lands On Destination Planet?
000 Cape Canaveral to LEO Earth Earth Cape Canaveral FALSE FALSE
001 Baikonur to LEO Earth Earth Baikonur FALSE FALSE
002 Tranquility Base to Low Lunar Orbit Moon Moon Tranquility Base FALSE FALSE
003 Jezero Crater to Low Martian Orbit Mars Mars Jezero Crater FALSE FALSE
004 Columbia Crater to Low Martian Orbit Mars Mars Jezero Crater FALSE FALSE
Transfer Orbits (100 - 199)
ID Route Name Starting Planet Destination Planet Starting Spaceport Destination Spaceport Starts From Orbit? Lands On Destination Planet?
100 Transfer Orbit (Earth to Moon) Earth Moon TRUE FALSE
101 Transfer Orbit (Earth to Mars) Earth Mars TRUE FALSE
102 Transfer Orbit (Mars to Earth) Mars Earth TRUE FALSE
103 Transfer Orbit (Moon to Earth) Moon Earth TRUE FALSE
104 Free Return Transfer Orbit (Earth via Moon) Earth Earth TRUE FALSE
105 Free Return Transfer Orbit (Earth via Mars) Earth Earth TRUE FALSE
Enter Low Planetary Orbit (200 - 299)
ID Route Name Starting Planet Destination Planet Starting Spaceport Destination Spaceport Starts From Orbit? Lands On Destination Planet?
200 Enter LEO Earth TRUE FALSE
201 Enter Low Lunar Orbit Moon TRUE FALSE
202 Enter Low Martian Orbit Mars TRUE FALSE
Planetary Descent (300 - 399)
ID Route Name Starting Planet Destination Planet Starting Spaceport Destination Spaceport Starts From Orbit? Lands On Destination Planet?
300 Earth Re-entry Earth Baikonur TRUE TRUE
301 Lunar Descent Moon Tranquility Base TRUE TRUE
302 Martian Descent (Jezero) Mars Jezero Crater TRUE TRUE
303 Martian Descent (Columbia) Mars Jezero Crater TRUE TRUE

The runtime data is stored in the file spaceroutes.csv, which currently contains the 18 entries shown above.

Entities for Modifiable Master Data

Extension to Entity Itineraries

The Itineraries entity is extended here to add SpaceLegs that consists of up to 9 separate legs (or stages).

Definition

extend flight.Itineraries {
  SpaceLegs : {
    leg1  : Association to SpaceRoutes;
    leg2  : Association to SpaceRoutes;
    leg3  : Association to SpaceRoutes;
    leg4  : Association to SpaceRoutes;
    leg5  : Association to SpaceRoutes;
    leg6  : Association to SpaceRoutes;
    leg7  : Association to SpaceRoutes;
    leg8  : Association to SpaceRoutes;
    leg9  : Association to SpaceRoutes;
  };
};

Structure

Each leg of the journey refers to the ID of a space route.

Content

The data used to populate the database table generated from this entity has been defined manually. Entries have been created to represent the following end-to-end journeys:

ID Starts from Destination Via Free Return?
1 London Moon Cape Canaveral Tick
2 Bangalore Moon Baikonur Tick
3 San Francisco Moon Cape Canaveral Tick
4 London Moon Cape Canaveral Cross
5 Bangalore Moon Baikonur Cross
6 San Francisco Moon Cape Canaveral Cross
7 London Mars Cape Canaveral Tick
8 Bangalore Mars Baikonur Tick
9 San Francisco Mars Cape Canaveral Tick
10 London Mars Cape Canaveral Cross
11 Bangalore Mars Baikonur Cross
12 San Francisco Mars Cape Canaveral Cross
13 Moon London Cape Canaveral Cross
14 Moon Bangalore Baikonur Cross
15 Moon San Francisco Cape Canaveral Cross
16 Mars (Jezero) London Cape Canaveral Cross
17 Mars (Jezero) Bangalore Baikonur Cross
18 Mars (Jezero) San Francisco Cape Canaveral Cross
19 Mars (Columbia) London Cape Canaveral Cross
20 Mars (Columbia) Bangalore Baikonur Cross
21 Mars (Columbia) San Francisco Cape Canaveral Cross

The runtime data is stored in the file itineraries.csv, which currently contains the 21 entries shown above.