Prepare ALKIS Hesse boundary points in QGIS and export GPX

Set up official maps and aerial imagery, distinguish boundary-point positions, filter markers and export selected waypoints for MapTools.

1. Create a QGIS project with a clear coordinate reference system

  1. Create a project and set the project CRS to EPSG:25832, ETRS89 / UTM zone 32N. Easting and northing are expressed in metres.
  2. Keep the QGIS project and its local point files in one folder. Add existing GeoJSON point files through the Browser panel or the vector data source manager. Check each source layer CRS; a project CRS setting alone does not repair incorrectly assigned source coordinates.
  3. Keep TA and AU as separate layers. Retain the point identifier, source-object identifier, position type, marker code, coordinate status, accuracy class and retrieval date. Save the project as a QGZ file.

A QGZ project stores the layer configuration and references. External GeoJSON files must travel with it. A saved local extract is a snapshot and does not update itself.

2. Add Hesse maps and orthophotos

  1. Open Data Source Manager → WMS/WMTS → New. Create separate connections for the maps service and the imagery service using the two base URLs below.
  2. Connect, select the required layer and add it. Use EPSG:25832 where offered and PNG for transparent overlays. The addresses shown here are WMS services; the combined WMS/WMTS dialog does not turn them into WMTS services.
  3. Place point layers above the backgrounds. Display one opaque background at a time and zoom in if a layer is blank at the current scale.
https://www.gds-srv.hessen.de/cgi-bin/lika-services/ogc-free-maps.ows
https://www.gds-srv.hessen.de/cgi-bin/lika-services/ogc-free-images.ows

Useful layers: he_dtk for topographic maps, he_pg for the map group, he_dop_rgb for colour orthophotos and he_dop_alk_t for orthophotos with cadastral linework. he_alk_t supplies white cadastral linework as an overlay.

WMS and WMTS supply rendered map images or tiles. Their symbols and pixels are background context, not a substitute for an individual boundary-point coordinate and its attributes. Imagery can have a different acquisition date from the point data.

3. Obtain boundary-point geometries and attributes

Prepared point files are the simplest starting point in QGIS. A raw ALKIS WFS requires an additional relationship step: AX_Grenzpunkt contains the marker information, while AX_PunktortTA and AX_PunktortAU supply positions. Adding only AX_Grenzpunkt is therefore insufficient for this service.

  1. In Data Source Manager → WFS / OGC API Features create a WFS connection to the address below. Connect and inspect the available feature types. Do not select OGC API Features for this WFS endpoint.
  2. Start with a small map extent. Request AX_PunktortTA and AX_PunktortAU separately, limited to that extent, with output in EPSG:25832. In manual WFS requests, check the BBOX reference system and its axis order; do not copy latitude/longitude bounds into metre coordinates.
  3. For each position, read istTeilVon and collect the referenced source identifiers. Retrieve those source objects with GetFeature and RESOURCEID in small groups. Retain only AX_Grenzpunkt objects; positions belonging to other survey-point types are not boundary points.
  4. Join the position and source records using the full object identifier, removing only the reference prefix if necessary. In QGIS, Join attributes by field value can join prepared tables with normalized identifier columns. A row number, nearby position or similar label is not a reliable join key.
  5. Save the resulting TA and AU point layers separately as GeoJSON. Copy abmarkung_Marke into a documented marker-code field such as marke_code. Preserve the original identifiers and quality attributes. Never create a missing AU position from a TA position.
https://www.gds.hessen.de/wfs2/aaa-suite/cgi-bin/alkis/sf/wfs?SERVICE=WFS&VERSION=2.0.0&REQUEST=GetCapabilities

These are data-preparation operations, not an automatic QGIS join supplied by connecting the service. If the provider exposes nested references without usable table columns, prepare the linked records with a suitable ALKIS reader or WFS processing workflow first. MapTools provides its own ALKIS position handling for the direct-service route.

