Fix Documentation artefacts, include latest asnimports.py

* signal phase and timing via the SPAT message) to events at specific geographic locations on the roadway.

*

* @field timeStamp: time reference

* @field msgIssueRevision: The MapData revision is defined by the data element `revision` for each intersection

* @field msgIssueRevision: The MapData revision is defined by the data element **revision** for each intersection

*                          geometry (see [ISO TS 19091] G.8.2.4.1). Therefore, an additional revision indication of the overall

*                          MapData message is not used in this profile. It shall be set to "0" for this profile.

* @field layerType: There is no need to additionally identify the topological content by an additional identifier. The ASN.1

*                   definition of the data frames `intersections` and `roadSegments` are clearly defined and need no

*                   definition of the data frames **intersections** and **roadSegments** are clearly defined and need no

*                   additional identifier. Therefore, this optional data element shall not be used in this profile.

* @field layerID: This profile extends the purpose of the `layerID` data element as defined in SAE J2735 as follows: For

* @field layerID: This profile extends the purpose of the **layerID** data element as defined in SAE J2735 as follows: For

*                 large intersections, the length of a MapData description may exceed the maximum data length of the

*                 communication message. Therefore, a fragmentation of the MapData message (at application layer) in

*                 two or more MapData fragments may be executed. If no MapData fragmentation is needed, the `layerID`

*                 two or more MapData fragments may be executed. If no MapData fragmentation is needed, the **layerID**

*                 shall not be used. For more details, see the definition of the data element @ref LayerID.

* @field intersections: All Intersection definitions.

* @field roadSegments: All roadway descriptions.

* @field lane: Index of the connecting lane.

*

* @field maneuver: This data element allows only the description of a subset of possible manoeuvres and therefore

*    represents an incomplete list of possible travel directions. The connecting `lane` data element gives the

*    represents an incomplete list of possible travel directions. The connecting **lane** data element gives the

*    exact information about the manoeuvre relation from ingress to egress lane. Therefore the "maneuver"

*    data element may be used only additionally if the travel direction of the manoeuvre is unanmbigoulsy

*    represented (e.g. left, right, straight, etc.).

