Page tree
Skip to end of metadata
Go to start of metadata

ID:

AIXM-425

target version:

AIXM 5.2

version:

1.0

last updated:

10 OCT 2019

status:

APPROVED


Description

New codes for start/end twilight are added in the CodeTimeEventBaseType.

Rationale for change

See https://aixmccb.atlassian.net/browse/AIXM-377 

The meaning of 'day' and 'night' is not the same in the world. For European States that apply the "SERA Regulation" (European Union Commission Implementing Regulation (EU) No 923/2012), ‘night’ might actually mean "the hours between the end of evening civil twilight and the beginning of morning civil twilight. Civil twilight ends in the evening when the centre of the sun’s disc is 6 degrees below the horizon and begins in the morning when the centre of the sun’s disc is 6 degrees below the horizon."

In this case, different values are used for start/end event when coding HJ/HN codes. In AIXM 5.1(.1) OTHER has to be used:

  • Timesheet.startEvent='OTHER:START_MORNING_CIVIL_TWILIGHT'
  • Timesheet.endEvent='OTHER:END_EVENING_CIVIL_TWILIGHT'

Impact assessment

AIXM 5.1.1 files remain valid against the AIXM 5.2 schema as no value is removed. In existing systems, the missing values can be coded prefixed with “OTHER:”, thus making it suitable for automatic conversion into proper values in AIXM 5.2.

AIXM 5.2 files that use the new values would be invalid against the AIXM 5.1.1 schema and will need to be converted, using the data type extension mechanism - prefix with “OTHER:”. The conversion is straightforward.

Change Proposal details

In the UML model add the following code values to CodeTimeEventBaseType:

  • BMCT = “Beginning of morning civil twilight, which is the time when the centre of the sun’s disc is 6 degrees below the horizon.
  • EECT = “End of evening civil twilight, which is the time when the centre of the sun’s disc is 6 degrees below the horizon.

The additional values are shown in the UML class diagram to the right.

Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

[MAPC-01] The following data conversion algorithm is proposed:

  • For each Timesheet.startEvent
    • Replace “OTHER:START_MORNING_CIVIL_TWILIGHT” with “BMCT”
    • Replace “OTHER:END_EVENING_CIVIL_TWILIGHT” with  “EECT”
  • For each Timesheet.endEvent
    • Replace “OTHER:START_MORNING_CIVIL_TWILIGHT” with “BMCT”
    • Replace “OTHER:END_EVENING_CIVIL_TWILIGHT” with  “EECT”

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

[MAPC-01] The following data conversion algorithm is proposed:

  • For each Timesheet.startEvent that has the value “BMCT”:
    • Replace the value with “OTHER:START_MORNING_CIVIL_TWILIGHT”
  • For each Timesheet.startEvent that has the value “EECT”:
    • Replace the value with “OTHER:END_EVENING_CIVIL_TWILIGHT”
  • For each Timesheet.endEvent that has the value “BMCT”:
    • Replace the value with “OTHER:START_MORNING_CIVIL_TWILIGHT”
  • For each Timesheet.endEvent that has the value “EECT”:
    • Replace the value with “OTHER:END_EVENING_CIVIL_TWILIGHT”


Mapping example

Mapping examples to be added...


(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx

AIXM 5.2AIXM 5.1(.1)
  ...





...



  • No labels