Talk:Oil and Gas Infrastructure

From OpenStreetMap Wiki
Jump to navigation Jump to search

Hello Mike, nice Work! You should publish it more prominent in the Wiki. May be you can add some photos explaining the words? and add the things around power plants (often combined with oil and gas harbours). Thanks, -- Markus 07:39, 26 May 2011 (BST)

DE: Vorschlag

Der Vorschlag sollte schnellsten umgesetzt werden. Es gibt mittlerweile schon in Deutschland allein viele Erdgasstationen und Tankstellen. Vorschlag: (Google-Translator - EN:The proposal should be implemented rapidly. Meanwhile, there are already many gas stations in Germany alone, and gas stations. proposal:)


industrial=natural gas (Erdgas oder lpg {für Flüssiggas} oder natur oil {für Erdöl} oder oil {für andere Öle})

man made=works (für Fördergebiete)

man made=pumping station (für Druckerhöhungsstation)

man made=pipeline (für Leitung/Pipeline) (layer=-1 für Untergrund?)

man made=distribution station (für Verteilerstation/Schiebergruppen)

man made=regulating station (für Reglerstation)

man made=tank (für Speicher/Tank)

operator, name, usw. nach Bedarf

siehe auch:


Nachtrag aus Forumsmeinungen (17.06.2011):

 -  pumping_station ist eine Pumpstation, wie sie zur Druckerhöhung alle xx km in Piplines notwendig ist. 
    Eine Förderstation wird mit *_well bezeichnet (petroleum_well, water_well) 
 -  pipeline + location=overground/underground/underwater + type=gas (besser material=gas) 
 -  statt tank besser storage_tank + content=*

--Geri-oc 12:56, 16 June 2011 (BST)

Gas Pipelines in United Kingdom

UK gas pipelines (on the high pressure system) are available online as shapefiles - no statement of copyright though so off bounds for OpenStreetMap at the moment. The attributes are:

  1. Pipeline reference (e.g. "Feeder 7")
  2. Section reference (e.g. 983108)
  3. Section name (e.g. "FM02 - Bacton to Brisley")
  4. Owner
  5. Diameter
  6. Maximum Operating Pressure (in bar)
  7. Steel grade (e.g. X60, X52)
  8. Wall thickness (in mm)
  9. Year commissioned.

The diameters are in mm but it's my understanding that we are still building in inches in the UK. I can check that if you'd like.

Above ground installations (AGIs) can comprise one or more of: Block Valve, Multi Junction, Compressor Station, LNG storage, Minimum Offtake, Offtake, Distribution Offtake, Pig Trap, Entry Terminal. --RobJN (talk) 21:48, 27 May 2014 (UTC)

Unfinished O&G infrastructure tagging proposal

With apologies, this proposal is too much work for me, at least for the foreseeable future. If anyone else wants to do something with it you are welcome too.--Martin2014 (talk) 12:06, 27 June 2014 (UTC)

Licence blocks

Licence blocks dictate who is allowed to drill where, when. In quite a few cases the data is made available in the public domain at a country level, so could be relatively easy to include in OSM.

Geometry Key Value Description Usage Comment
node area industrial hydrocarbon_field Tagged to a polygon showing the outline of the deposit (if data is available),
or a node showing the deposit's approximate centre-point.
hydrocarbon_field oil Recommended
status undeveloped A hydrocarbon deposit which has no extraction infrastructure on the surface Recommended
reserves:bboe <numerical value> This number indicates the "recoverable reserves", also known as "proven reserves" or "reserves" in the deposit. [1] [2]
"The units we are using is Billions of Barrels of Oil Equivalent (bboe) which wikipedia suggests for measuring petroleum reserves. The unit is written in the key.
The data sources you are using might have the figure in:
boe (barrels of oil equivalent)
kboe (sometimes used for thousands of barrels of oil equivalent)
mboe (thousands of barrels of oil equivalent)
Mboe (can also mean miilions of barrels of oil equivalent)
mmboe (millions of barrels of oil equivalent)
toe (tonne of oil equivalent)
depth:m <numerical value> The depth below the surface at which the deposit is located in metres. Optional
water_depth:m <numerical value> For offshore fields the water depth in metres should be entered as well as the total depth. for offshore fields only
reservoir_rock sandstone This identifies the type of underground rock containing the resource. Optional
discovery_date YYYY-MM The date the deposit was discovered Optional
production_date YYYY-MM The date that production started on the field Optional