/**

* This DF is used to combine/connect multiple physical lanes (i.e. within intersections or road

* segments). For signalized movements, the `connectsTo` data frame defines e.g. the relation between

* segments). For signalized movements, the **connectsTo** data frame defines e.g. the relation between

* ingress and egress lanes within an intersection. It describes the allowed manoeuvres and includes the

* link (`signalGroup` identifier) between the @ref MapData and the @ref PAT message. The data frame is also used

* link (**signalGroup** identifier) between the @ref MapData and the @ref SPAT message. The data frame is also used

* to describe the relation of lanes within a non signalized intersection (e.g. ingress lanes which are

* bypassing the conflict area and ending in an egress lane without signalization). Within a road segment,

* it is used to combine two or multiple physical lanes into a single lane object.

*

* @field connectingLane: 

* @field remoteIntersection: When the data element `remoteIntersection` is used, it indicates

* @field remoteIntersection: When the data element **remoteIntersection** is used, it indicates

*                            that the connecting lane belongs to another intersection. 

*                            (see clause [ISO TS 19091] G.9.1 for further explainations).

* @field signalGroup: 

* constructing a separate lane object in the intersection map for each different configuration, a single unified map can be

* developed and used.

*

* Contents are the unique ID numbers for each lane object which is 'active' as part of the dynamic map contents.

* Contents are the unique ID numbers for each lane object which is **active** as part of the dynamic map contents.

*

* @category: Infrastructure information

* @revision: V1.3.1

* @field egressApproach: outbound Approach ID to which this lane belongs

* @field laneAttributes: All Attribute information about the basic selected lane type

*                        Directions of use, Geometric co-sharing and Type Specific Attributes

*                        These Attributes are 'lane - global' that is, they are true for the entire length of the lane

*                        These Attributes are **lane - global** that is, they are true for the entire length of the lane

* @field maneuvers: This data element allows only the description of a subset of possible manoeuvres and therefore

*                    reperesents an incomplete list of possible travel directions. The connecting `lane` data element gives

*                    reperesents an incomplete list of possible travel directions. The connecting **lane** data element gives

*                    the exact information about the manoeuvre relation from ingress to egress lane. Therefore the

*                    "maneuver" data element is used only additionally if the travel direction of the manoeuvre is

* @field nodeList: Lane spatial path information as well as various Attribute information along the node path

*                    the path of this lane when used

* @field regional: optional region specific data.

*

* @note: The data elements `ingressApproach` and `egressApproach` are used for grouping lanes whin an

* @note: The data elements **ingressApproach** and **egressApproach** are used for grouping lanes whin an

*       approach (e.g. lanes defined in travel direction towards the intersection, lanes in exiting direction and

*       cross walks). For a bidirectrional lane (e.g. bike lane) both dataelements are used for the same lane. The

*       integer value used for identifying the `ingressApproach` and the `egressAproach`, based on the

*       integer value used for identifying the **ingressApproach** and the **egressAproach**, based on the

*       topology, may be e.g. the same for all lanes within an approach of an intersection.

* @category: Infrastructure information

* @revision: V1.3.1

*

* @field name: For debug use only

* @field id: A globally unique value set, consisting of a regionID and intersection ID assignment

* @field revision: This profile extends the purpose of the `revision` data element as defined in SAE J2735 as follows.

* @field revision: This profile extends the purpose of the **revision** data element as defined in SAE J2735 as follows.

*           The revision data element is used to communicate the valid release of the intersection geometry

*           description. If there are no changes in the deployed intersection description, the same revision counter

*           is transmitted. Due to a revised deployment of the intersection description (e.g. new lane added, ID's

*           changed, etc.), the revision is increased by one. After revision equal to 127, the increment restarts by 0.

*           The intersection geometry and the signal phase and timing information is related each other. Therefore,

*           the revision of the intersection geometry of the MapData message shall be the same as the revision of

*           the intersection state of the SPAT (see data element `revision` of `DF_IntersectionState` in [ISO TS 19091] G.8.2.9)

*           the intersection state of the SPAT (see data element **revision** of **DF_IntersectionState** in [ISO TS 19091] G.8.2.9)

* @field refPoint: The reference from which subsequent data points are offset until a new point is used.

* @field laneWidth: Reference width used by all subsequent lanes unless a new width is given

* @field speedLimits: Reference regulatory speed limits used by all subsequent lanes unless a new speed is given

* @field id: A globally unique value set, consisting of a regionID and intersection ID assignment

*            provides a unique mapping to the intersection MAP in question which provides complete location

*            and approach/move/lane data

* @field revision: The data element `revision` is used to communicate the actual valid release of the intersection

* @field revision: The data element **revision** is used to communicate the actual valid release of the intersection

*                  description. If there are no changes in the deployed intersection description, almost the same revision

*                  counter is transmitted. Due to a revised deployment of the intersection description (e.g. introduction of

*                  additional signal state element), the revision is increased by one. After revision equal to 127, the

*                  increment leads to 0 (due to the element range).

*                  The intersection state and the intersection geometry is related to each other. Therefore, the revision of

*                  the intersection state shall be the same as the revision of the intersection geometry (see the data

*                  element `revision` of `DF_IntersectionGeometry` in [ISO TS 19091] G.8.2.6).

*                  element **revision** of **DF_IntersectionGeometry** in [ISO TS 19091] G.8.2.6).

* @field status: general status of the controller(s)

* @field moy: Minute of current UTC year, used only with messages to be archived.

* @field timeStamp: the mSec point in the current UTC minute that this message was constructed.

* - 8 - trackedVehicleTraffic:

* - 9 - pedestrianTraffic:

*

* @note: All zeros would indicate `not shared` and `not overlapping`

* @note: All zeros would indicate **not shared** and **not overlapping**

* @category: Infrastructure information

* @revision: V1.3.1

*/

