Pipelines

MarineCadastre.gov Data Registry

URL where the source data were originally accessed.

Polyline shapefiles of pipeline data.

Polyline shapefiles of California pipeline data.

State and Federal waters within the Economic Exclusion Zone of the United States feature class used to clip source datasets.

Polyline shapefile of Louisiana pipeline data.

URL where the source data were originally accessed.

Polyline shapefile of pipeline data.

URL where the source data were originally accessed.

Polyline shapefile of Mississippi pipeline data.

Polyline shapefile of Alaska pipeline data.

URL where the source data were originally accessed.

Polyline shapefiles of pipeline data.

URL where the source data were originally accessed.

Polyline shapefile of Alabama pipeline data.

URL where the source data were originally accessed.

Polyline shapefiles of pipeline data.

URL where the source data were originally accessed.

Vector digital data of USA States, Territories, Outlying and Associated Areas used to clip the Pipelines Feature class.

Project all source layers into WGS_1984_World_Mercator & erase any pipelines that fall on land using the USAStateTerritoriesAssociatedAreas feature class with the FederalAndStateWaters layer removed from it to assure pipelines falling in State Waters were captured. Each layer was named with "_project" after it was properly projected and the layers that had to have space erased had "_erase" after this step was completed.

Cleaned up attributes to read more clearly. Set attribute alias.

Create the Length attribute and utilize the calculate geometry function and calculate the length in meters. Select the Alaska data, export & project into Alaska Albers Equal Area & calculate the length in meters within this projection. Take the Alaska Equal Area length calculations for each attribute and replace them in the proper place in the Pipeline feature class. The calculations for the Alaska data will be from Albers Equal Area, but the layer and data are still projected into World_Mercator.

Merged the BOEM_Pacific_Pipelines_2011-08 & ppl_arcs projected layers into one layer called BOEM_MC_Pipelines.

Utilizing the select by location for all other layers individually NaturalGas_Pipelines_US_201804_project_erase , PetroleumProduct_Pipelines_US_201801_project_erase, ME_project_erase, mv_infra_pipeline_ln_project_erase , MS_Natural_Gas_Pipelines_project_erase , LAPipelinesfromTIMS_project_erase, Offshore_pipelines_project_erase select the attributes that intersect with the Pipelines feature class & export this data with a naming convention that ends in layername_Conflict & add this back to your map. Reselect the data that intersects the Pipelines using the Select by location and reverse the selection so that you have all of the pipelines that are not currently present in the Pipelines feature class, using the Editor copy the data into Pipelines feature class.

Copy all data in the BOEM_MC_Pipelines dataset and save as a new Pipelines feature class. Starting with California, individually confirm Emmy_oil.shp , Emmy_oil_and_low_pressure_gas.shp , Emmy_water_and_high_pressure_gas.shp , Esther_gas.shp , Esther_oil.shp , Eva_gas.shp , Eva_oil.shp , Holly_gas.shp , Holly_oil.shp , Holly_Power_Cable.shp , & spps tent gas.shp attributes were not present in BOEM data and added to the Pipelines feature class using the Editor.

Create Status_Descrpt & Prod_Descrpt attributes and fill in the information required using the Select by Attribute feature in the table to select for the status code or product code that is provided by BOEM/BSEE. https://www.data.bsee.gov/Main/HtmlPage.aspx?page=pipelineMastersFields#Prod%20Code

Once the conflicting data has been edited & remove pipelines that already existed you will be left with pipelines to add to the Pipelines feature class, which can be completed with the Merge tool or utilizing the Editor tool. The Pipelines feature class now has all pipelines added into the attributes.

Create attributes STATUS_CODE, PPL_SIZE_CODE, PROD_CODE, SDE_COMPANY for each layer and populate using the information available from each layer assuring that schema is matching to the BOEM/BSEE layers - https://www.data.bsee.gov/Main/HtmlPage.aspx?page=pipelineMastersFields#Prod%20Code . Turn off attributes in the fields tab that will not be needed moving forward for all 20 data layers/deleted empty attributes so that when exported only the important attributes move forward.

The Pipelines feature class with now have all data that was not conflicting from all layers present. Go through each "layername_Conflicting" data set utilizing the Editor tool and remove any pipelines that you can confirm are already present in the Pipelines feature class. Utilize the STATUS_CODE, PPL_SIZE_CODE, PROD_CODE,& SDE_COMPANY attributes that you already filled out to see if the data is truly already present. If a pipeline did not have information available & a N/A was filled in it will not be possible to determine if this line has already been gathered so it should be left in.