Skip to content

GPS Tracking & Field Collection

GeoLibre has two tools for work in the field, both on the Controls menu:

  • GPS Tracking... streams a live position onto the map, records a track log, and captures points where you stand.
  • Field Collection... captures point, line, or polygon observations against a form you define, with optional photos.

Both write ordinary GeoJSON layers, so everything they capture is saved with the project, shows up in the attribute table, and exports through the usual Layer actions → Export formats. Neither has a server sync or upload step: captures live in the project until you save or export it.

GPS Tracking

Controls → GPS Tracking... opens the GPS Tracking dialog.

Position source

Pick one entry under Position source:

  • This device uses the browser or operating system's location service with high accuracy requested. In the Android and iOS apps the OS asks for location permission the first time. If permission is refused the dialog says so; allow location for the site (browser) or app (system settings) and press Start GPS again.
  • NMEA receiver (serial or Bluetooth) reads an external GPS/GNSS receiver. Choose a Baud rate (4800, 9600, 19200, 38400, 57600, or 115200; 9600 by default, and remembered), then Connect serial or Connect Bluetooth. Once connected the dialog shows the device and a running count such as 1,204 sentences · 300 fixes with the current fix quality (for example RTK fixed, RTK float, Differential GPS). Disconnect releases the receiver.

GeoLibre parses the GGA, RMC, VTG, GSA, and GST sentences from any talker (GP, GN, GL, …). Accuracy comes from GST when the receiver sends it; otherwise it is estimated from HDOP.

NMEA needs a Chromium browser

The receiver is read through the Web Serial and Web Bluetooth APIs, which Chrome and Edge provide and Firefox and Safari do not. Most Bluetooth GPS receivers use classic Bluetooth: pair those in your operating system's settings and connect them as a serial port. Connect Bluetooth is for Bluetooth Low Energy receivers only.

Bluetooth receivers in the Android app

The Android app's WebView has neither API, so it reads the receiver natively instead. Pair the receiver in Android's Bluetooth settings, then pick it from Paired receiver and press Connect receiver. Android asks for the Nearby devices permission the first time. The app talks to the receiver over classic Bluetooth (Serial Port Profile), which is what most survey GNSS receivers use; Bluetooth Low Energy-only devices are listed but cannot be connected.

RTK corrections (NTRIP)

In the Android app, once a Bluetooth receiver is connected, the dialog shows RTK corrections (NTRIP). Enter the Caster host, Port (2101 by default), Mountpoint, and your Username and Password from the correction provider, tick Use TLS if the caster requires it, and press Start corrections. GeoLibre connects to the caster, sends the receiver its RTCM corrections over the same Bluetooth link, and sends the caster the receiver's own position (GGA) every 10 seconds, which network (VRS) casters need before they start streaming. The status line counts the corrections received, and the receiver readout above it shows the fix moving to RTK float and RTK fixed.

A pasted caster URL such as http://caster.example.com:2102/ is split into host and port, and a leading / is dropped from the mountpoint. If the caster drops the stream, GeoLibre reconnects every few seconds; a rejected login or an unknown mountpoint stops it with a message instead. The settings, including the password, are saved on the device, and corrections restart on their own the next time the receiver connects, until you press Stop corrections.

The web version cannot run an NTRIP client: a browser page cannot open the plain TCP connection a caster speaks.

Following your position

Start GPS begins streaming. The map shows a blue dot, a heading arrow when a heading is reported, and a translucent circle for the reported accuracy. The readout lists the accuracy (±4 m), Satellites, altitude, speed in km/h, and heading in degrees.

Keep map centered on my position (on by default) recenters the map on each fix. Dragging the map turns it off.

When you close the dialog while GPS is running, a small floating panel stays in the bottom corner of the map with the coordinates, accuracy, satellites, speed, the track statistics, Capture point, a follow toggle, Pause/Resume, and a button that reopens the dialog.

Recording a track

Under Track log:

  1. Record track clears any previous unsaved track and starts recording, turning GPS on if needed.
  2. Pause stops logging; Resume continues in a new segment, so a gap is not drawn as a straight line.
  3. While a track exists the dialog shows its point count, distance, and duration, with four actions:
    • Save as layer adds the track to the project as a line layer named like GPS Track 2026-10-04 0930 (a MultiLineString when it has several segments), keeping each vertex's time, accuracy, and satellite count.
    • Export GPX writes GPX 1.1, one <trkseg> per segment.
    • Export GeoJSON writes the same track as GeoJSON.
    • Discard throws the track away.

Saving and exporting need at least two points.

Unsaved tracks are not kept

A track lives only in memory until you press Save as layer or export it. Closing the app or reloading the page loses an unsaved track.

Capturing points

Capture point under Digitize adds a point at the current fix to a layer named GPS Points, creating it on first use. Each point records time, accuracy_m, satellites_used, ele, speed_mps, and heading_deg. To capture into a layer of your choice, with a form, use Field Collection instead.

Logging filters

