For the complete documentation index, see llms.txt. This page is also available as Markdown.

🗾How to add your own area to GNW Horizon

Upload a boundary file or draw your area on the map, then analyze it or build a dashboard for it. Takes about five minutes.

Goal

By the end of this guide, your own area of interest is saved in GNW Horizon, named the way you want, and ready to analyse.

What you need

  • Your boundary as a .geojson, .csv or zipped shapefile (.zip), or a rough idea of the boundary so you can draw it.

  • Optional: QGIS (free) or another GIS tool to check or fix your file.

Choose how to add your area

Method

Best for

Where to start

A. Upload a file

Exact boundaries you already have (CSV or shapefile)

Map > Areas > Upload file

B. Draw on map

A quick, approximate boundary when you do not have a file

Map > Areas > Draw on map

C. Upload from Dashboards

Going straight to monitoring: a dashboard is created for you

Dashboards > Upload area

Option A: Upload a file

  1. Select Map in the top bar. Below the assistant chat box, select Areas.

  1. At the top of the Areas panel, select Upload file.

  1. In the Upload Area window, drag your file into the box, or select Select File. The window lists the accepted file types and limits.

  1. Check the file name, then select Upload. If the file has a problem, a red message appears instead. See If you see this error below.

  1. Horizon zooms to your area, outlines it on the map and adds it to the AI-assistant pane as context. GeoJSON uploads get a name assigned by Horizon (e.g.: "Pristine Valley").

  1. Check the location. Make sure the outline is where you expect. If it is in the wrong place (for example, in the ocean), your latitude and longitude could be swapped.

  2. Rename the area. In the Areas panel, select My areas, select the three dots next to your area, then Rename. Type a name and select Save.

Tip: select the target icon next to an area in My areas to centre the map on it.

Option B: Draw on map

  1. Select Map, then Areas. Zoom in to your area first: drawn areas are limited to 10,000 km².

  2. In the Areas panel, select Draw on map.

  1. Click the map to add points around your area. Double-click to add the last point and finish.

  1. Horizon suggests a name for the area. Select Save area to keep it, Redraw to start again, or Cancel.

If your shape is too big, Horizon shows the size and the limit. Select Try again and draw a smaller area.

Option C: Upload from Dashboards

  1. Select Dashboards in the top bar. Under Create new dashboard, select Upload area.

  1. Upload your file in the same Upload Area window as Option A.

  2. Horizon creates a dashboard for your area straight away and opens it. Start with an analysis template, such as Near real-time monitoring or Post-2020 forest loss, or ask the assistant to add charts, maps and imagery.

What you can do with your area

Select the three dots on the area label on the map to:

  • Generate Insights or View Analysis for the area

  • Create Dashboard to monitor the area over time

  • Remove from map (the area stays saved in My areas)

Your areas are listed under Map > Areas > My areas and under Dashboards > Create new dashboard > Custom areas.

Prepare your file

Use a CSV or zipped shapefile when you have several areas: each row or feature becomes its own area, named from your file.

Format

Size limit

Areas created

Area name

Must include

GeoJSON (.geojson)

1 MB

One per file

Assigned by Horizon; rename after upload

A Polygon or MultiPolygon

CSV (.csv)

10 MB

One per row

From the name column

A name column and a geom column of WKT polygons in longitude, latitude order

Zipped shapefile (.zip)

10 MB

One per feature

From the name attribute

The .shp, .shx, .dbf and .prj files, and a name attribute

A CSV row looks like this:

We are working to align the three formats to have the same requirements, and to provide additional formats in the future.

