|
|
|
|
|
1 TSO_2_0
|
|
|
|
2 CONTEXT
|
|
|
This part of the TSO identifies the context of each
instance of a TSO
|
|
|
3 ID
|
|
|
The identifier of the TSO which shall be
unique over the context in which the TSO is used. (Name of the element has
been changed in version 1.2)
|
|
|
3 MODE
|
Only allowed values are:
'ACTUAL' | 'EXERCS' | 'SYSTEM' | 'TEST'
|
|
|
It defines if the TSO is related to an actual
event (ACTUAL value), an exercise (EXERCS value) or a test (SYSTEM value
for messages that support alert network internal functions or TEST, for
technical testing only, all recipients disregard).
|
|
|
3 MSGTYPE
|
Only allowed values are:
'ALERT' | 'UPDATE' | 'CANCEL' | 'ACK' | 'ERROR'
|
|
|
The code denoting the nature of the alert
message. This element is mandatory. The possible values are: ACK =
Acknowledges receipt and acceptance of the message(s)) identified in
reference, ALERT = Initial information requiring attention by targeted
recipients, CANCEL = Cancels the earlier message(s) identified in
reference, ERROR = indicates rejection of the message(s) identified in
reference, UPDATE = Updates and supersedes the earlier message(s)
identified in reference.
|
|
|
3 CREATION
|
|
|
if string-length(.) <26
then
setDateMask(YYYY-MM-DD'T'HH:MI:SSZ)
end if;
|
if string-length(.) >25
then
setDateMask(YYYY-MM-DD'T'HH:MI:SS.SZ)
end if;
|
|
|
--- Modified in version 1.2 --- The date and
time when the TSO was created. This is the date and time of the sender
computer and receivers may not assume that this date and time is
accurate.
|
|
|
3 LINK
|
|
|
--- Modified in V1.2: multiple links are now
allowed, and an optional ROLE element has been added.
|
|
|
4 ID
|
|
|
The identifier of the TSO which shall be
unique over the context in which the TSO is used. (Name of the element has
been changed in version 1.2)
|
|
|
4 ROLE
|
|
|
--- New in version 1.2 --- Defines the
relation of the linked TSO through the data dictionary.
|
|
|
3 LEVEL
|
|
|
Only allowed values are:
'OPR' | 'STRTGC' | 'TACTCL'
|
|
|
It provides the level of the organisation
which provides the TSO (STRTGC = strategic, OPR = operational, TACTCL =
tactical)
|
|
|
3 SECLASS
|
|
|
Only allowed values are:
'CONFID' | 'RESTRC' | 'SECRET' | 'TOPSRT' | 'UNCLAS' | 'UNMARK'
|
|
|
--- Changed in version 1.4: name is changed,
UNMARK value is added --- It provides the confidentiality level of the TSO
(CONFID = confidential, RESTRC = restricted, SECRET = secret, TOPSRT = top
secret, UNCLAS = unclassified)
|
|
|
3 FREETEXT
|
|
|
A free text description of the TSO. This
element may be used to add non-normalised information.
|
|
|
3 URGENCY
|
|
|
Only allowed values are:
'URGENT' | 'NOT_URGENT'
|
|
|
--- Modified in version 1.2 --- Characterises
the urgency of the message. Possible values are URGENT and
NOT_URGENT.
|
|
|
3 ORIGIN
|
|
|
It provides the identity of the creator /
emitter of the TSO.
|
|
|
4 ORG_ID
|
|
|
--- Modified in version 1.2 --- It
provides the unique identifier for an organisation
element.
|
|
|
4 USER_ID
|
|
|
It provides the identifier of the user.
It shall be unique inside each organisation.
|
|
|
4 NAME
|
|
|
--- New in version 1.2 --- It provides
the name (and eventually other information such as a contact point, a
telephone number, an address) which identifies the agency and the
node.
|
|
|
3 EXTERNAL_INFO
|
|
|
Provides the capability to describe links to
additional external information Note: Implementations should consider how
this reference affects the interpretation of the TSO in the case where the
referenced TSO is not available to the recipient
|
|
|
4 FREETEXT
|
|
|
A free text description of the TSO. This
element may be used to add non-normalised information.
|
|
|
4 URI
|
with content type of "anyURI"
|
|
|
|
|
A full absolute URI, typically a
Uniform Resource Locator that can be used to retrieve the resource file
over the network (Internet, Intranet).
|
|
|
4 TYPE
|
|
|
--- New in version 1.2 --- This provides the type of the attached information such as PHOTO, MAP, MANUAL, WEBSITE (cf. the
TSO data dictionary).
|
|
|
2 EVENT
|
|
|
--- Mandatory for version 2.0 --- This part of the
TSO describes the event to which the emergency is
related.
|
|
|
3 ID
|
|
|
The identifier of the TSO which shall be
unique over the context in which the TSO is used. (Name of the element has
been changed in version 1.2)
|
|
|
3 NAME
|
|
|
--- New in version 1.2 --- It provides
the name (and eventually other information such as a contact point, a
telephone number, an address) which identifies the agency and the
node.
|
|
|
3 MAIN_EVENT_ID
|
|
|
--- New in version 1.2 --- Optional link to
the main event (in this case, the current event is a sub-event of this main
event).
|
|
|
3 ETYPE
|
|
|
--- Name changed for version 1.4 --- Name and
structure changed in version 1.2 --- It provides the type of the event
|
|
|
4 CATEGORY
|
|
|
It provides the description of the
scenario which lead to the event. The complete list is in the data
dictionary.
|
|
|
4 ACTOR
|
|
|
It provides the type of the endangered
object(s). Typical values are: Human, Animals, Critical site, Vehicle (car,
truck, ship, aircraft, train, metro, tramway, cable car, etc.). The
complete list is in the data dictionary.
|
|
|
4 LOCTYPE
|
|
|
It provides the type of the location
where the event is. The complete list is in the data
dictionary.
|
|
|
4 ENV
|
|
|
It provides the general environment (or
context) of the event. The complete list is in the data
dictionary.
|
|
|
3 SOURCE
|
|
|
Only allowed values are:
'COMFOR' | 'HUMDED' | 'HUMOBS' | 'SENSOR'
|
|
|
It describes the origin of the declaration of
the event (if it was detected by a human, by a system,
etc.).
|
|
|
3 SCALE
|
numeric with format "######"
|
|
|
|
|
|
3 CERTAINTY
|
numeric with format "######"
|
|
|
|
|
A percentage probability of occurrence of the
event (for example for events which are predicted). Note: this is typically
used for computerised prediction of a future event (such as a flood
prediction according to meteorological measures).
|
|
|
3 DECL_DATIME
|
|
|
if string-length(.) <26
then
setDateMask(YYYY-MM-DD'T'HH:MI:SSZ)
end if;
|
if string-length(.) >25
then
setDateMask(YYYY-MM-DD'T'HH:MI:SS.SZ)
end if;
|
|
|
The date and time of the declaration that
event has occurred or is about to occur.
|
|
|
3 OCC_DATIME
|
|
|
if string-length(.) <26
then
setDateMask(YYYY-MM-DD'T'HH:MI:SSZ)
end if;
|
if string-length(.) >25
then
setDateMask(YYYY-MM-DD'T'HH:MI:SS.SZ)
end if;
|
|
|
--- New in version 2.0 --- The date and time
of the occurence of the event.
|
|
|
3 OBS_DATIME
|
|
|
if string-length(.) <26
then
setDateMask(YYYY-MM-DD'T'HH:MI:SSZ)
end if;
|
if string-length(.) >25
then
setDateMask(YYYY-MM-DD'T'HH:MI:SS.SZ)
end if;
|
|
|
The date and time of the information
contained in this event description.
|
|
|
3 STATUS
|
|
|
Only allowed values are:
'NST' | 'IPR' | 'COM' | 'STOP'
|
|
|
The current status of the event: COM = event
complete, IPR= event in progress, NST= event not started -- New in version
1.3 -- STOP = event under control, no need for additional
resource.
|
|
|
3 RISK_ASSESSMNT
|
|
|
Only allowed values are:
'INCREA' | 'DECREA' | 'STABLE'
|
|
|
The foreseen evolution of the event
(increasing / decreasing / stable).
|
|
|
3 REFERENCE
|
|
|
--- New in V1.1 --- Provides the list of
events identifiers which may be related to the same
event.
|
|
|
4 ORG_ID
|
|
|
--- Modified in version 1.2 --- It
provides the unique identifier for an organisation
element.
|
|
|
4 OTHER_EVENT_ID
|
|
|
It provides identifiers for the same
event, if this event was also identified by other agencies. It shall help
to maintain the consistency between agencies which have their own
identification schemes.
|
|
|
3 CASUALTIES
|
|
|
Provides the count of the actual casualties
at the time of the CASUALTIES/ DATIME.
|
|
|
4 CONTEXT
|
Only allowed values are:
'REQ_ACTION' | 'ALR_TREATED' | 'PRED_URGENT' | 'PRED_MEDIUM' | 'INITIAL_STAT' | 'PRELIM_STAT'
|
|
|
This part of the TSO identifies the context of each
instance of a TSO
|
|
|
4 DATIME
|
|
|
if string-length(.) <26
then
setDateMask(YYYY-MM-DD'T'HH:MI:SSZ)
end if;
|
if string-length(.) >25
then
setDateMask(YYYY-MM-DD'T'HH:MI:SS.SZ)
end if;
|
|
|
--- Changed for version 1.2, as the
PREDICTED_CASUALTIES element has been removed --- For predicted contexts,
it provides the date and time of the prediction.
|
|
|
4 DECONT
|
|
|
numeric with format "######"
|
|
|
--- Name changed in version 1.2 ---
Number of individuals who need or are treated against CBRN agents in the
current context.
|
|
|
4 TRIAGERED
|
|
|
numeric with format "######"
|
|
|
This category has the highest priority
for treatment or evacuation, as urgent resuscitative interventions are
required to ensure survival of the casualty or patient. Examples include
airway obstruction, respiratory emergencies, shock and severe trauma. It is
likely that such cases will die within 2 hours or earlier, in the absence
of appropriate medical treatment.
|
|
|
4 TRIAGEYELLOW
|
|
|
numeric with format "######"
|
|
|
This comprises cases that require early
treatment, particularly surgery, and it is recommended that evacuation to a
surgical facility take place within 6 hours of injury. Examples include
visceral injury, closed thoracic injury without threatening asphyxia, major
limb injuries and fractures, closed head injury, open eye injury and
moderate burns.
|
|
|
4 TRIAGEGREEN
|
|
|
numeric with format "######"
|
|
|
Treatment is less urgent in this
category and can be deferred if there are other casualties requiring
limited treatment or evacuation assets. Examples include simple closed
fractures, soft tissue injury, closed chest injury and maxillary-facial
injury.
|
|
|
4 TRIAGEBLACK
|
|
|
numeric with format "######"
|
|
|
This category refers to casualties
whose injuries or illness are so serious that they have minimal chances of
survival or who are dead on arrival. Should there be competition for
limited medical resources, such cases will have lower priority for
evacuation or treatment, despite the severity of their condition. Examples
include brain-stem death and terminal illness.
|
|
|
4 MISSING
|
|
|
numeric with format "######"
|
|
|
Number of individuals reported or
presumed missing, kidnapped (etc) in the current
context.
|
|
|
3 EVAC
|
|
|
Provides the count of the actual persons who
are evacuated at the time of the EVAC/DATIME.
|
|
|
4 DATIME
|
|
|
if string-length(.) <26
then
setDateMask(YYYY-MM-DD'T'HH:MI:SSZ)
end if;
|
if string-length(.) >25
then
setDateMask(YYYY-MM-DD'T'HH:MI:SS.SZ)
end if;
|
|
|
--- Changed for version 1.2, as the
PREDICTED_CASUALTIES element has been removed --- For predicted contexts,
it provides the date and time of the prediction.
|
|
|
4 DISPLACED
|
|
|
numeric with format "######"
|
|
|
Number of people who are moved from
their home due to the event.
|
|
|
4 EVACUATED
|
|
|
numeric with format "######"
|
|
|
Number of individuals who are moved
outside their usual places of life (in shelter, in transport, awaiting
transport, etc..).
|
|
|
3 EGEO
|
|
|
--- Name changed in version 1.4 --- Provides
information on the geographical position of the event. Several geographical
areas could be provided, for example if several affected areas are
described.
|
|
|
4 DATIME
|
|
|
if string-length(.) <26
then
setDateMask(YYYY-MM-DD'T'HH:MI:SSZ)
end if;
|
if string-length(.) >25
then
setDateMask(YYYY-MM-DD'T'HH:MI:SS.SZ)
end if;
|
|
|
--- Changed for version 1.2, as the
PREDICTED_CASUALTIES element has been removed --- For predicted contexts,
it provides the date and time of the prediction.
|
|
|
4 TYPE
|
|
|
--- New in version 1.2 --- This provides the type of the attached information such as PHOTO, MAP, MANUAL, WEBSITE (cf. the
TSO data dictionary).
|
|
|
4 POSITION
|
|
|
Provides the position of the GEO element. Note: all
elements are optional, but at least one must be provided (it could be only
the LOC_ID, only the NAME, or only the TYPE and COORD, or a combination of
at least 2 of these elements).
|
|
|
5 LOC_ID
|
|
|
It provides an identifier, which is unique
inside the current TSO file. This identifier can be used in another part of
the TSO in order to avoid duplicating the same position object (cf. the
explanation of the TYPE element for an example of the use of this
element).
|
|
|
5 NAME
|
|
|
--- New in version 1.2 --- It provides
the name (and eventually other information such as a contact point, a
telephone number, an address) which identifies the agency and the
node.
|
|
|
5 TYPE
|
|
|
|
|
Only allowed values are:
| 'POINT' | 'CIRCLE' | 'LINE' | 'SURFACE' | 'GRID' | 'POLYGON' | 'ELLIPSE'
|
|
|
--- New in version 1.2 --- This provides the type of the attached information such as PHOTO, MAP, MANUAL, WEBSITE (cf. the
TSO data dictionary).
|
|
|
5 COORDSYS
|
|
|
--- New in version 2.0 --- It defines the
coordinate system in use in the TSO file. Currently the default and only
valid value is EPSG:4326, which corresponds to WGS-84.
|
|
|
5 COORD
|
|
|
--- Modified in V1.1: mutiple coordinates are
allowed, removed from the sequence --- Provides a sequence of geographical
points (one is the minimum) with at least their latitude and longitude and
optionally the height.
|
|
|
6 LAT
|
with data type of "double"
|
|
|
|
|
It provides the latitude of one point in the
provided coordinate system
|
|
|
6 LON
|
with data type of "double"
|
setNumberRange(-180-+180)
|
|
|
It provides the longitude of one point in the
provided coordinate system
|
|
|
6 HEIGHT
|
|
|
with data type of "double"
|
|
|
It provides the height above the mean sea level
in meters
|
|
|
5 HEIGHT_ROLE
|
|
|
Only allowed values are:
'MIN' | 'MAX' | 'AVE'
|
|
|
--- New in v1.2 --- This element provides the
meaning of the height parameter in the COORD element (if there is one).
Values can be: minimum, maximum, average.
|
|
|
5 ADDRESS
|
|
|
--- New in version 1.4 --- Provides a
physical address for this position. Includes the capability to provide
Marker Posts (Road infrastructure).
|
|
|
4 WEATHER
|
|
|
The weather at the location, from the
data dictionary. Where several WEATHER elements are present, all are
applicable.
|
|
|
4 FREETEXT
|
|
|
A free text description of the TSO. This
element may be used to add non-normalised information.
|
|
|
4 ID
|
|
|
The identifier of the TSO which shall be
unique over the context in which the TSO is used. (Name of the element has
been changed in version 1.2)
|
|
|
4 STATUS
|
|
|
Only allowed values are:
'GONE' | 'PLANNED' | 'INPLACE'
|
|
|
The current status of the event: COM = event
complete, IPR= event in progress, NST= event not started -- New in version
1.3 -- STOP = event under control, no need for additional
resource.
|
|
|
3 CAUSE
|
|
|
Only allowed values are:
'ACC' | 'DEL' | 'NAT'
|
|
|
--- New in version 1.4 --- Cause of this
event. Valid values are: ACC ? accidental, DEL ? deliberate, NAT ?
natural
|
|
|
3 FREETEXT
|
|
|
A free text description of the TSO. This
element may be used to add non-normalised information.
|
|
|
2 RESOURCE
|
|
|
--- Modified in V1.1: mutiple resources are
directly described at the top level --- This part of the TSO describes the
resources (human, vehicles, other hardware, etc...) which are involved in
an emergency. It describes each individual resource.
|
|
|
3 RTYPE
|
|
|
--- Name changed in version 1.4 --- New in
version 1.2 --- It provides a relatively detailed description of the
resource.
|
|
|
4 CLASS
|
|
|
It provides the type of the resource
(rescue team, vehicle, tent, water purifier, etc...). The type is an
string, one acronym in the TSO data dictionary.
|
|
|
4 CAPABILITY
|
|
|
It provides the main domains of
capabilities and competencies of the resource. It is a string, from the TSO
data dictionary.
|
|
|
4 CHARACTERISTICS
|
|
|
It provides information about the
physical main characteristics of the resource (heigth, weight, size, etc.).
It is a string, from the TSO data dictionary.
|
|
|
3 ID
|
|
|
The identifier of the TSO which shall be
unique over the context in which the TSO is used. (Name of the element has
been changed in version 1.2)
|
|
|
3 ORG_ID
|
|
|
--- Modified in version 1.2 --- It
provides the unique identifier for an organisation
element.
|
|
|
3 NAME
|
|
|
--- New in version 1.2 --- It provides
the name (and eventually other information such as a contact point, a
telephone number, an address) which identifies the agency and the
node.
|
|
|
3 FREETEXT
|
|
|
A free text description of the TSO. This
element may be used to add non-normalised information.
|
|
|
3 RGEO
|
|
|
--- Name changed in version 1.4 --- New in
version 1.3 --- it allows to define several position of the resource at
different times.
|
|
|
4 DATIME
|
|
|
if string-length(.) <26
then
setDateMask(YYYY-MM-DD'T'HH:MI:SSZ)
end if;
|
if string-length(.) >25
then
setDateMask(YYYY-MM-DD'T'HH:MI:SS.SZ)
end if;
|
|
|
--- Changed for version 1.2, as the
PREDICTED_CASUALTIES element has been removed --- For predicted contexts,
it provides the date and time of the prediction.
|
|
|
4 TYPE
|
|
|
--- New in version 1.2 --- This provides the type of the attached information such as PHOTO, MAP, MANUAL, WEBSITE (cf. the
TSO data dictionary).
|
|
|
4 POSITION
|
|
|
Provides the position of the GEO element. Note: all
elements are optional, but at least one must be provided (it could be only
the LOC_ID, only the NAME, or only the TYPE and COORD, or a combination of
at least 2 of these elements).
|
|
|
5 LOC_ID
|
|
|
It provides an identifier, which is unique
inside the current TSO file. This identifier can be used in another part of
the TSO in order to avoid duplicating the same position object (cf. the
explanation of the TYPE element for an example of the use of this
element).
|
|
|
5 NAME
|
|
|
--- New in version 1.2 --- It provides
the name (and eventually other information such as a contact point, a
telephone number, an address) which identifies the agency and the
node.
|
|
|
5 TYPE
|
|
|
|
|
Only allowed values are:
| 'POINT' | 'CIRCLE' | 'LINE' | 'SURFACE' | 'GRID' | 'POLYGON' | 'ELLIPSE'
|
|
|
--- New in version 1.2 --- This provides the type of the attached information such as PHOTO, MAP, MANUAL, WEBSITE (cf. the
TSO data dictionary).
|
|
|
5 COORDSYS
|
|
|
--- New in version 2.0 --- It defines the
coordinate system in use in the TSO file. Currently the default and only
valid value is EPSG:4326, which corresponds to WGS-84.
|
|
|
5 COORD
|
|
|
--- Modified in V1.1: mutiple coordinates are
allowed, removed from the sequence --- Provides a sequence of geographical
points (one is the minimum) with at least their latitude and longitude and
optionally the height.
|
|
|
6 LAT
|
with data type of "double"
|
|
|
|
|
It provides the latitude of one point in the
provided coordinate system
|
|
|
6 LON
|
with data type of "double"
|
setNumberRange(-180-+180)
|
|
|
It provides the longitude of one point in the
provided coordinate system
|
|
|
6 HEIGHT
|
|
|
with data type of "double"
|
|
|
It provides the height above the mean sea level
in meters
|
|
|
5 HEIGHT_ROLE
|
|
|
Only allowed values are:
'MIN' | 'MAX' | 'AVE'
|
|
|
--- New in v1.2 --- This element provides the
meaning of the height parameter in the COORD element (if there is one).
Values can be: minimum, maximum, average.
|
|
|
5 ADDRESS
|
|
|
--- New in version 1.4 --- Provides a
physical address for this position. Includes the capability to provide
Marker Posts (Road infrastructure).
|
|
|
4 FREETEXT
|
|
|
A free text description of the TSO. This
element may be used to add non-normalised information.
|
|
|
4 ID
|
|
|
The identifier of the TSO which shall be
unique over the context in which the TSO is used. (Name of the element has
been changed in version 1.2)
|
|
|
3 QUANTITY
|
|
|
with data type of "double"
|
|
|
It provides the quantity of this type of
resource in the unit of measure provided in the UM
element.
|
|
|
3 UM
|
|
|
It provides the unit for the quantity. The
type is a string, one acronym in the TSO data
dictionary.
|
|
|
3 STATUS
|
|
|
Only allowed values are:
'AVAILB' | 'UNAV' | 'MAINTC' | 'RESRVD' | 'VIRTUAL' | 'IN_USE' | 'IN_USE/MOBILE' | 'IN_USE/ON_SCENE' | 'REQUEST'
|
|
|
The current status of the event: COM = event
complete, IPR= event in progress, NST= event not started -- New in version
1.3 -- STOP = event under control, no need for additional
resource.
|
|
|
3 NATIONALITY
|
|
|
It provides the national origin of this
resource. It is a string, from the ISO 3166-1-alpha-2 code
elements.
|
|
|
3 CONTACT
|
|
|
--- Name changed in version 1.4 --- It
provides one or several addresses for a resource. This could be postal
addresses or electronic addresses (the type is
mandatory).
|
|
|
4 TYPE
|
Only allowed values are:
'PSTADD' | 'EMLADD' | 'IPADD' | 'FTPADD' | 'WWWADD' | 'PHNADD' | 'FAXADD' | 'PMRADD'
|
|
|
--- New in version 1.2 --- This provides the type of the attached information such as PHOTO, MAP, MANUAL, WEBSITE (cf. the
TSO data dictionary).
|
|
|
4 DETAIL
|
|
|
It provides one actual address of the
resource.
|
|
|
2 MISSION
|
|
|
--- Modified in V1.1: mutiple missions are directly
described at the top level --- This part of the TSO describes the missions
which are completed, which are active and which are planned. It describes
each individual mission
|
|
|
3 TYPE
|
|
|
--- New in version 1.2 --- This provides the type of the attached information such as PHOTO, MAP, MANUAL, WEBSITE (cf. the
TSO data dictionary).
|
|
|
3 FREETEXT
|
|
|
A free text description of the TSO. This
element may be used to add non-normalised information.
|
|
|
3 ID
|
|
|
The identifier of the TSO which shall be
unique over the context in which the TSO is used. (Name of the element has
been changed in version 1.2)
|
|
|
3 MAIN_MISSION_ID
|
|
|
--- New in version 1.2 --- Optional link to
the main mission (in this case, the current mission is a sub-mission of
this main mission)
|
|
|
3 ORG_ID
|
|
|
--- Modified in version 1.2 --- It
provides the unique identifier for an organisation
element.
|
|
|
3 NAME
|
|
|
--- New in version 1.2 --- It provides
the name (and eventually other information such as a contact point, a
telephone number, an address) which identifies the agency and the
node.
|
|
|
3 STATUS
|
|
|
The current status of the event: COM = event
complete, IPR= event in progress, NST= event not started -- New in version
1.3 -- STOP = event under control, no need for additional
resource.
|
|
|
3 START_TIME
|
|
|
if string-length(.) <26
then
setDateMask(YYYY-MM-DD'T'HH:MI:SSZ)
end if;
|
if string-length(.) >25
then
setDateMask(YYYY-MM-DD'T'HH:MI:SS.SZ)
end if;
|
|
|
It provides the date and time when this
mission begins.
|
|
|
3 END_TIME
|
|
|
if string-length(.) <26
then
setDateMask(YYYY-MM-DD'T'HH:MI:SSZ)
end if;
|
if string-length(.) >25
then
setDateMask(YYYY-MM-DD'T'HH:MI:SS.SZ)
end if;
|
|
|
It provides the date and time when this
mission is supposed to finish.
|
|
|
3 RESOURCE_ID
|
|
|
Provides the link with the description in the
RESOURCE/ID element(s).
|
|
|
3 PARENT_MISSION_ID
|
|
|
It provides the list of the missions which
shall be completed before the beginning of this mission.
|
|
|
3 CHILD_MISSION_ID
|
|
|
It provides the list of the missions which
shall start when this mission is finished.
|
|
|
3 POSITION
|
|
|
Provides the position of the GEO element. Note: all
elements are optional, but at least one must be provided (it could be only
the LOC_ID, only the NAME, or only the TYPE and COORD, or a combination of
at least 2 of these elements).
|
|
|
4 LOC_ID
|
|
|
It provides an identifier, which is unique
inside the current TSO file. This identifier can be used in another part of
the TSO in order to avoid duplicating the same position object (cf. the
explanation of the TYPE element for an example of the use of this
element).
|
|
|
4 NAME
|
|
|
--- New in version 1.2 --- It provides
the name (and eventually other information such as a contact point, a
telephone number, an address) which identifies the agency and the
node.
|
|
|
4 TYPE
|
|
|
|
|
Only allowed values are:
| 'POINT' | 'CIRCLE' | 'LINE' | 'SURFACE' | 'GRID' | 'POLYGON' | 'ELLIPSE'
|
|
|
--- New in version 1.2 --- This provides the type of the attached information such as PHOTO, MAP, MANUAL, WEBSITE (cf. the
TSO data dictionary).
|
|
|
4 COORDSYS
|
|
|
--- New in version 2.0 --- It defines the
coordinate system in use in the TSO file. Currently the default and only
valid value is EPSG:4326, which corresponds to WGS-84.
|
|
|
4 COORD
|
|
|
--- Modified in V1.1: mutiple coordinates are
allowed, removed from the sequence --- Provides a sequence of geographical
points (one is the minimum) with at least their latitude and longitude and
optionally the height.
|
|
|
5 LAT
|
with data type of "double"
|
|
|
|
|
It provides the latitude of one point in the
provided coordinate system
|
|
|
5 LON
|
with data type of "double"
|
setNumberRange(-180-+180)
|
|
|
It provides the longitude of one point in the
provided coordinate system
|
|
|
5 HEIGHT
|
|
|
with data type of "double"
|
|
|
It provides the height above the mean sea level
in meters
|
|
|
4 HEIGHT_ROLE
|
|
|
Only allowed values are:
'MIN' | 'MAX' | 'AVE'
|
|
|
--- New in v1.2 --- This element provides the
meaning of the height parameter in the COORD element (if there is one).
Values can be: minimum, maximum, average.
|
|
|
4 ADDRESS
|
|
|
--- New in version 1.4 --- Provides a
physical address for this position. Includes the capability to provide
Marker Posts (Road infrastructure).
|
|
|
3 PRIORITY
|
numeric with format "######"
|
|
|
|
|
It provides the priority level for this
mission (an integer between 0=low priority to 5=highest
priority).
|
|