/**

* All the node attributes defined in this DF are valid in the direction of

* node declaration and not in driving direction (i.e. along the sequence of the declared nodes). E.g. node

* attributes of an `ingress` or an `egress` lane are defined from the conflict area (first node) to the

* outside of the intersection (last node). Node attributes with ‘left’ and ‘right’ in their name are also

* attributes of an **ingress** or an **egress** lane are defined from the conflict area (first node) to the

* outside of the intersection (last node). Node attributes with **left** and **right** in their name are also

* defined in the direction of the node declaration. This allows using attributes in a unambigious way also

* for lanes with biderctional driving. See the following attribuets examples for additianl explanations.

*

/**

* This DE is an enumerated list of attributes which can pertain to the current node

* point. The 'scope' of these values is limited to the node itself. That is, unlike other types of attributes which can be

* point. The **scope** of these values is limited to the node itself. That is, unlike other types of attributes which can be

* switched on or off at any given node (and hence pertains to one or more segments), the DE_NodeAttribute is local to the

* node in which it is found. These attributes are all binary flags in that they do not need to convey any additional data. Other

* attributes allow sending short data values to reflect a setting which is set and persists in a similar fashion.

*

*  - reserved:             do not use

*  - stopLine:             point where a mid-path stop line exists. See also 'do not block' for segments

*  - stopLine:             point where a mid-path stop line exists. See also **do not block** for segments

*  - roundedCapStyleA:     Used to control final path rounded end shape with edge of curve at final point in a circle

*  - roundedCapStyleB:     Used to control final path rounded end shape with edge of curve extending 50% of width past final point in a circle

*  - mergePoint:           merge with 1 or more lanes

* @field lat: Latitude in 1/10th microdegrees

* @field long: Longitude in 1/10th microdegrees

* @field elevation: The elevation information is defined by the regional extension (see module ETSI-ITS-DSRC-AddGrpC). 

*                   Therefore, the `elevation` data element of `DF_Position3D` is not used.

*                   Therefore, the **elevation** data element of **DF_Position3D** is not used.

* @field regional: optional region specific data.

*

* @category: Infrastructure information

/**

* This DF expresses the speed of the vehicle and the state of the transmission.

* The transmission state of 'reverse' can be used as a sign value for the speed element when needed.

* The transmission state of **reverse** can be used as a sign value for the speed element when needed.

*

* @field transmisson: state of the transmission

* @field speed: speed of the vehicle

* - `noValidSPATisAvailableAtThisTime`      - 13: SPAT system is not working at this time

* - Bits 14,15 reserved at this time and shall be zero

*

* @note: All zeros indicate normal operating mode with no recent changes. The duration of the term 'recent' is defined by the system performance requirement in use.

* @note: All zeros indicate normal operating mode with no recent changes. The duration of the term **recent** is defined by the system performance requirement in use.

* @category: Infrastructure information

* @revision: V1.3.1

*/

* - `bikeRevocableLane`       - 0: this lane may be activated or not based on the current SPAT message contents if not asserted, the lane is ALWAYS present

* - `pedestrianUseAllowed`    - 1: The path allows pedestrian traffic, if not set, this mode is prohibited

* - `isBikeFlyOverLane`       - 2: path of lane is not at grade

* - `fixedCycleTime`          - 3: the phases use preset times, i.e. there is not a 'push to cross' button

* - `fixedCycleTime`          - 3: the phases use preset times, i.e. there is not a **push to cross** button

* - `biDirectionalCycleTimes` - 4: ped walk phases use different SignalGroupID for each direction. The first SignalGroupID in the first Connection

*                                  represents 'inbound' flow (the direction of travel towards the first node point) while second SignalGroupID in the

*                                  next Connection entry represents the 'outbound' flow. And use of RestrictionClassID entries in the Connect follow this same pattern in pairs.

*                                  represents **inbound** flow (the direction of travel towards the first node point) while second SignalGroupID in the

*                                  next Connection entry represents the `outbound` flow. And use of RestrictionClassID entries in the Connect follow this same pattern in pairs.

* - `isolatedByBarrier`           - 5: The lane path is isolated by a fixed barrier

* - `unsignalizedSegmentsPresent` - 6: The lane path consists of one of more segments which are not part of a signal group ID

* - Bits 7-15 reserved and set to zero

* - `crosswalkRevocableLane`  - 0:  this lane may be activated or not based on the current SPAT message contents if not asserted, the lane is ALWAYS present

* - `bicyleUseAllowed`        - 1: The path allows bicycle traffic, if not set, this mode is prohibited

* - `isXwalkFlyOverLane`      - 2: path of lane is not at grade

* - `fixedCycleTime`          - 3: ped walk phases use preset times. i.e. there is not a 'push to cross' button

* - `fixedCycleTime`          - 3: ped walk phases use preset times. i.e. there is not a **push to cross** button