Before you upload: checklist

  1. The file extension is .geojson, .csv or .zip. A .json or .kml file is rejected. Rename a .json file to .geojson; convert KML to GeoJSON first.

  2. The file is within the size limit: 1 MB for GeoJSON, 10 MB for CSV and zipped shapefiles. Simplify the boundary or reduce coordinate precision if needed.

  3. The geometry is a polygon. Polygon and MultiPolygon are both accepted. Points and lines are rejected; buffer them into polygons in your GIS tool first.

  4. Each area is between 10 hectares (0.10 km²) and 10,000 km². Split very large areas into smaller ones.

  5. A GeoJSON file holds one area. A GeoJSON file with several features creates only one area. To upload several areas at once, use a CSV or zipped shapefile.

  6. The boundary is closed and does not cross itself. The first and last coordinates must match. Fix in QGIS: Vector > Geometry Tools > Fix Geometries.

  7. Coordinates are in longitude, latitude order. Swapped coordinates are not flagged: the file uploads, but the area lands somewhere else in the world. This often happens when building a file from a spreadsheet.

  8. Areas made of separate parcels (one MultiPolygon with parts that do not touch) upload as one area, and analysis covers every part. The map may only outline one part. To see and analyse each parcel on its own, upload them as separate rows in a CSV or separate features in a shapefile.

  9. No need to fix a "crs" block or the direction of your boundary points. Horizon accepts both.

If you see this error

Message

What it means

Fix

"Only .geojson, .csv, .zip files are supported"

Wrong file type, for example .json or .kml

Rename .json to .geojson, or convert the file

"File size exceeds 1MB limit"

GeoJSON file is over 1 MB

Simplify the boundary, or use a zipped shapefile (10 MB limit)

"No valid Polygon or MultiPolygon features found"

The file has no polygons, for example only points or lines

Re-export or buffer the area as a polygon

"Area is too small (X km²). Minimum area is 0.10 km²."

The area is under 10 hectares

Use a larger boundary, or check for swapped coordinates

"Area is too small (0.000 km²)" for an area that is clearly larger

The boundary crosses itself

Run Fix Geometries in QGIS, then upload again

"Area is too large (X km²). Maximum is 10,000 km²."

The area is over 10,000 km²

Split it into smaller areas

"Failed to process file. Please try again."

Often a boundary that is not closed

Make the first and last coordinates match, then upload again

No error, but the area is in the wrong place

Latitude and longitude are swapped

Swap to longitude, latitude order and upload again

No error, but fewer areas than expected

A GeoJSON file with several features creates one area

Upload a CSV or zipped shapefile, or one GeoJSON file per area

Example: an unsupported file type shows a red message under the upload box.

Try this prompt

Copy into the assistant

"Give me a summary of land cover change in [your area name] over the last five years."

What to do next

  • Ready to explore your area? Try Run your first analysis.

  • Want to check forest loss since 2020? Try Check post-2020 forest loss and alerts for your area.

  • Want to track the area over time? Try Create a dashboard.

Test

Route

Result

GeoJSON over 1 MB (1.4 MB)

Map

Rejected: "File size exceeds 1MB limit"

KML file

Map

Rejected: "Only .geojson, .csv, .zip files are supported"

GeoJSON, about 17,600 km²

Map

Rejected: "Area is too large (17,604 km²). Maximum is 10,000 km²."

Drawn area, about 148,700 km² and 12,700 km²

Draw on map

Rejected: "Area too large: X km². Maximum is 10,000 km²." with Try again

Drawn area under 10,000 km²

Draw on map

Accepted; suggested name "Upper Chari River Basin" (cancelled, not saved)

GeoJSON with "crs" block

Map

Accepted ("Remote Ridge")

GeoJSON, clockwise ring

Map

Accepted ("Vibrant Lake")

Self-crossing (bowtie) ring

Map and Dashboards

Rejected: "Area is too small (0.000 km²)"

Unclosed ring

Map

Rejected: "Failed to process file. Please try again."

MultiPolygon, two separate parts, large part first

Map

Accepted as one area ("Vibrant Grove"); only first part outlined

MultiPolygon, small part (about 5 ha) first, large part 11 km away

Map

Accepted ("Remote Peak"), so the size check counts both parts. Tree cover loss chart showed about 55 ha in 2001, more than the small part alone, so analysis covers both parts. Only the small part is outlined.

Valid GeoJSON with a "name" property

Map

Accepted; name ignored, assigned "Pristine Valley"; renamed to "Farm boundary"

Valid GeoJSON

Dashboards

Accepted; dashboard "Hidden Grove" created and opened

Last updated