tidal/tsunami data collection using mtsat-dcs

36
Tidal/Tsunami Data Collection using MTSAT-DCS Japan Meteorological Agency Doc 5.1(3) Appendix B Implementation – Coordination Meeting on the GTS and ISS in RA V (Hawaii, 2-5 December 2009) Please consider our Earth environment before printing

Upload: gayle

Post on 31-Jan-2016

57 views

Category:

Documents


0 download

DESCRIPTION

Tidal/Tsunami Data Collection using MTSAT-DCS. Doc 5.1(3) Appendix B Implementation – Coordination Meeting on the GTS and ISS in RA V (Hawaii, 2-5 December 2009). Japan Meteorological Agency. Please consider our Earth environment before printing. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Tidal/Tsunami Data Collection  using MTSAT-DCS

Tidal/Tsunami Data Collection using MTSAT-DCS

Japan Meteorological Agency

Doc 5.1(3) Appendix B

Implementation – Coordination Meeting on the GTS and ISS in RA V(Hawaii, 2-5 December 2009)

Please consider our Earth environment before printing

Page 2: Tidal/Tsunami Data Collection  using MTSAT-DCS

Data Collection System (DCS) is one of the main functions of MTSAT-1R that collects and distributes in-situ observational data obtained with automatic surface stations (Data Collection Platforms; DCPs), such as an automatic weather station at a remote site, or a tide (tsunami) gauge, or an instrumented ship/island.

  Almost 100 thousand data are being collected a month. MTSAT-DCS has sufficient capacity to collect more

tsunami data so far.

Fulfills two functions: a meteorological function by the JMA and an aviation control function by the Japanese

civil aviation authority Succeeds GMS-5, covering East Asia and the

Western Pacific (as the sixth geostationary meteorological satellite of Japan)

Introduction of MTSAT-1RThe Multi-functional Transport Satellite

Operational since 28 June

2005

Page 3: Tidal/Tsunami Data Collection  using MTSAT-DCS

Preliminary Information of the Follow-on MTSAT series satellites Named Himawari-8/-9

JMA has made a contract for the manufacture of the follow-on meteorological satellites named Himawari-8/-9.

The Agency plans to launch Himawari-8 in 2014 and begin its operation in 2015. To ensure the robustness of the satellite system, the launch of a second follow-on satellite (Himawari-9) for in-orbit standby is also scheduled in 2016.

Himawari-8/-9 will be continued to operate around 140 degrees east covering the East Asia and the Western Pacific as with the MTSAT series.

General objectives ; - Dedicated satellite for meteorological function

- Observation mission: Advanced Himawari Imager - Data Collection System Mission JMA will continue the Data Collection System service with Himawari-8/-9, maintaining fundamentally the same specifications as those of the MTSAT series.

Artist’s image of Himawari-8 and -9

Page 4: Tidal/Tsunami Data Collection  using MTSAT-DCS

Communication range of MTSAT-DCS

Note: The communication range of Hiamwari-8/-9 is same as MTSAT-DCS.

Page 5: Tidal/Tsunami Data Collection  using MTSAT-DCS

MTSAT-1R

MSC

CDAS*

(1.6GHz band)Acoustic gauge

Pressure sensor

Acousticgauge

Pressure sensor

Tidal Observatory

Transmission of Data

Transmission interval: 12 min, 15 min or 1 hour

Transmission length should not exceed 1 min National

Meteorological & Hydrological Services (NMHSs)

National Meteorological & Hydrological Services (NMHSs)

PTWCPTWC

Report of tidal data (402MHz band)

Tidal/tsunami data collectionvia MTSAT-DCS

* Command and Data Acquisition Station of MSC

InternetOrganizations without GTS connection

Organizations without GTS connection

GTSJMA HQ

Tidal Observatory

Page 6: Tidal/Tsunami Data Collection  using MTSAT-DCS

Current status of tidal/tsunami data collectionvia MTSAT-DCS

Cocos Is. 12.50S, 96.83E

Jackson Bay 43.97S, 163.62E

Pohnpei 6.98N, 158.20’E

Minami Torishima Is. 24.28N, 153.97E

Ust-Kamchatsk 56.23N, 162.47ESevero-Kurisk

50.67N, 156.12E

Legaspi 13.15N, 123.75E

Malakal 7.33N, 134.47E

Manila 14.60N,120.95E

Davao 7.10N,125.65E

Colombo 6.97N, 79.85E

Saipan 15.18N, 145.75E

Yap 9.52N, 138.13E

Lombrum 2.04S, 147.38E

Majuro 7.12N, 171.37’E

Betio 1.36S,172.93E

Apia 13.82S, 171.75W Rarotonga 21.20S, 159.79W

Lautoka 17.60S, 177.44E

Port Vila 17.76S, 168.29E

Nauru 0.53S, 166.91E

Honiara 9.43S, 159.95E

Funafuti 8.50S, 179.21E

Nuku’Alofa 21.14S, 175.18W

Kings Wharf 18.13S, 178.43E

:JMA

:PTWC

:IOTWS

:Australia

Click a station, its status shows up.

SAUMLAKI(NEW) 8.01S, 131.18E

AMBON(NEW) 3.41S, 128.11E

Page 7: Tidal/Tsunami Data Collection  using MTSAT-DCS

Remarks

There are some constraints to MTSAT-DCS: Limited number of channels ---> JMA will coordinate with relevant

countries and organizations, taking into account of the

number of available channels and the latest needs of countries, for optimal solution

Reliability is not necessarily 100% ---> Considering the above nature of MTSAT-

DCS, it is better to collect tsunami data

jointly with other methods; i.e. simultaneous

data collection through landline and via MTSAT-DCS is recommended

Page 8: Tidal/Tsunami Data Collection  using MTSAT-DCS

Detailed information on DCS including application procedures is available at the following web site:

http://www.jma.go.jp/jma/jma-eng/satellite/index.html

For inquiries, contact Hiroshi TOMITA Senior Scientific Officer, Satellite Program Division Japan Meteorological Agency

E-mail: [email protected] Telephone: +81-3-3201-8677 Facsimile: +81-3-3217-1036

For more information

Page 9: Tidal/Tsunami Data Collection  using MTSAT-DCS

Thank you for your attention

Thank you

Page 10: Tidal/Tsunami Data Collection  using MTSAT-DCS

Betio station (BoM NTF, transmission interval: 60 minutes)

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 11: Tidal/Tsunami Data Collection  using MTSAT-DCS

Apia station (BoM NTF, transmission interval: 60 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 12: Tidal/Tsunami Data Collection  using MTSAT-DCS

Majuro station (BoM NTF, transmission interval: 60 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 13: Tidal/Tsunami Data Collection  using MTSAT-DCS

Rarotonga station (BoM NTF, transmission interval: 60 minutes)  Number of messages correctly received (Jan – Oct 2009)

Number of Error messages (Jan – Oct 2009)

Page 14: Tidal/Tsunami Data Collection  using MTSAT-DCS

Lautoka station (BoM NTF, transmission interval: 60 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 15: Tidal/Tsunami Data Collection  using MTSAT-DCS

Port Vila station (BoM NTF, transmission interval: 60 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 16: Tidal/Tsunami Data Collection  using MTSAT-DCS

Nauru station (BoM NTF, transmission interval: 60 minutes)  

Number of messages correctly received (Jan – Oct 2009)

Number of Error messages (Jan – Oct 2009)

Page 17: Tidal/Tsunami Data Collection  using MTSAT-DCS

Honiara station (BoM NTF, transmission interval: 60 minutes)  

Number of messages correctly received (Jan – Oct 2009)

Number of Error messages (Jan – Oct 2009)

Page 18: Tidal/Tsunami Data Collection  using MTSAT-DCS

Funafuti station (BoM NTF, transmission interval: 60 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 19: Tidal/Tsunami Data Collection  using MTSAT-DCS

Nuku’Alofa station (BoM NTF, transmission interval: 60 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Nov 2007)

Page 20: Tidal/Tsunami Data Collection  using MTSAT-DCS

Cocos Island station (BoM NTF, transmission interval: 60 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 21: Tidal/Tsunami Data Collection  using MTSAT-DCS

Lombrum station (BoM NTF, transmission interval: 60 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 22: Tidal/Tsunami Data Collection  using MTSAT-DCS

Jackson Bay station (BoM NTF, transmission interval: 60 minutes)  

Number of messages correctly received (Jan – Oct 2009)

Number of Error messages (Jan – Oct 2009)

Page 23: Tidal/Tsunami Data Collection  using MTSAT-DCS

Kings Wharf station (BoM NTF, transmission interval: 60 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 24: Tidal/Tsunami Data Collection  using MTSAT-DCS

Pohnpei station (BoM NTF, transmission interval: 60 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 25: Tidal/Tsunami Data Collection  using MTSAT-DCS

Malakal Island station (NOAA ITSU, transmission interval: 12

minutes)  Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 26: Tidal/Tsunami Data Collection  using MTSAT-DCS

Yap Island station (NOAA ITSU, transmission interval: 12 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 27: Tidal/Tsunami Data Collection  using MTSAT-DCS

Legaspi station (NOAA ITSU, transmission interval: 12 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 28: Tidal/Tsunami Data Collection  using MTSAT-DCS

Ust-Kamchatsk station (NOAA ITSU, transmission interval: 12

minutes)  Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 29: Tidal/Tsunami Data Collection  using MTSAT-DCS

Severo-Kurilsk station (NOAA ITSU, transmission interval: 12

minutes)  Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 30: Tidal/Tsunami Data Collection  using MTSAT-DCS

Colombo station (NOAA ITSU, transmission interval: 15 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 31: Tidal/Tsunami Data Collection  using MTSAT-DCS

Manila station (NOAA ITSU, transmission interval: 15 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 32: Tidal/Tsunami Data Collection  using MTSAT-DCS

Davao station (NOAA ITSU, transmission interval: 15 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct

2009)

Page 33: Tidal/Tsunami Data Collection  using MTSAT-DCS

Saipan station (NOAA ITSU, transmission interval: 15 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Page 34: Tidal/Tsunami Data Collection  using MTSAT-DCS

Saumlaki station (NOAA ITSU, transmission interval: 15 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Note) Saumlaki DCP started its operation on MTSAT-DCS on 1 October 2008.

Page 35: Tidal/Tsunami Data Collection  using MTSAT-DCS

Ambon station (NOAA ITSU, transmission interval: 15 minutes)  

Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)

Note) Ambon DCP started its operation on MTSAT-DCS on 1 October 2008.

Page 36: Tidal/Tsunami Data Collection  using MTSAT-DCS

Minami Torishima station (JMA Tide DCP, transmission interval: 10

minutes)Number of messages correctly received (Jan – Oct

2009)

Number of Error messages (Jan – Oct 2009)