ONS-Energy-use-fossil-fuels-by-fuel-type-and-industry #137
Conversation
osamede20
added
the
data test case
| @@ -0,0 +1,101 @@ | |||
| { | |||
| "@context": "https://staging.idpd.uk/#ns", | |||
| "@id": "https://staging.idpd.uk/datasets/ons-energy-use-fossil-fuels-by-fuel-type-and-industry/editions", | |||
There was a problem hiding this comment.
ons-dropped from URIs throughout
| "email": "mailto:[email protected]" | ||
| }, | ||
| "topics": [ | ||
| "https://staging.idpd.uk/topics/climatechange", |
There was a problem hiding this comment.
topic renamed to agriculture-energy-and-environment in line with the 9 topics received
| }, | ||
| "topics": [ | ||
| "https://staging.idpd.uk/topics/climatechange", | ||
| "https://staging.idpd.uk/topics/carbonemissions"], |
There was a problem hiding this comment.
Not sure this is a theme on the catalogue? Might be wrong tho. If it is, it would be carbon-emissions but double check.
There was a problem hiding this comment.
topic renamed to agriculture-energy-and-environment in line with the 9 topics received
| "topics": [ | ||
| "https://staging.idpd.uk/topics/climatechange", | ||
| "https://staging.idpd.uk/topics/carbonemissions"], | ||
| "frequency": "irregular", |
There was a problem hiding this comment.
It's not released regularly? Like annually or something?
There was a problem hiding this comment.
oversight; from an existing example.
frequency changed to annual
| "table_schema": { | ||
| "columns": [ | ||
| { | ||
| "name": "Year", |
There was a problem hiding this comment.
I can't see a CSV file with this PR, but would want to make the CSV headers snake_case
There was a problem hiding this comment.
I understand URIs are not required on the output CSV file; I'm still trying to understand how this api-poc works as I have been on leave.
Not sure how it works with this particular dataset - with Standard Industrial Classification (SIC) and a local codelist, but I have left URIs on the Section column of the CSV file.
I can remove the URIs from the output CSV, but would obviously require re-transforming the dataset. I am open to doing this.
Thanks.
There was a problem hiding this comment.
Welcome back :)
Yes please - make the changes as needed. With things like SIC codes it might be best to have two columns - one with the code (e.g. A, B or 01 or whatever) and on with the label (Manufacturing)
There was a problem hiding this comment.
Many thanks.
Great; I will get this done shortly.
There was a problem hiding this comment.
Changes made as directed - 'Section Notation' and 'Industry Section Name'.
Please let me know if I have missed anything. Thanks.
| "columns": [ | ||
| { | ||
| "name": "Year", | ||
| "datatype": "xsd:datetime", |
There was a problem hiding this comment.
datetime not xsd:datetime
In theory they are the same but the xsd: isn't needed here
| }, | ||
| { | ||
| "name": "Value", | ||
| "datatype": "xsd:decimal", |
2 participants
first pass at matching new metadata format