Nik Cubrilovic

https://aws.amazon.com/about-aws/whats-new/2022/08/amazon-cloudfront-supports-http-3-quic/ updated to support http3/quic on all CF distributions

#79 is related

@simonhac can you just clarify these - as committed at the moment MUJA AB - https://github.com/opennem/opennem/blob/master/opennem/data/stations.json#L27979 MUJA CD - https://github.com/opennem/opennem/blob/master/opennem/data/stations.json#L28100 Kwinana Newgen - https://github.com/opennem/opennem/blob/master/opennem/data/stations.json#L28423 Kwinana Swift - https://github.com/opennem/opennem/blob/master/opennem/data/stations.json#L28579 Kwinana Cogen...

@aleith does this split of Kwinana and MUJA units look right? edit: hold on that for a moment - I have a better way of asking this we're looking at...

https://data.wa.aemo.com.au/public/public-data/datafiles/facilities/facilities.csv

thanks @aleith i'll check the spreadsheet now - we just need a logical way of representing these stations

> maybe it would be worth having a hash table of urls that are source links for info in the database. that way any info like capacity, emissions rating*, retirement...

`emission_factor_source` as a simple string field? will be in db and `stations.json` and API outputs https://github.com/opennem/opennem/blob/master/opennem/db/models/opennem.py#L615

`emission_factor_sources` table? `code` `source_name` `source_link` `created_at` etc. and then each fac `emission_factor_source` links to a record `code`

https://data.dev.opennem.org.au/v3/stats/au/NEM/VIC1/energy/2022.json