Skip to content
This repository has been archived by the owner on Dec 11, 2023. It is now read-only.

Update SOS descriptions #87

Open
RacingTadpole opened this issue Jan 24, 2017 · 10 comments
Open

Update SOS descriptions #87

RacingTadpole opened this issue Jan 24, 2017 · 10 comments

Comments

@RacingTadpole
Copy link
Contributor

@ChantelleDoan will provide the updated descriptions.

@ChantelleDoan
Copy link
Contributor

I have the description text to add at http://staging.neiiviewer.nicta.com.au/#build/TerriaJS/test/init/bom.json

  1. Add Data - Data Catalogue - Bureau of Meteorology Water Sensors
    a. Rename from 'Bureau of Meteorology Water Sensors' to 'Bureau of Meteorology Water Regulations Data'
    b. Add text:
    Description
    The Bureau receives water data measured at stations around Australia from organisations named in the Water Regulations (2008). This data is stored in the Australian Water Resource Information System (AWRIS). A large proportion of time series data in AWRIS is made available to the public via SOS2 web services. NEII uses these web services to present storage levels, storage volume, water course discharge and water course levels data. Please refer to for more information.

Custodian: Bureau of Meteorology

Further information: http://www.bom.gov.au/waterdata/

@ChantelleDoan
Copy link
Contributor

ChantelleDoan commented Apr 6, 2017

In addition, WDO team requested if the Feature Information fields could be updated as follows:

  1. Summary of changes to Feature Information pop-up fields for Water Storage Levels, Water Storage Volume, Water Course Levels. Refer to attached image.

sos2 feature info
sos2 feature info 2
sos2 feature info 3

@ChantelleDoan
Copy link
Contributor

Hi @RacingTadpole,
3. Here are the updated desciption text for the SOS2 datasets:
Watercourse Level:

Watercourse level as defined under category 1a of the Water Regulations 2008 – refer to Definitions – Subcategories of Water Information. This data is shown as provided to the Bureau of Meteorology by data owner organisations, and is subject to their terms and conditions of use. Please refer to Copyright on the Water Data Online website, and Disclaimer statements relating to the use of Bureau of Meteorology material.

Watercourse Discharge:

Watercourse discharge as defined under category 1b of the Water Regulations 2008 – refer to Definitions – Subcategories of Water Information. This data is shown as provided to the Bureau of Meteorology by data owner organisations, and is subject to their terms and conditions of use. Please refer to Copyright on the Water Data Online website, and Disclaimer statements relating to the use of Bureau of Meteorology material.

Storage Level:

Storage Level as defined under categories 3a and 3e of the Water Regulations 2008 – refer to Definitions – Subcategories of Water Information. This data is shown as provided to the Bureau of Meteorology by data owner organisations and is subject to their terms and conditions of use. Please refer to Copyright on the Water Data Online website, and Disclaimer statements relating to the use of Bureau of Meteorology material.

Please note that storage levels made available on this website may be measured using local rather than Australian Height Datum (AHD). For this reason they may differ to the Storage Level provided on the Bureau of Meteorology's Water Storages website.

Storage Volume:

Storage Volume as defined under category 3b of the Water Regulations 2008 – refer to Definitions – Subcategories of Water Information. This data is shown as provided to the Bureau of Meteorology by data owner organisations and is subject to their terms and conditions of use. Please refer to Copyright on the Water Data Online website, and Disclaimer statements relating to the use of Bureau of Meteorology material.

Please note that storage volumes made available on this website are usually total rather than accessible volume, depending on how they are supplied by the data owner. For this reason they may differ to the Storage Volume provided on the Bureau of Meteorology's Water Storages website and mobile app.

Thanks,
Chantelle

@RacingTadpole
Copy link
Contributor Author

Great - here's what I will push through in the next update:

image
and
image

plus the updated dataset descriptions you've provided.

@ChantelleDoan
Copy link
Contributor

Thanks @RacingTadpole for making the changes. Here are my feedback.

Feature Information pop-up: I have included edits on the below screen shot. Could we also update all dataset to display all these fields? Currently some dataset only shows a subset of field (eg the Watercourse Discharge - Bibikin Road Bridge screenshot above only displays 4 feature information fields (feature type, ID, Latitude and Longitude) instead of the full 9 feature information fields).

image

@RacingTadpole
Copy link
Contributor Author

Sure thing, I've made those updates, except for the "Spatial Reference System" (which isn't available in the code at that point), and similarly, the Watercourse data only has a subset of the data available - that's because the SOS2 standard requires one call per 250 or so features, and there are 1000s of watercourse stations, so I've had to fall back to a lesser representation for them. (In contrast there are <1000 Storage features, so I make just 4 calls to stitch all the time-series data together.)

@ChantelleDoan
Copy link
Contributor

Thanks for the update @RacingTadpole. I don't yet see the changes on http://staging.neiiviewer.nicta.com.au/#build/TerriaJS/test/init/bom.json

When would the changes be rolled out?

@ChantelleDoan ChantelleDoan reopened this Apr 12, 2017
@ChantelleDoan
Copy link
Contributor

Hi @RacingTadpole,
I have included the test feedback to the word document attached. Thanks.
SOS2 test feedback #2.docx

@RacingTadpole
Copy link
Contributor Author

Hi Chantelle, can I just confirm, for next week you only want Water Course Discharge and Water Course Levels to be moved into "NEII Data Services – Conformant" -> Water -> "Bureau of Meteorology Water Regulations Data" ?

@azzerger
Copy link
Contributor

azzerger commented May 8, 2017 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants