meteohub.de

This weblink explains the actual formats expected by WOW_UK/MetOffice for various data-inputs through their API, with subsequent transfer of data to WOW_NL/KNMI, etc.

Because the nomenclature is not one-to-one, it triggers a question about Mapping in Meteobridge:
how can in Meteobridge's Mapping a T&H-set for 'grass'-data unambiguously be identified towards WOW_UK?
Not difficult if only 1 station feeding Meteobridge, but of interest if several stations feed and have candidates for the job.

Similar question how to clearly identify in Meteobridge's Mapping towards WOW_UK the Soil-info for -10cm, -30cm and -100cm.
Same question would apply to 'continental' organisations like KNMI and DWD, which prefer Soil-info for -10cm, -20cm, -50cm and -100cm.
In this perspective an interesting aspect:
you could feed WOW_UK with Soil-10, Soil-30 and Soil-100, but what would effectively be transferred by WOW_UK/MetOffice to WOW_NL/KNMI?

Adaptation Feb13, 2024:
Identification of organisations extended.

Thanks for bringing this up. I checked with current implementation and WOW added some new sensor type, which are now supported. Meteobridge reports now data fro temp and humidity for "soil0" sensor. If you have multiple soil sensors, the one mapped to "soil0" is used.

List of sensors supported by WOW is still very basic:

• baromin - Barometric Pressure
• dailyrainin - Accumulated rainfall so far today
• dewptf - Outdoor Dewpoint
• humidity - Outdoor Humidity
• rainin - Accumulated rainfall since the previous observation
• soilmoisture - % Moisture
• soiltempf - Soil Temperature (10cm)
• tempf - Outdoor Temperature
• visibility - Visibility (not supported by Meteobridge)
• winddir - Instantaneous Wind Direction
• windspeedmph - Instantaneous Wind Speed
• windgustdir - Current Wind Gust Direction (using software specific time period)
• windgustmph - Current Wind Gust (using software specific time period)