This is a GitHub repository at Global Energy Monitor to store pipeline routes.
Individual routes are stored as [ProjectID].geojson
, in the data > individual-files
folder.
If a given project does not have a route, either because it's a capacity expansion with no actual new pipeline associated with it, or because we haven't created the route yet or cannot find a map to trace online, we STILL create a .geojson
file for it, it's just stored as an empty GeoJSON file (i.e., None
-type geometry).
An example of an "empty" GeoJSON file could look something like this:
{
"type": "FeatureCollection",
"crs": { "type": "name", "properties": { "name": "urn:ogc:def:crs:OGC:1.3:CRS84" } },
"features": [
{ "type": "Feature", "properties": { "ProjectID": "P6445" }, "geometry": null }
]
}
or like this:
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"geometry": null
}
]
}
If you update a route or multiple routes...
firstname-p9998-p9999
)If you are comfortable working in QGIS or JOSM, those are the most complex ways to do it. Create a route or edit an existing one and re-export it as a GeoJSON file. You don't need to include any specific information about the pipeline itself (name, status, etc.) in the GeoJSON file; the only way I ask you to label it is via the title: [ProjectID].geojson
. (You can of course include more info, but it's not necessary.)
If you're creating a new route from scratch, and the tools above aren't familiar, try using geojson.io or placemark.io.
If you're editing an existing route, you can import the GeoJSON file that already exists for it
The GeoJSON file format specification says that GeoJSON files use a WSG 84 (EPSG:4326) coordinate reference system, so this is expected for all pipelines and no crs is required in the GeoJSON file.