Informējam, ka Sistēma pielāgota darbam ar interneta pārlūkprogrammu Internet Explorer (8. un jaunākām versijām) un Mozilla Firefox (3.6 un jaunākām versijām).
Izmantojot citu interneta pārlūkprogrammu, brīdinām, ka Sistēmas funkcionalitāte var tikt traucēta.
This specification describes the Binary encoding methodology for the Weather information message application of the TPEG "Toolkit".
Detailed weather information for travellers has been a long term desire of many TTI service providers and this application addresses a wider range of weather information messages than that possible by existing TPEG applications (e.g. TPEG-RTM etc,). TPEG-WEA will provide information about detailed weather information such as: pollution index, sun index (UVA, UVB), precipitation (rainfall and snow depth), temperature, wind speed, wind direction, wind chill factor, pressure, flood warnings, sunrise & sunset times, relative humidity, pollen count (non-exhaustive list). As with all TPEG applications, whilst the message content has to be sourced from meteorological providers and road operators this application is end-user focussed and thus is not designed or able to be exactly compatible with standards used in the Content Segment (e.g. DATEX 2). It is designed to specifically satisfy the Delivery Segment requirement which is particularly designed for both human comprehension and automatic clients.
Reģistrācijas numurs (WIID)
27148
Darbības sfēra
This specification describes the Binary encoding methodology for the Weather information message application of the TPEG "Toolkit".
Detailed weather information for travellers has been a long term desire of many TTI service providers and this application addresses a wider range of weather information messages than that possible by existing TPEG applications (e.g. TPEG-RTM etc,). TPEG-WEA will provide information about detailed weather information such as: pollution index, sun index (UVA, UVB), precipitation (rainfall and snow depth), temperature, wind speed, wind direction, wind chill factor, pressure, flood warnings, sunrise & sunset times, relative humidity, pollen count (non-exhaustive list). As with all TPEG applications, whilst the message content has to be sourced from meteorological providers and road operators this application is end-user focussed and thus is not designed or able to be exactly compatible with standards used in the Content Segment (e.g. DATEX 2). It is designed to specifically satisfy the Delivery Segment requirement which is particularly designed for both human comprehension and automatic clients.
