GeoJSON Specification (2.9.0)

Our upload feature accepts FeatureCollection GeoJSON files with optional CRS definitions and multiple geometry types.

1. Overview

Users can upload spatial data into Map View using a simple, structured GeoJSON format.

Supported objects include:

• Points (well locations)

• LineString (paths, pipelines)

• Polygon (leases, tenements, areas)

• MultiLineString

• MultiPolygon

💡 Tip: If you are unsure how to create GeoJSON, use common GIS tools such as QGIS, ArcGIS, or http://geojson.io .

2. Supported GeoJSON Structure

All uploads must follow the FeatureCollection → Features → Geometry → Properties pattern.

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": { "well_name": "ABC123" },
      "crs": { "type": "name", "properties": { "name": "EPSG:4326" }},
      "geometry": {
        "type": "Polygon",
        "coordinates": [
          [
            [138.6, -34.92],
            [138.7, -34.92],
            [138.7, -34.95],
            [138.6, -34.95],
            [138.6, -34.92]
          ]
        ]
      }
    }
  ]
}

3. Required Elements

4. Coordinate Reference System (CRS)

The CRS section is optional.

If included, it must follow the format below:

"crs": {
  "type": "name",
  "properties": {
    "name": "EPSG:xxxx"
  }
}

Supported CRS values

⚠️ If no CRS is provided, the system assumes WGS84 (EPSG:4326).

5. Geometry Examples

5.1 Point

"geometry": {
  "type": "Point",
  "coordinates": [138.601, -34.928]
}

5.2 LineString

"geometry": {
  "type": "LineString",
  "coordinates": [
    [138.60, -34.92],
    [138.65, -34.93],
    [138.70, -34.94]
  ]
}

5.3 Polygon

"geometry": {
  "type": "Polygon",
  "coordinates": [
    [
      [138.6, -34.92],
      [138.7, -34.92],
      [138.7, -34.95],
      [138.6, -34.95],
      [138.6, -34.92]
    ]
  ]
}

5.4 MultiLineString

"geometry": {
  "type": "MultiLineString",
  "coordinates": [
    [
      [138.60, -34.92],
      [138.65, -34.93]
    ],
    [
      [138.61, -34.91],
      [138.63, -34.90]
    ]
  ]
}

5.5 MultiPolygon

"geometry": {
  "type": "MultiPolygon",
  "coordinates": [
    [
      [
        [138.6, -34.9],
        [138.7, -34.9],
        [138.7, -34.95],
        [138.6, -34.95],
        [138.6, -34.9]
      ]
    ],
    [
      [
        [138.8, -34.8],
        [138.9, -34.8],
        [138.9, -34.85],
        [138.8, -34.85],
        [138.8, -34.8]
      ]
    ]
  ]
}

6. Optional: Map Bounds

You may include a suggested map bounding box for zooming:

"mapBound": [minLon, minLat, maxLon, maxLat]

Example:

"mapBound": [-102.55, 30.71, -99.98, 33.64]

7. Behaviour When Extra Data Exists

To avoid unpredictable behaviour, the AFA will ignores:

Ignored Feature Fields

• Unknown or extra root-level fields

• Additional fields inside properties other than well_name

• Any metadata not explicitly listed (e.g., id, timestamp, owner, custom JSON objects)

Ignored Geometry Elements

• Unsupported geometry types

• Extra geometry keys

• Z-values or M-values (e.g., [lon, lat, elevation])

Ignored CRS Forms

• Non-standard CRS formats

• Embedded CRS definitions inside properties unrelated to crs.type = "name"

Ignored Non-GeoJSON Content

• Anything outside the standard FeatureCollection structure

This ensures the upload system remains fast, secure, and predictable.

8. Common Errors & How to Fix Them

9. Best Practices

• Use short property names (e.g., well_name, field).

• Avoid unnecessary nesting.

• Keep coordinates below 1,000 points for performance.

• Prefer EPSG:4326 unless your organisation uses GDA2020.

• For polygons, always ensure first = last coordinate.