Edit your maps in QGIS

You can open the design features of your maps in QGIS (3.x) or any other GIS program that speaks WFS, edit them there, and save them back to landplan.io. The app shows the changes like any other edit: the other people on the map see them, and your quotes and reports use them.

What you need:

• An API key with the wfs:edit scope (or wfs:read to look only).
• QGIS 3.x.

You see and edit exactly what you can in the app: your own maps, the maps shared with you (read only when you may only view them), and, with an organization's key, the organization's projects.

1. Create an API key

Your own key. Open the account menu, then Account > API keys. On your API client's card, click New key, give it a Name (for example QGIS on my laptop), choose the wfs:edit scope (or wfs:read), and click Issue key. Copy the key: it is shown once. It looks like lp_1a2b3c4d_<secret>.

If the page says No API access yet, write to support@landplan.io: we set up an API client for your account. The WFS scopes are free: QGIS calls are never billed or counted against a plan.

An organization's key (Enterprise): an Owner or Admin opens Organization > API keys and creates a key with wfs:edit (see Organization). It acts as the organization: it reaches the organization's projects (not the private ones, and read only while the organization is read-only), never a member's personal projects.

Treat the key like a password. Anyone who has it can edit your maps. Revoke it on the same page if you lose it; it stops working within a minute.

2. Connect QGIS

1. In QGIS, open Layer > Add Layer > Add WFS / OGC API - Features Layer.
2. Click New and fill in:
   • Name: for example landplan.io.
   • URL: https://fastapi.landplan.io/design/v1/wfs
   • Authentication > Basic: User name: anything (for example your email); Password: your API key.
   • Version: Maximum (or 2.0.0). Leave the other options as they are.
3. Click OK, then Connect. The list shows one layer per kind of feature: tanks, pipes, septic_tank, sewer_main, soil_test and so on.

One map only. To work on a single map, use the map's own URL: https://fastapi.landplan.io/design/v1/wfs/maps/<map id>. The layers then hold that map's features only, and a feature you draw goes into that map without filling in map_id. Ask support@landplan.io for a map's id if you don't have it.

3. Layers and fields

Add the layers you need. QGIS loads the features of the area on screen.

• Two kinds of layers. The tables named after a group (tanks, pipes, site_areas, ...) keep each feature's properties in one field, props (JSON). The tables named after one type (septic_tank, sewer_main, drip_zone, ...) have one field per property: edit those when you can.
• Fields you can't change. id, map_id, version, project_id, the dates and who changed a feature last are kept by landplan.io. Edits to them are ignored.
• New features. Fill in map_id (the map's id), unless you connected with the map's own URL. id is filled in for you. The group tables also need layer_id and type (for example Septic Tank and septic_tank).
• Deleting a feature removes it from the map. landplan.io keeps it, so it can be restored.
• Parcel lines and buffers are read only here: change them in the app.

Edit as usual, then click Save Layer Edits.

4. When someone else changed the same feature

landplan.io never lets one person's save silently overwrite another's.

Each feature QGIS loads carries the version it had at that moment. When you save, landplan.io compares:

• Nobody changed it since: your change is saved.
• Someone changed something else (you moved the feature, they changed an attribute, or the other way round): both changes are kept.
• Someone changed the same thing, or deleted the feature, or you delete a feature someone changed: nothing of that save is written, and QGIS shows an error like Conflict on tanks.…: it was changed since you read it (version 3, now 4): name. Nothing was saved: reload the layer to get the current features, then make your edit again.

To continue after a conflict: in QGIS, Toggle Editing off and discard your edits (or note them), right-click the layer and choose Reload, then make the edit again on the current feature.

Your own saves never conflict with each other: you can edit a feature, save, and edit it again in the same QGIS session. A second QGIS window (or a colleague with the same organization key) is a separate session: there, reload the layer first.

Limits

• At most 5,000 features per request and 500 changes per save. QGIS pages through larger layers.
• Only the design layers are offered. Basemaps, parcels and other landplan.io data layers are not editable here.
• QGIS sees the features of the maps you can open in the app. A map you may only view can't be saved.
• A key works only for the scopes it has: wfs:read can't save.
• A revoked key stops working within a minute.

Other GIS programs

Any WFS 1.1 or 2.0 client works the same way: the key as the Basic password (or Authorization: Bearer <key>), and the feature ids landplan.io returns (<layer>.<map id>.<feature id>.v<version>) in your Update and Delete filters. A program that builds its own filters can name the version instead, with version = n in the filter or a version property in the update.