Created an adapter to fetch PM values from Denmark #734
Conversation
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
|
Because this is not a governmental source, we reached out to them to 1) understand what sensors they're using and 2) if they would be comfortable with sharing data on the platform (in the past, the research-grade data we've added has been at the request of the researchers). So putting this on hold until we hear back |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an adapter to fetch the 4 pm stations in denmark, which updates hourly from this site:
https://envs2.au.dk/Luftdata/Presentation/Graph/PM.
The current source EEA, does not provide us any PM values for Denmark, so this should add the data we lack for Denmark.
Only problem with this source is that the timestamp is currently a bit shaky, because it is not given in the sourcecode, or atleast nowhere I could find, but the site displays hourly data, so I had to do a workaround where the timestamp is based around nearest hour, which does seem to correspond correctly to what is displayed on the site.