* - `biDirectionalCycleTimes` - 4:  ped walk phases use different SignalGroupID for each direction. The first SignalGroupID

*                                   in the first Connection represents 'inbound' flow (the direction of travel towards the first

*                                   node point) while second SignalGroupID in the next Connection entry represents the 'outbound'

*                                   in the first Connection represents **inbound** flow (the direction of travel towards the first

*                                   node point) while second SignalGroupID in the next Connection entry represents the **outbound**

*                                   flow. And use of RestrictionClassID entries in the Connect follow this same pattern in pairs.

* - `hasPushToWalkButton`     - 5: Has a demand input

* - `audioSupport`            - 6:  audio crossing cues present

* index for fragmentation of large @ref MapData descriptions. The fragmentation of the messages shall be

* executed on application layer. The fragmentation occurs on an approach base. This means that almost a

* complete approach (e.g. lanes, connectsTo, etc.) has to be included within a fragment.

* The decimal value of the `layerID` is used to define the amount of maximum @ref MapData fragments. The

* The decimal value of the **layerID** is used to define the amount of maximum @ref MapData fragments. The

* lower value defines the actual fragment.

*

* Example:

* Values:

* - `unavailable` - 0:         This state is used for unknown or error

* - `dark` - 1:                The signal head is dark (unlit)

* - `stop-Then-Proceed` - 2:   Often called 'flashing red'

* - `stop-Then-Proceed` - 2:   Often called **flashing red**

*                              Driver Action:

*                              - Stop vehicle at stop line.

*                              - Do not proceed unless it is safe.

*                              Note that the right to proceed either right or left when it is safe may be contained in the lane description to

*                              handle what is called a 'right on red'

* - `stop-And-Remain` - 3:     e.g. called 'red light'

*                              handle what is called a **right on red**

* - `stop-And-Remain` - 3:     e.g. called **red light**

*                              Driver Action:

*                              - Stop vehicle at stop line.

*                              - Do not proceed.

*                              Note that the right to proceed either right or left when it is safe may be contained in the lane description to

*                              handle what is called a 'right on red'

*                              handle what is called a **right on red**

* - `pre-Movement` - 4:        Not used in the US, red+yellow partly in EU

*                              Driver Action:

*                              - Stop vehicle.

*                              - Prepare to proceed (pending green)

*                              - (Prepare for transition to green/go)

* - `permissive-Movement-Allowed` - 5: Often called 'permissive green'

* - `permissive-Movement-Allowed` - 5: Often called **permissive green**

*                              Driver Action:

*                              - Proceed with caution,

*                              - must yield to all conflicting traffic

*                              Conflicting traffic may be present in the intersection conflict area

* - `protected-Movement-Allowed` - 6: Often called 'protected green'

* - `protected-Movement-Allowed` - 6: Often called **protected green**

*                              Driver Action:

*                              - Proceed, tossing caution to the wind, in indicated (allowed) direction.

* - `permissive-clearance` - 7: Often called 'permissive yellow'.

* - `permissive-clearance` - 7: Often called **permissive yellow**.

*                              The vehicle is not allowed to cross the stop bar if it is possible

*                              to stop without danger.

*                              Driver Action:

*                              - Proceed if unable to stop,

*                              - Clear Intersection.

*                              Conflicting traffic may be present in the intersection conflict area

* - `protected-clearance` - 8:  Often called 'protected yellow'

* - `protected-clearance` - 8:  Often called **protected yellow**

*                              Driver Action:

*                              - Prepare to stop.

*                              - Proceed if unable to stop, in indicated direction (to connected lane)

*                              - Clear Intersection.

* - `caution-Conflicting-Traffic` - 9: Often called 'flashing yellow'

* - `caution-Conflicting-Traffic` - 9: Often called **flashing yellow**

*                              Often used for extended periods of time

*                              Driver Action:

*                              - Proceed with caution,

* - headInParking:   Parking at an angle with the street

* - freeParking:     No restriction on use of parking

* - timeRestrictionsOnParking: Parking is not permitted at all times

*                              typically used when the 'parking' lane becomes a driving lane at times

*                              typically used when the **parking** lane becomes a driving lane at times

* - costToPark: Used where parking has a cost

* - midBlockCurbPresent: a protruding curb near lane edge

* - unEvenPavementPresent: a disjoint height at lane edge

