This CanadaMeteo data import is used for targeted access Environment and Climate Change Canada in the form of Observation Summary Data Observations Data summary data in XML format.
...
The parser is included in Delft-FEWS versions 2017.02 and higher.
Since 2024.02, data quality can also be imported if present. 100 is seen as reliable and 10 as doubtful.
This documentation contains:
...
Please comment if anything further is needed or requires updating.
1) Data Provider Documentation
This service is hosted by the Meteorological Service of Canada:
...
The license of the data provider (Environment and Climate Change Canada) can be found here https://dd.weather.gc.ca/doc/LICENCE_GENERAL.txt
2) Sample Configuration
Example of the Delft-FEWS import module
| Code Block | ||||
|---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2006 rel. 3 sp1 (http://www.altova.com) by Computer Services (WL | Delft Hydraulics) -->
<timeSeriesImportRun xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/timeSeriesImportRun.xsd">
<import>
<general>
<importType>CanadaMeteo</importType>
<serverUrl>http://dd.meteo.gc.ca/observations/xml</serverUrl>
<user>dummy_username</user>
<password>dummy_password</password>
<!-- Time period has to be configured for the importer to work -->
<relativeViewPeriod unit="hour" start="-5" end="0" startOverrulable="true" endOverrulable="true"/>
</general>
<properties>
<!--Optional configuration field. Value is a comma separated string of the region folder to be included.-->
<!--If it is not configured, data will be fetched from all folders for the specified time. Case sensitive.-->
<!--Possible choices: AB, BC, MB, NB, NL, NS, NT, NU, ON, PE, QC, SK, YT-->
<string key="RegionDirectory" value="AB, BC"/>
<!--Optional configuration field. Value is a comma separated string of the time folders to be included.-->
<!--If it is not configured, data will be fetched from all folders for the specified time.-->
<!--Possible choices: "hourly", "today", "yesterday"-->
<string key="TimeDirectory" value="hourly, today"/>
</properties>
<timeSeriesSet>
<moduleInstanceId>CanadaMeteo</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>mean_sea_level</parameterId>
<locationId>3025481</locationId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="nonequidistant"/>
<readWriteMode>add originals</readWriteMode>
</timeSeriesSet>
</import>
</timeSeriesImportRun> |
...
- The first set of data (member) contains information that is not specific to one location, it is not imported.
- Data concerning record temperatures, record rain, record snow, since when temperature and precipitation data is available, present weather and tendency characteristic are ignored. (Thus fields that do not contain data measured at sampling time).
- Measurements with no "value" are ignored.
- Wind direction is calculated from code (for example, NW for NorthWest) to degrees. For location ID climate station number is used.
- If, in the import module, a RegionDirectory is configured (for the purpose of importing data for, say, a single Province only), special attention should be paid to make sure that the locationSet that data is imported to, includes locations that are available in the directory specified.
- If data is not available for the chosen times, en empty time series set is returned.
- It is practical to configure either a short time period, or other restrictions to prevent running out of local memory.
Locations and id mapping
Two files used for Locations and IdMapping are linked here.
...