Filter Effect
Min distance (m) Skip track fixes closer than this to the previous one.
Min time (s) Skip track fixes sooner than this after the previous one.
Max accuracy (m) Do not log fixes less accurate than this, and block Capture point while the fix is worse.

Each is off at 0. The filters are remembered between sessions.

Field Collection

Controls → Field Collection... captures observations into a collection layer against a custom form.

Set up a collection layer

  1. Under Collection layer, pick an existing collection layer or New collection layer….
  2. For a new layer, enter a Layer name and pick a Geometry: Point, Line, or Polygon. A layer holds one geometry type.
  3. Add field for each attribute. Give it a Label, a Type (Text, Number, Date, or Choice), tick Required if it must be filled, and for a Choice field list the Options (comma-separated).
  4. Create layer.

A layer with no fields captures location-only observations. Property names are derived from the labels.

If the layer has an attribute form configured, Field Collection uses it instead of the plain field list: its aliases, dropdowns and checkboxes, number, range and date widgets, conditional visibility, constraints, and default values all apply.

A QGIS or QField project brings its forms with it: after importing the project, every layer that has a form is already a collection layer, with nothing to set up here.

Linked records and photos

A project imported from QGIS or QField can link layers together: several reviews, samples or photos that belong to one point. In GeoLibre the linked layer is usually a table layer (records with no location of their own).

  1. Capture and save the point as usual.
  2. Under the confirmation, Add to layer appears for each layer that links to the one you just saved into. Choose it.
  3. The form of the linked layer opens with the link to your point already filled in. There is no location to pick. Fill it in and Save record.
  4. The form stays on the linked layer with the same link, so you can add the next record (a second photo) straight away. Switch the Collection layer back to carry on with points.

You can also pick a table layer as the Collection layer yourself and choose the record it belongs to from the dropdown, which lists the parent layer's current features.

A field set up as a Photo in the attribute form (a QGIS Attachment widget, or the Photo edit widget chosen in the Style panel) shows Choose photo… instead of a text box. The picture is stored in that field, travels with the project, and shows as a thumbnail in popups and the attribute table. Each picture can be up to 2 MB.

Default values

A field's Default value in the attribute form is an expression that fills the field as soon as you capture a location. It uses QGIS expression syntax, so defaults written for QGIS or QField work unchanged:

Default value Fills in
uuid() A unique ID. uuid('WithoutBraces') drops the braces.
now() The date and time (the date alone for a Date widget).
concat("site", '_', format_date(now(), 'yyyyMMdd_HHmmss'), '.jpg') A name built from other fields. The \|\| operator works too.
@position_horizontal_accuracy The GPS accuracy in meters.
x(@position_coordinate), y(@position_coordinate), z(@position_coordinate) The GPS longitude, latitude and altitude.
x(transform(@position_coordinate, 'EPSG:4326', 'EPSG:2056')) A projected coordinate, for any EPSG code GeoLibre knows.
@position_number_of_used_satellites Satellites used, when the receiver reports it.
@user_full_name Your editor name.

The @position_... variables (and QField's older @gnss_... spellings) are set only when the location came from Use GPS. For a point picked on the map they are empty, so @position_coordinate is not null records whether a point was measured or placed by hand. $x and $y give the captured point itself either way.

A filled-in value is a starting point: type over it and your value is kept. Until you do, it follows the capture, so repositioning the point refreshes it, and a default built from other fields updates as you fill those in. Text functions (upper, lower, trim, left, right, substr, replace, lpad, rpad, concat, length), number functions (round, floor, ceil, abs, min, max), coalesce, if, and CASE WHEN are available. Aggregates and lookups into other layers (aggregate, get_feature) are not.

Capture an observation

For a point:

  • Use GPS takes a single high-accuracy fix from this device (up to 15 seconds). It does not read the NMEA receiver connected in GPS Tracking.
  • Pick on map places the point where you click; Esc cancels.
  • Reposition point moves a point you have already placed.

For a line or polygon, Draw on map opens a toolbar along the bottom of the map. Click to add vertices, or Add GPS vertex to add one at your current position; Undo removes the last vertex, and Finish (or a double-click) closes the shape once it has enough vertices.

Fill in the form, attach photos if you like, and press Save point, Save line, or Save polygon. Required fields are marked *, and the form refuses an empty required field, a non-numeric number, or a choice outside the listed options.

Photo (optional) → Choose photo… attaches one or more images, up to 2 MB each. Photos are stored on the feature, so they travel with the project.

Session behavior

Done ends the collection session. Closing the dialog with the X button or Esc only hides it: an Open Field Collection pill stays on the map so you can capture the next observation without setting up again.

The GPS accuracy shown while collecting is for your information and is not stored on the feature. If you need per-point accuracy and satellite counts, use Capture point in GPS Tracking.

Working offline

Captures are kept in the project, so collecting needs no connection once the app is loaded. Cache the basemap for the area before you go with Project → Offline Basemap..., and save the project before closing the app.