Import feature-layer templates

Use shared WFS and OGC API views by file, HTTPS link or QR link, without a built-in worldwide service list.

Service, layer, view or data file?

A service supplies data over a network. A layer is one dataset within it. A view defines filters, area and styling. A .mtfeature.json file shares that configuration; it contains no downloaded features. GeoJSON contains geometry and attributes and is imported as a data file.

Import a template

  1. Download a .mtfeature.json example below or copy its HTTPS link. Open Online feature services in MapTools.
  2. Choose Import view template for a file, or Import template link for the URL. QR links use the same download confirmation.
  3. Check the provider and terms. Set up the source if needed, load its layer fields, inspect the conditions and save a copy. Enable the view in your map slot.
Template review before configuring the public Berlin source.
Template review before configuring the public Berlin source.
The template supplies the public WFS endpoint to the source dialogue.
The template supplies the public WFS endpoint to the source dialogue.

Set up a service without a template

  1. Open Online feature services, choose WFS or OGC API and enter the provider’s HTTPS endpoint. A WMS address supplies map images and cannot replace it here.
  2. Discover the feature layers, select the relevant dataset and save the source. Open New view and load or refresh its fields.
  3. Use + to add conditions or groups. All conditions means AND; At least one means OR. Nest, for example, (type = A OR type = B) AND status = active. Field names, units and values belong to the provider.

Check, display and work with results

Check the preview in a small relevant map area. Save the view and enable it in the map slot. With the Map viewport area option, moving the map triggers another request; a fixed area remains fixed.

Tap displayed features for available attributes. For incomplete results, tap the status message for the reason and counts. Zoom in or narrow the query; zero matches in a sample do not prove complete absence.

HTTPS is required, including for private local servers. Private network addresses are allowed. For your own CA or server certificate, configure explicit trust for the server host and port in the certificate settings. Hostname and validity checks remain active; HTTP is not supported.

Examples

Hessen selects boundary stones with code 1110 and official position AU. Berlin selects street trees with trunk circumference at least 315 cm, approximately 100 cm diameter; circumference is not diameter.

Choose a small map area in the relevant region. Results may be limited; tap the map status for the reason and counts. These data do not confirm a stone in the field or provide an RTK measurement.

What does your own template contain?

Export a configured view in the app. The file contains the service address, layer identifier, required fields, filters and styling, plus any code-catalogue references. Credentials are not shared. Still check names, descriptions and any deliberately exported area for private information. Use the app export as the format reference; do not replace technical identifiers with translated display names.

Create, share and update

Configure your own view and export it as a template. Leave area sharing off unless intended. Publish only public endpoints and your own conditions, without credentials or private locations.

Each import creates an independent copy. Website changes do not update saved views; reimport deliberately and remove old copies if desired. Providers may require registration, payment or a licence. Downloads contain our configurations, not the datasets or third-party code catalogues; check the original provider terms.

.mtfeature.json · JSON
{
  "format": "maptools-feature-template",
  "version": 1,
  "name": "Berlin · denkmale:denkmale",
  "endpoint": "https://gdi.berlin.de/services/wfs/denkmale",
  "protocol": "WFS",
  "collection": "denkmale:denkmale",
  "namespace": "denkmale",
  "requestCrs": "urn:ogc:def:crs:EPSG::4326",
  "requiredFields": {},
  "area": { "type": "viewport" },
  "positionMode": "SOURCE_GEOMETRY"
}