Geometry Key Value Description Usage Comment
node man_made petroleum_well A boring through the earth's surface that is designed to find, acquire or aid in the extraction of hydrocarbons (oil, gas & condensate). Mandatory
petroleum_well oil A crude oil production well Such wells primarily produces crude oil, but it is assumed that some associated gas is also being produced. Recommended
gas A natural gas or "dry gas" production well These typically produces only raw natural gas that does not contain any hydrocarbon liquids.
condensate A natural gas condensate or "wet gas" production well These produce raw natural gas along with natural gas liquid.
abandoned A well that has been abandoned for technical reasons during the drilling process. For production wells that have been abandoned because they are no longer economically viable, see disused=yes below
disused yes For disused production or injection wells use this tag in conjunction with petroleum_well=* so its clear what kind of well it is that is not in use. Optional
location onshore Default value: If the location=* key is not used the well is assumed to be onshore. not necessary
offshore An offshore well with some kind of offshore platform. Recommended for offshore & subsea wells Offshore platforms should also receive the OpenSeaMap tags:
subsea Remote sub-sea wells that are connected by pipeline to a platform. [3] [4]
method natural_pressure Optional
well_count <numerical value> If the well_count=* key is not used then the well_count is assumed to be 1. Recommended for well clusters
cluster If its impossible to tell how many wells there are in the well cluster, use this tag.
operator <company name> The name of the company which operates the well Optional
name <name of the well> This identifies the well. Well "names" are often numeric or alphanumeric. Optional
field_name <name> The name of the field which the well is part of. Optional
date_drill <YYYY-MM> The year & month that the well was drilled. If only the year is known, just mark the first four digits. Optional

man_made=petroleum_well conflicts with man_made=pumping_rig, which is already approved. IMHO man_made=pumping_rig always implies "oil". Presumably man_made=petroleum_well and man_made=pumping_rig are intended to be used mutually exclusive?

This whole tagging proposal is a result of me being a bit overwhelmed by the number of conflicting O&G tags in use, and trying to streamline and rationalise it all, as well as trying to make it comprehensive.
My thought on the man_made=petroleum_well, man_made=pumping_rig conflict is that pumping rig only describes the apparatus on the surface / method of extraction rather than the existence of the oil well itself, which is what is primarily being mapped:
Pumping rigs don't exist without oil wells, but oil wells do exist without pumping rigs.
Therefore pumping rig should have a "second tag" status to the well itself, which in the above suggestion would be man_made=petroleum_well, petroleum_well=oil, method=pumpjack. I'd be proposing that this three tag combination should replace man_made=pumping_rig If this proposal were ever to be finished.
Im aware that the list of values for the method=* key above needs more research and work. "method" was the best word I could think of that might be able to encompass everything, rather than something like "apparatus".
Incidently, thanks for helping with the pipeline type values list, that was cool of you. I'm going to get back to it. --Martin2014 (talk) 16:16, 23 October 2014 (UTC)
thanks for completing the list! the pipeline extension proposal is now in RFC state, with discussion going on on the talk page and the "tagging" mailing list. hope that I can help out with your proposal soon, if knowledge allows ... --Rfuegen (talk) 09:12, 15 November 2014 (UTC)
No problem. Any input is always welcome, Im only learning as I go too. Do you have a link to the "tagging" discussion, I don't seem to be on that mailing list. thanks. --Martin2014 (talk) 23:44, 16 November 2014


you can find the web archive here: (check the end of the list). discussion is also taking place on the talk page.--Rfuegen (talk) 21:43, 17 November 2014 (UTC)
List of possible platform_type=* values.
Key Value Description Comment
platform_type fixed_platform
platform_type compliant_tower
platform_type semi
platform_type TLP
platform_type GBS
platform_type GBS_condeep
platform_type spar_platform
platform_type NUI


"man_made=petroleum_well" should be tagged to the well or apparatus directly over the well. On land the area surrounding the well is known as the "well pad", "well site", or "wellsite" in OSM. (Offshore platforms do not count as wellsites. For offshore platforms please use the "location=offshore", "platform_type=*" scheme above)

Wellsites should be drawn as a polygon and tagged like this:

Geometry Key Value Description Usage Comment
area industrial wellsite "This is an oil & gas industry well site." Mandatory Though it has so far only been used over a small geographic area in Colorado, this tag is the most popular tag for O&G well sites, with about 1000 uses.
landuse industrial This is the appropriate landuse=* tag for O&G well sites. Mandatory
field_name <name> eg:tengiz This identifies which field this wellsite belongs to. Optional

Produced water resevoirs

wikipedia - Produced water

This tag combination is based on the existing landuse=resevoir tagging scheme because the alternate scheme based around natural=water sounds misleading in this instance - produced water is viewed as an industrial waste product rather than something natural.


Roads on oil and gas fields

This is the suggested tag combination for roads that connect the well sites and complexes on oil & gas fields.


On-site residential areas in oil & gas fields

Crude Oil Refineries and Natural Gas Processing plants

The industrial=refinery tag has already been used to map the refineries in Europe. For natural gas processing plants the additional tag product=gas has been used

refinery=oil "this is a crude oil refinery"
refinery=gas "this is a natural gas processing plant"
name=* The name of the refinery
operator=* The name of the company operating the refinery.
landuse=industrial This is the appropriate landuse=* tag for refineries.

Refineries contain a assortment of distinct units. They can be labelled like this:

Production facilities, Terminals, Depots

A "terminal" is where a product gets transported to, stored, sometimes processed or changed in some way, then transported from, sometimes in a different mode of transport. So, for example, an LNG liquefaction terminal could be tagged like this