In the Fellerdilln extract retrieved on 27 October 2026, the prepared layers contain 19,012 TA positions and 36 AU positions; 1,846 TA positions and seven AU positions are classed as stone markers. These counts describe that extract and its filters, not all boundary points in Hesse.

Survey control points, securing points and AFIS control points are different object types. Keep them in separate layers; a triangle or another point symbol alone does not identify a boundary stone.

4. Filter the markers and assess their positions

  1. Select the required point layer and use Identify Features to inspect a point. In Current layer mode, only the selected layer is queried. Read the point identifier, TA/AU type, marker and quality fields before selecting an export candidate.
  2. For exactly the marker type stone / boundary stone, filter marker code 1110. Code 1140 is a plastic marker and 9500 means no marker. Other stone types have separate codes. Field names and storage types depend on the source.
  3. Prefer an available, uniquely assigned AU position with the appropriate coordinate status for the intended use. Retain TA as a separately labelled map position. Compare only records belonging to the same source object; a difference between TA and AU does not prove a stone moved.
"marke_code" = '1110'

The first expression is for the prepared text field marke_code. For a numeric original field use the expression below; if the original field is text, quote the value instead.

"abmarkung_Marke" = 1110

The prepared boolean field ist_stein covers a broader group of stone codes. The following filter is suitable for that boolean field; it is not equivalent to selecting exactly code 1110.

"ist_stein" = true

According to the HVBG information sheet, TA is the graphical coordinate and AU the official coordinate; official coordinates are used for calculations. GST 2000 means a standard deviation of point position up to 2 cm, GST 2200 up to 6 cm and GST 3200 up to 100 cm. These source attributes do not describe phone reception or guarantee the present physical position of a marker.

5. Export selected points as GPX waypoints

GPX is useful when you need a few independent target points on the phone. It transfers waypoint coordinates and standard descriptive fields; the QGIS map design and the complete ALKIS relationship model are not transferred.

  1. Select only the intended points in the correct TA or AU layer. Use the selection tool or select rows in the attribute table; Identify Features alone does not select a feature for export.
  2. For recognizable waypoints, create text fields named name and desc in an export copy, using the Field Calculator or Refactor fields. Put the point identifier in name and the position type and marker in desc. The examples below use the prepared field names.
  3. Right-click the layer → Export → Save Selected Features As. Choose GPS eXchange Format (GPX) and a new file name. Confirm that only selected features will be saved; exporting an entire large extract is usually unnecessary.
  4. Set the export CRS explicitly to EPSG:4326, WGS 84. QGIS must transform the source geometry from EPSG:25832; merely assigning a different CRS to the original layer would reinterpret its coordinates incorrectly.
  5. In the field selection, retain name and desc and omit unnecessary source fields. Point geometries are exported as waypoints. Do not export the TA/AU comparison lines or a polygon when you want individual targets.
  6. Add the saved file back to QGIS, choosing its waypoints layer. Compare the waypoint count, identifiers and positions with the selected originals. Then transfer the file to the phone and import it in MapTools.

Example Field Calculator expressions for the two standard GPX text fields:

name: to_string("punktkennung")
desc: 'ALKIS | ' || "punktort" || ' | Marke ' || "marke_code"

If extra attribute fields cause an export error, deselect them or enable the GPX_USE_EXTENSIONS creation option. Extensions are less portable: do not assume another app interprets every ALKIS attribute. Keep the original data and its quality information separately.

A GPX waypoint stores latitude in lat and longitude in lon, in degrees. For Fellerdilln, expect approximately 50.8 degrees north and 8.2 degrees east, not UTM metre values around 443,000 and 5,627,000. Reimporting should place the points over their original positions.

Retain the original EPSG:25832 coordinates as source evidence. Changing format or transforming a coordinate does not improve its accuracy, and the phone target remains subject to source and GNSS uncertainty.

Sources and conditions of use

Data provider: HVBG. Check the current access, licence, attribution, download and fee conditions for each product. Public map access does not make every cadastral or AFIS product free. Live requests transmit the requested area to the provider.

Continue: use the points in MapTools and search on site