Hydro risk curve data

  • 1.4K Views
  • Last post 27 February 2018
littlejj posted this 26 February 2018

I'm keen to download a csv of the hydro risk cruve dataset.

The the link to download the CSV is constructed from a bunch of parameters (see below):

https://www.emi.ea.govt.nz/Environment/Download/DataReport/CSV/3UN1KD?
EffectiveDt=20180220&
RegionCode=NZ&_
si=p|0,
v|4,
_dr_
EffectiveDt|20180220,
_dr_RegionCode|NZ,
_dr_seriesFilter|1%2c2%2c4%2c5%2c6%2c7%2c8%2c9%2c10%2c11
&seriesFilter=1,2,4,5,6,7,8,9,10,11

 

Are there any details on how those parameters work? Can I leave at least some of them blank so that the 'latest' effective date data is presented?

 

Order by: Standard | Newest | Votes
Matthew Keir posted this 27 February 2018

Hi littlejj

The URLs for the web pages and reports are key to providing the functionality on EMI. The content of the URL is subject to change as we continually improve or adapt the website. Given this is the case, we don't support direct interaction with reports through URL with any documentation, and certainly, we don't attempt to advise users of changes affecting URLs or maintain compatibility of these methods through time. Our preference for this type of interaction would be to release data through a documented channel like our other APIs. However, we're a small team with a lot to get done.

All EMI reports have default parameter settings, these are chosen to reflect what we think is the most useful or frequent view of each report. This means whenever a parameter is not specified the default applies.

For the HRC report, the effective date defaults to today, and the end of the date range defaults to 12 months ahead of today. If you are happy with those defaults, you can set the start date that you want and the region code to either NZ or SI.

https://www.emi.ea.govt.nz/Environment/Download/DataReport/CSV/3UN1KD?DateFrom=20100201&RegionCode=NZ&_si=v|4

That should get you what you want, just be aware that using this method will likely result in it breaking from time to time, as changes to the website and associated processes occur.

Cheers,

Matthew

 

  • Liked by
  • littlejj
littlejj posted this 27 February 2018

That is great! Thanks very much.

I'd very much support an API for this report and dataset - please let us know if you want help to support that case!