Floating Storage and Offloading vessel (FSO)
Storage tanks that are painted black are designed to absorb solar energy and stay warm. They contain the more viscous petroleum products, such as heavy fuel oil, which only flow properly when they are warm.
Storage tanks that are painted white are designed to reflect solar energy and stay cool. They contain petroleum products with volatile constituents.
"Floating roof tanks" are circular and have a roof that floats on the surface of the liquid, eliminating the cavity that exists in a conventional tank. They contain liquids such as crude oil and gasoline which have volatile constituents that would evaporate if there was a cavity.

Tanker routes

Ferry routes are currently being marked in OpenSeaMap as seamark:ferry_route:category=*. So, it seems feasible that tanker routes (and maybe 'dry' cargo shipping routes too) could also be marked.

seamark:tanker_route:category=* LNG | oil

O&G Rail routes

This is a additional tag on top of the current usage key.

usage:industrial=* < oil | fuel | hydrocarbons | coal | bauxite | etc >

General O&G tags

If you spot something, such as an industrial complex, which you suspect to be part of the oil and gas industry, but don't know more than that, use the tag:

note=* state your reasoning

And if you know whether it is either oil or gas related, use:


These tags can act as "holding tags", and will flag the area for the attention of someone with more specialist knowledge.

Environmental & humanitarian issues

volume:bbl=* <numerical_value>
location=* <onshore | offshore | subsea>
operator=* Name of the company or companies resposible
oil_spill:type=* <tanker | blowout | pipeline>
duration:days=* <numerical_value> (if applicable)

population=* <numerical_value>
name=* Name of the settlement
operator=* Name of the company or companies responsible
project=* Name of the project

Text from the WikiProject Oil and Gas Infrastructure page from 2011


The location of oil and gas infrastructure is something that becomes periodically of great topical interest for journalists and the general public. As of writing, there is little tagged within the OSM database, and what there is is difficult to find. For example, a major refinery may be tagged only as man_made=works.

This is a research and experimental project to systematically tag such facilities in a way that can easily be found by search engines such as Nominatim and for making specialist maps. I am trying to use existing tagging scheme where possible. Except where noted, tags are suggestions only and discussion is welcome. MikeCollinson 09:14, 12 March 2011 (UTC)

Proposed tagging

Oil and gas pipelines

For the pipeline itself, a good tagging scheme exists, man_made=pipeline

For subsea pipelines, see seamark:type=pipeline_submarine

Oil and gas tank farms

Used to store oil or gas and usually located at a transhipment centre such as a ship harbour or railway. man_made=storage_tank

Oil and gas tanker ship facilities

See Harbour tagging for an excellent schema for tagging harbours. For O&G purposes, it lacks a method to differentiate between oil and LNG tanker loading. Suggestion:

industrial=oil industrial=gas

Oil refineries


landuse=industrial man_made=works


landuse=industrial industrial=oil industrial=gas

Case Study

Sidi Kerir on the Egyptian coast consists of a tanker harbour, tank farm, possibly a polyethelene production facility, and the terminus point of the SUMED pipiline.

Harbour (node)

  • harbour=yes
  • harbour:main=yes
  • harbour:category=tanker
  • harbour:size=very small
  • industrial=oil
  • operator=Arab Petroleum Pipelines Co. (SUMED)
  • name=Sidi Kerir Terminal
  • harbour:LOCODE=EG SKT
  • harbour:portindex
  • description=6 SBMs capable of accommodating vessels 150,000 to 400,000 DWT

Tank Farm (area)

  • landuse=industrial
  • industrial=oil
  • name=Sidi Kerir tanker facility
  • alt_name=Sidi Kerir Sea Terminal
  • operator=Arab Petroleum Pipeline Co.
  • note=name identification is tentative


  • building=tank
  • source=Bing

Pipeline (way)

  • man_made=pipeline
  • type=oil
  • name=SUMED pipeline ?
  • alt_name=Suez-Mediterranean Pipeline
  • length=220 mile
  • description=ng at Ain Sukhna termina on the Gulf of Suez to Sidi Kerir tanker facility on the Mediterranean just west of Alexandria. Runs south of Cairo.
  • note=the identification and route of this pipeline is from Bing imagery only and needs corroborating.
  • operator= Arab Petroleum Pipeline Co.
  • source=Bing

Nominatum search phrase suggestions

  • Oil refinery, oil refineries, refinery, refineries
  • Oil pipline(s), Gas pipiline(s)
  • Oil rig, oil well
  • Oil terminal, tanker facility, tanker terminal

Fuel depots

I've created a proposal for industrial=fuel_depot. Edits and comments are more than welcome here.

Seismic survey / prospection leftovers

How to tag such: lines or craters that appear (and persist) by techniques used to locate oil in the ground (

--SLMapper1 (talk) 01:23, 15 May 2022 (UTC)

Page quality

There seems to be some questionable content on the page, for example, "man_made=fuel_deport" and "man_made=fuel storage_tanks". It seems to be mostly abandoned since the initial creation in 2014, with user Mentor doing some cleanup lately. Overall, it seems like a harsh culling might be in order :) --Richlv (talk) 11:48, 11 July 2023 (UTC)