210 likes | 227 Views
Learn about MetBroker for accessing FieldServer data, available tools, weather databases, data retrieval methods, and data formats. Use Java, VB, Delphi, or SOAP to access data efficiently. Combine with other weather data sources to improve analysis.
E N D
Using MetBroker software with FieldServer Matthew Laurenson
Contents • What is MetBroker • Why use MetBroker to access FieldServer data • What MetBroker tools are available • How does MetBroker access FieldServer data • Which FieldServer data are available through MetBroker
The Problem: Lack of standard data formats limits DSS portability Database A Database B DSS A DSS B
The Goal: Users in any country can run any DSS Database A Database B
What is MetBroker? Consistent data access “Driver” for each database Weather Databases (Heterogeneous) Applications Relational MetBroker File-based Web-pages/CGI
Existing MetBroker tools: • Retrieve and graph data from one station • Display data from all stations in an area • Calculate the risk of extreme climatic events based on historical data • Display risk of climatic events on a regional basis • Get data directly into Excel spreadsheet
Retrieve data from any station Retrieves data from any of 12,000 MetBroker-linked stations Station’s period of operation Weather elements and resolutions available from station
View daily maximum and minimum temperatures and rainfall across a region
Examine risks of climatic extremes Risk of daily max temp in Bangkok > 34°C, 35°C, 36°C ...
Month: March Interested in frosts colder than -3°C Probability of one or more frosts in month based on 25 years data Area around Tsukuba, Japan Weather station locations
FieldServer data available through MetBroker <OneDayData> … <Data> <Date>2003/3/8</Date> <Time>2:42</Time> <O-Temp.>0 C</O-Temp.> <Humid.>62</Humid.> <PPFD-r>32 C</PPFD-r> ... </Data> ... </OneDayData> FieldServer XML data structure
In comparison to “regular” weather station data... • FieldServers can be easily shifted so location associated with data changes • Data has irregular time intervals • Some new kinds of data (eg images) MetBroker not fully able to handle these differences (but is changing toward supporting)
MMS Dataase? Current Data Handling Architecture FieldServer–specific applications FieldServer–specific applications XML files RelationalDatabase Rawdata (HTTP) (JDBC) DatabaseLoader FS AgentSystem MetBroker
Why Both Relational DB and Archive? • XML is flexible so can accommodate wide range of data structures, but slow to access randomly • Relational databases offer fast random access and standard access (ODBC, JDBC)
Options for developing new MetBroker tools • Java developers: • Applets and Swing applications can use JavaBean components • Servlets for easy access from browsers • Access via Java RMI • Other languages (eg Microsoft .Net, PHP, PERL, Delphi…) • Access using SOAP through MetSOAP
JavaBean components for rapid applet and Java Swing application development
MetSOAP Visual Basic client application VB function calls MS SOAP Toolkit Application code VB objects SOAP over HTTP MetBroker MetSOAP RMI Delphi client application Delphi function calls SOAP over HTTP Applicationcode Borland SOAP Toolkit Delphi objects
Why use MetBroker to access FieldServer data? • Can immediately view and analyze your data with existing MetBroker applications and use services such as interpolation • Combine FieldServer data with other weather data (eg from national meteorological service, or research network) • Utilize new MetBroker applications as soon as they are developed • Develop new software applications to share with or sell to other countries
Other brokers and servers • ChizuBroker – online maps • DEMBroker – digital elevation models • ResourceServer – localization system for screen text • CountryServer – national boundaries and regional boundaries
For more information on brokers see www.agmodel.netThank you