Same messageID across all TPEG files
When one inspects TPEG EAW messages from the sample_data
folder, each of them has the same messageID
.
Example 1:
python3 ./TPEG/TPEG_parser.py ./sample_data/EAW_sample_data/TPEG_EAW_for_37A128001FE00BB8_20210504T092224.tpeg
displays the message with the following id:
Example 2: after generating a TPEG file from the CAP message using the commands:
python3 ./CAP/CAP_to_EAW.py ./sample_data/CAP_sample_data/CAP_evaluation_DE/01_Absturz_eines_Satelliten.cap
the command:
python3 ./TPEG/TPEG_parser.py ./sample_data/CAP_sample_data/CAP_evaluation_DE/TPEG_EAW_for_01_Absturz_eines_Satelliten_20230502T170838.tpeg
*(Note: the file 'TPEG_EAW_for_01_Absturz_eines_Satelliten_20230502T170838.tpeg' will have a slightly different name, depending on the date when the script is run)
displays the TPEG message with the following id:
whereas the original CAP message 01_Absturz_eines_Satelliten.cap
has the id of <identifier>DE-NW-BN-SE030-20210820-18-000</identifier>
and the KML file CAP_KML_for_01_Absturz_eines_Satelliten_20210827T125842.kml
has no id whatsoever.
The same problem occurs in all TPEG samples and generated TPEG EAW files.