WPLA Dev 3.0 \\ Reconstruction of the original version 2.x models for version 3.0

[rflinnenbank]

The following features are included:

• The new models should support v2.x identical output via the harmonizing utilities.
• The new models should be based on the optimal source for the data they entail. (if for instance the data is available on both the KNMI Data Platform as well as the site itself, the KDP should be used. If the data is available in multiple formats, the format should be used that is the least likely to cause problems translating into harmonized NetCDF4) For the known formats (excluding GRIB) this order is, from preferred to not preferred: NetCDF4, NetCDF3, json, csv, txt Formats not mentioned should be judged based on the likely amount of effort required to format them to the harmonized NetCDF4 file format. Note: GRIB is not rated as it is not a file format as much as it is a content format. A GRIB file's contents could be harder to parse than trying to translate data from multiple website pages, or almost as easy as loading a NetCDF4 file directly. A secondary reason is that parsing GRIB files requires pygrib or cfgrib. Both have issues operating properly within a Windows environment system.
• All of the code has both proper sphinx-proof documentation and full unit test coverage.