The correctness of these ASN.1 files can be verified using the bash script **syntax_check.sh**

See the notes in this script for further details.

For convenience a Dockerfile is available that might be useful for this.

See the notes in this script for further details. Output of current run:

```

Usage:

	>docker build -t etsi-its-asn-is:2.2.2 .

	>docker run -v `pwd`:/home/etsi-its-asn1 etsi-its-asn-is:2.2.2

file IVIM-PDU-Descriptions.asn

  process IVIM-PDU-Descriptions-0-4-0-5-1-103301-2-2-1

    found IVI-1-0-19321-3-WS - enqueue successor

    found ETSI-ITS-CDD-0-4-0-5-1-102894-2-4-WS - enqueue successor

file cdd/ETSI-ITS-CDD.asn

  process ETSI-ITS-CDD-0-4-0-5-1-102894-2-4-2

  remove successor

file DSRC.asn

  process ETSI-ITS-DSRC-0-4-0-5-1-103301-6-2-1

    found ETSI-ITS-CDD-0-4-0-5-1-102894-2-4-WS - successor exist

    found ETSI-ITS-DSRC-REGION-0-4-0-5-1-103301-6-1-2-WS - enqueue successor

file DSRC-addgrp-C.asn

  process ETSI-ITS-DSRC-AddGrpC-0-4-0-5-1-103301-6-0-2-1

    found ETSI-ITS-DSRC-0-4-0-5-1-103301-6-2-1 - already exist

    found ETSI-ITS-CDD-0-4-0-5-1-102894-2-4-WS - successor exist

file DSRC-region.asn

  process ETSI-ITS-DSRC-REGION-0-4-0-5-1-103301-6-1-2-1

  remove successor

    found ETSI-ITS-DSRC-0-4-0-5-1-103301-6-2-1 - already exist

    found ETSI-ITS-DSRC-AddGrpC-0-4-0-5-1-103301-6-0-2-1 - already exist

file .external/IVI-1-0-19321-3-WS.asn

  process IVI-1-0-19321-3-1

    found ETSI-ITS-CDD-0-4-0-5-1-102894-2-4-WS - successor exist

    found EfcDataDictionary-1-0-17573-3-1-WS - enqueue successor

    found GddVersion1-1-0-14823-1-1-WS - enqueue successor

    found IVI-IS - enqueue

file .external/EfcDataDictionary-1-0-17573-3-1-WS.asn

  process EfcDataDictionary-1-0-17573-3-1-3

file .external/GddVersion1-1-0-14823-1-1-WS.asn

  process GddVersion1-1-0-14823-1-1-1

file .external/IVI-IS.asn

  process IVI-IS

    found IVI-1-0-19321-3-1 - already exist

++++++++++++++++++++++++

+++ SUCCESS

+++ All modules compiled

a5a97244c826797fc7dab4cf506a04fd1ec6a6369c31a9315b4d6ee5a4146da5  DSRC-addgrp-C.asn

55b2592f630a0104a2d03db7faebd387c50a4345471969585faafa621b67c55a  DSRC-region.asn

45ec89805ba1ae7133c025811c287037d9a2131e6ba513261e5a4b8bb5cdf34c  DSRC.asn

a8a4ea41c05554ccc414284c9f0336fa1d2e631aa5bc3516f67fb6b6c6df5d87  IVIM-PDU-Descriptions.asn

b5c0d28ae238d905bd2d0b54b74291ea9fbf5d4093ddf27b367ac4a99fe8f040  MAPEM-PDU-Descriptions.asn

0786da745470771b599f9dead7b7141f16aead2e73c1234c6804b652264feac2  RTCMEM-PDU-Descriptions.asn

f41b051f9703e16d80fd45cec47b5359fd257a071cca4e18f2795b473ad5a144  SPATEM-PDU-Descriptions.asn

8381a329ed5259679bacc1919b8de16976d057828217d04a10a3b6946aa59596  SREM-PDU-Descriptions.asn

9b71acfcd8d193892da1f9bc9e3e238269366d030ac11fcaf48cfd0b9b230658  SSEM-PDU-Descriptions.asn

++++++++++++++++++++++++

```

Subproject commit 2c263b52d9aa3b7b613c9ca8f8c4bbc70c57be18

Subproject commit 78d1d090bc72ce60763e3163ea9772cbfc6d39c8