Skywarn - Serviceplan
The Dutch Skywarn section is set up to be an open and transparant organisation; "everyone" can participate and receive data and trainingmaterials:
- Partnersites: Selected websites Skywarn-spotters can logon to with their Skywarn-credentials and post reports.
- Premium clients:
meteo-organisations and -parties with direct access to the Skywarn
reports. This wil only be offered to professional organisations that
will be contacted by Skywarn as described in our
Please note that Skywarn NL actively monitors the quality of submitted extreme weather reports.
- All other: data-exports can be requested (CSV files, for available data see below) and observations may be displayed on any website (RSS-feed available).
For more information please contact the persons mentioned on the home-page.
Access to the servicedatabase
Partnersites and registered premium clients receive login-data for direct access to the (MySQL) servicedatabase in order to post and/or receive recent observations.
Available data (via MySQL view)
|swextobs_oid*||char(20)||Unique id of the observation. This id can be used to contact the observer (via Skywarn Nederland).|
|swextobs_scl||char(1)||Class of the observer:
1 = Entry-level, 2 = Certified, 3 = Professional/expert.
|swextobs_dat*||datetime||Date and time of the observation in local NL time (GMT+1) with summer-/wintertime applied. Format yyyy-mm-dd hh:mm:ss.|
|swextobs_utc*||datetime||UTC date and time of the obervation, format yyyy-mm-dd hh:mm:ss|
|swextobs_prc||char(2)||Precision of the given time of observation:
05 = +/- 5 minutes (default);
15 = +/- 15 minutes;
30 = +/- 30 minutes.
|swextobs_phnid*||tinyint(4) unsigned||Id of the reported extreme weather phenomenon, please see "encoding and selection of phenomena, countries and languages" for more info.|
|swextobs_phndsc*||char(45)||Description of the reported extreme weather phenomenon.|
|swextobs_ovr||char(1)||Only if funnelcloud or tornado's are reported,
n = n/a (default), o = unknown, l = land, w = water (waterspout).
|swextobs_dir||char(6)||In which direction the event was seen, for
'n/a' =not applicable or on location (default);
SSW =southsouthwest, etc.
|swextobs_dst||char(7)||Distance to the observed event, only if
applicable and known:
'n/a' =not applicable or on the spot, default;
1-5km = less than 5km;
5-10km = 5 to 10km, etc.
|swextobs_dsc||varchar(384)||Further description of the event, e.g. indication of strength or any other relevant details. Input is not required.|
|swextobs_lat*||char(12)||Lattitude position observer, decimal point, max. 8 decimals.|
|swextobs_lon*||char(13)||Longitude position observer, decimal point, max. 8 decimals.|
|swextobs_loc1*||char(50)||Name of the town or place as given in Google geolocation "locality".|
|swextobs_loc2*||char(4)||Name of the region or district as given in Google geolocation "administrative_area_level_1"
4 positions. For example:
Vlaams Gewest - Vlaa
|swextobs_loc3*||char(3)||Country-id as given in Google geolocation "country",
NL = Nederland, DE = Deutschland, etc.
|swextobs_stsid||tinyint(2) unsigned||Id of the reportstatus, default 1 = "as received".|
|swextobs_org||char(4)||Id of the (partner-)site that received the report, default SWNL = Skywarn Nederland.|
|swextobs_evt||datetime||Date on which damage occurred, only relevant in case of damage reports. The date on which the damage was observed may differ from the date the damage was caused. Format yyyy-mm-dd.|
|swextobs_edt||datetime||Date and time the report was last edited, format yyyy-mm-dd hh:mm:ss in lokale tijd (GMT+1) and summer-/wintertime applied.|
|* = these data can not be changed once a report is submitted.|
Extreme weather report properties are encoded in de Skywarn databases as shown below. Per organisation is tagged which data are relevant (SWNL = Skywarn Nederland).
Premium clients: log on to this page with the account you received for database-access to see your current selection.
|10||Dense fog (sight < 100mtrs)||√|
|2||Funnel / Tuba (>10% distance cloud-surface)||√|
|5||Large hail (stones and/or deck at least 20mm)||√|
|17||Heat I - Temperature >= 35°C||√|
|18||Heat II - Heat Index >= 35°C||√|
|1||Spout / Tornado (touchdown observed)||√|
|12||Glaze(d frost) or sleet||√|
|9||Thunderstorm, heavy (at least 60 strikes/min.)||√|
|16||Snow, light - moderate|
|11||Snow, heavy (sight <200mtr)||√|
|19||Windchill - perceived temperature < -20°C||√|
|4||Heavy wind (at least 90 km/u)||√|
Which phenomena are selected will be determined in consultation with the client organisation. Should it be necessary to change the selection contact the persons mentioned on the home-page.
Premium clients and partnersites will receive a databaseaccount for direct access to the submitted reports. To ensure proper performance for all participating parties the allowed number of queries is limited, typically 60 per hour (so reports can be read and/or transfered each minute). To ensure ease of transfer and usefulness recent reports will be offered partly denormalized in a custom-made view per client. Best practice: we advise to save the records at once in a (temporary?) table in your own database environment for further processing or use. To create such table, e.g. "tblSWTemp", a databasescript is available, see the downloads below.
Depending on which further use is foreseen records could be used directly from the aformentioned table or, should archiving be desired, be converted to your own database-format. You can use fields swextobs_oid and swextobs_edt to determine which records are new and which records to update in case reports are changed.
If you want to archive reports in the Skywarn database definition you
can use the scripts in swtables.zip to create and populate the subtables.
This is advisable because is enables you to (re-)normalize the data. Or
download only the data as .CSV files as given in swsvcdata.zip.
In this scenario you can choose to simply overwrite existing records or update records in case corresponding reports have been changed.
(MySQL) Statement to create the aforementioned table tblSWTemp. If MySQL is being used make sure you have a recent version like 5.x.
Statements to create the additional tables containing phenomena, reportstatus and directions. For use with MySQL, but can be used for other DBMS's with minor modifications.
Data only in .CSV format.
* From 02:00z to 04:00z backups en database maintenance jobs are running with possible impact on response times. Note: in very rare cases (if one of the "constant" values would need to be changed) your database-query may not return any, or not all, records during maintenance.