Add Safeguard Mechanism facilities to oil & gas sector #152
Closed
aethr wants to merge 24 commits into
Closed
Conversation
6c6b7d5 to
654e305
Compare
0bd08b9 to
3d45c3c
Compare
654e305 to
6e5fc5c
Compare
6e5fc5c to
efb7a24
Compare
947d45e to
cff455e
Compare
48fdcfa to
557d4c6
Compare
557d4c6 to
7f194b0
Compare
This reads the asset file using geopandas, and returns a GeoDataFrame, which is a pandas DataFrame that supports vector geometry fields.
This DataSource fetches oil and gas field shapes from the Victorian Open Data geoserver and saves them as GeoJSON. The data is then parsed as a GeoDataFrame using geopandas.
…hapes The allocate_safeguard_facility_emissions method in the oil_gas sector module is similar to the implementation in the coal module, except it works on a data source which provides geometry shapes for locations instead of lat/lon points. In this naive implementation the emissions from a single facility are spread out equally over the area covered by its locations. Two grid cells fully covered by a facility location would be attributed equal emissions, while grid cells with only partial coverage would get a smaller share of the facility's reported total.
The test is meant to ensure there aren't any empty rows, and the shape of a single row, which it now does.
Currently, only facilities in Victoria are included, as this is the only location dataset that's been introduced.
For the output, we only need to allocate SGM facilities to the domain grid. However, we also need to remove SGM facilities from supplementary data sources so that these facilities aren't double-counted. The simplest way to do that is to remove any facilities which fall within a grid cell that already has emissions from the SGM, but we must do this across the entire inventory domain even when the domain of interest is a subdomain.
The oil and gas sector implementation is likely to use a number of data sources, this will help keep them a bit better organised than all existing in a single file.
7f194b0 to
0a541ce
Compare
When multiple GeoDataFrame objects are used in a layer and often combined, they must share a common CRS. The CRS of the domain projection may not be known at the time that parse_geo is run, so for now just normalise to a standard WGS84 projection.
9e29a86 to
c488842
Compare
This sector implementation is complex enough to warrant its own documentation where we can explain methodology, data sources, and decisions.
Since emission sources for this sector will come from many different datasets, this defines a common structure of data as an interchange format.
NOPTA is the National Offshore Petroleum Title Administrator who manages Australian offshore resource titles. Using their titles and wells datasets we can identify likely offshore locations where oil and gas are being extracted within a prior period.
Combine NSW drillholes dataset with petroleum leases dataset to extract producing wells with an activity period matching the period of interest.
Combine WA petroleum wells dataset with petroleum titles dataset to extract producing wells with an activity period matching the title period.
Combine QLD boreholes dataset with petroleum leases dataset to extract producing wells with an activity period matching the lease period.
The NOPTA dataset has significant overlap with WA and VIC datasets, with many wells occurring in both. In the case of VIC fields dataset, the NOPTA dataset has more detail and includes all the same sources, so the simplest solution is not to use the VIC data. In the case of WA, the WA dataset does include some wells that are not found in NOPTA, so we want to combine both datasets but remove any duplicates. The two datasets store coords with slightly different precision, so we allow for a small amount of distance between "duplicate" points.
c488842 to
64dcf18
Compare
3 tasks
3 tasks
Contributor
Author
|
Superseded by #170 . |
This file contains hidden or 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
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.
Description
Similar to #144, this adds a proof of concept for allocating Safeguard Mechanism facility emissions for facilities in the "Oil and gas extraction (070)" sector to the
oil_gasprior sector.This is more complicated than the coal implementation due to a number of factors:
Currently, this implements a single new data source which gives the shapes of oil and gas fields in Victoria, Australia, and allocates the SGM facility emissions to them continuously across the entire area.
Allocation of facility emissions
Even if it was clear exactly which fields and facilities were counted under a single Safeguard facility, the single annual emission figure must be allocated among them, which is a complex problem. How much do fields emit vs facilities? How much is lost in transport? Do pipelines leak at the start and end, or across their length? Answers to these questions may differ from facility to facility.
Checklist
Please confirm that this pull request has done the following:
changelog/Notes