-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #252 from IEA-Task-43/dev
Release version 1.3.0-2024.03
- Loading branch information
Showing
12 changed files
with
376 additions
and
50 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,84 @@ | ||
{ | ||
"author": "Stephen Holleran", | ||
"organisation": "BrightWind", | ||
"date": "2023-11-24", | ||
"version": "1.3.0-2024.03", | ||
"measurement_location": [{ | ||
"uuid": "282c5c44-17a2-426a-b10d-0826d0d868fc", | ||
"name": "ERA5_53.536N_-6.3E", | ||
"latitude_ddeg": 53.536, | ||
"longitude_ddeg": -6.3, | ||
"measurement_station_type_id": "reanalysis", | ||
"notes": "This is an ERA5 reanalysis dataset produced by ECMWF.", | ||
"update_at": "2023-11-24T18:13:00", | ||
"model_config": [{ | ||
"reanalysis": "ERA5", | ||
"horizontal_grid_resolution_m": 11000, | ||
"model_used": "ECMWF IFS", | ||
"offset_from_utc_hrs": 0, | ||
"averaging_period_minutes": 60, | ||
"timestamp_is_end_of_period": false, | ||
"date_from": "2000-01-01T00:00:00", | ||
"date_to": null, | ||
"notes": "This is an ERA5 reanalysis dataset produced by ECMWF.", | ||
"update_at": "2023-11-24T18:13:00" | ||
}], | ||
"measurement_point": [{ | ||
"name": "WS100m", | ||
"measurement_type_id": "wind_speed", | ||
"height_m": 100, | ||
"height_reference_id": "ground_level", | ||
"logger_measurement_config": [{ | ||
"measurement_units_id": "m/s", | ||
"date_from": "2000-01-01T00:00:00", | ||
"date_to": null, | ||
"column_name": [{ | ||
"column_name": "Spd_100m_mps", | ||
"statistic_type_id": "avg" | ||
}] | ||
}] | ||
},{ | ||
"name": "WD100m", | ||
"measurement_type_id": "wind_direction", | ||
"height_m": 100, | ||
"logger_measurement_config": [{ | ||
"measurement_units_id": "deg", | ||
"date_from": "2000-01-01T00:00:00", | ||
"date_to": null, | ||
"column_name": [ | ||
{ | ||
"column_name": "Dir_100m_deg", | ||
"statistic_type_id": "avg" | ||
}] | ||
}] | ||
},{ | ||
"name": "Tmp2m", | ||
"measurement_type_id": "air_temperature", | ||
"height_m": 2, | ||
"logger_measurement_config": [{ | ||
"measurement_units_id": "deg_C", | ||
"date_from": "2000-01-01T00:00:00", | ||
"date_to": null, | ||
"column_name": [ | ||
{ | ||
"column_name": "Tmp_2m_degC", | ||
"statistic_type_id": "avg" | ||
}] | ||
}] | ||
},{ | ||
"name": "Prs0m", | ||
"measurement_type_id": "air_pressure", | ||
"height_m": 0, | ||
"logger_measurement_config": [{ | ||
"measurement_units_id": "hPa", | ||
"date_from": "2000-01-01T00:00:00", | ||
"date_to": null, | ||
"column_name": [ | ||
{ | ||
"column_name": "Prs_0m_hPa", | ||
"statistic_type_id": "avg" | ||
}] | ||
}] | ||
}] | ||
}] | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -12,4 +12,6 @@ | |
| `"lidar"` | | | ||
| `"sodar"` | | | ||
| `"floating_lidar"` | | | ||
| `"wave_buoy"` | | | ||
| `"adcp"` | | | ||
| `"solar"` | | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
# Release Procedure | ||
|
||
**This is a procedure for how to create a release of the WRA Data Model.** | ||
|
||
The release is from the master branch. Ideally all merges over the course of maintenance or development were merged into | ||
the `dev` branch. Therefore, the `dev` branch will be cleaned up first. | ||
|
||
1. In the `dev` branch update the version number in: | ||
1. the actual JSON Schema file itself, | ||
2. all the relevant demo implementation files in the demo_data folder, | ||
3. the CHANGELOG file and | ||
4. the description of the SQL create table file. | ||
2. Do a pull request to merge the `dev` branch into `master`. | ||
3. The documentation is automatically generated when there is a merge into `master`. Make sure that this has completed successfully. | ||
4. Go to 'Releases' on GitHub and 'Draft a new release'. | ||
5. For the 'Choose a tag' create a new tag by typing in the name e.g. "v1.2.0-2023.01". Ensure you copy the format exactly | ||
including the "v" as this will be included in the URL to find the assets that may be hardcoded in software. | ||
1. The target for the tag should be the `master` branch. However, a recent commit can be selected. Selecting a recent | ||
commit would be more informative as the last commit is usually the 'Compile Documentation' commit which is not | ||
informative. In this instance the commit for "update version number to 1.2.0-2023.01" is selected. | ||
6. For the 'Release title' type in the same as the name for the tag but without the "v". E.g. "1.2.0-2023.01". The real | ||
reason for this only to be consistent with previous releases. | ||
7. In the 'Describe this release' box, copy and paste the contents from the CHANGELOG file that are relevant to this release. | ||
8. Attach the JSON Schema file as an asset so this can be retrieved via code. Ensure that you are copying the most | ||
up-to-date schema file which has the correct version number. | ||
9. Publish release. |
Oops, something went wrong.