Georgia Power scraper example #2
Open
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 example of what's required to set up a new scraper.
If this repo is cloned,
lgeku_scraper.pycan be replaced with another location-specific scraper, like the one in this PR.instance_idandview_idcome from the site’s HTML: https://outagemap.georgiapower.com/external/default.htmlownerandreponeed to be set to the repo where the outage JSON should be written.The only other thing to do is to add a GitHub token to the cloned repo's Actions so that it can write to the destination repo.
GH_TOKEN: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secretsThe action should have been copied over and should be picked up and execute an Action every 15 minutes, scraping and saving the current outages.