About this plugin
TrailsIQ lets you import GPX files to create trail records with calculated stats (distance, elevation gain, grade). Trails are displayed on interactive MapLibre maps with difficulty styling. Includes a maintenance reporting system for trail crews.
Features:
* Import GPX files and auto-calculate distance, elevation gain, and grade
* Interactive MapLibre GL map with outdoor, satellite, and topo styles
* Trail network management (group trails into networks)
* Maintenance issue reporting with GPS location and photo upload
* Admin dashboard with maintenance status overview
* Frontend shortcodes for maps and maintenance reporting
External Services
This plugin connects to the following external services. By using this plugin you agree to each service’s terms of use and privacy policy.
TrailsIQ central registry (app.trailsiq.com)
com so that public reporters using the TrailsIQ Report mobile app and crew members using the TrailsIQ Field mobile app can find your trails and route reports back to your site. The connection is opt-in: the registry only contacts your site after a site administrator pastes a registry token in the Registry settings page (TrailsIQ → Registry).
com:
- On manual or scheduled sync (every 24 hours by default): a simplified copy of your public trails — id, name, slug, status, difficulty, color, organisation id, and a Douglas-Peucker-simplified polyline (~50 m tolerance) — is pushed to the registry so the mobile apps can show “trails near me” and route reports back. Private/draft/archived trails are never sent.
- When a public report is filed against one of your trails through the central app, app.trailsiq.com forwards the report (title, description, optional reporter name, lat/lng, photos) to your site’s REST API; the report is stored on your server and is never retained by app.trailsiq.com.
- When a Field App user signs in with their WordPress credentials, app.trailsiq.com proxies API requests (issues, structures, points of interest, time logs, photos) between the app and your site; the central server does not retain the response payloads — it only forwards them.
- A registry token (random string generated on app.trailsiq.com), the bearer-token hash for any active Field App session on your site, and per-request HTTP timing metadata are kept on app.trailsiq.com to authenticate the proxy traffic.
The registry connection can be removed at any time from TrailsIQ → Registry → Disconnect; trails already pushed remain in the registry until the next sync (which sends an empty list) or until the central operator removes the install.
- Service: https://app.trailsiq.com
- Terms of use: https://trailsiq.com/terms
- Privacy policy: https://trailsiq.com/privacy
MapTiler
Map tiles, styles (Outdoor, Satellite, Topo), and terrain data are loaded from MapTiler’s servers using your MapTiler API key. Map tile requests include your API key and the coordinates of the map viewport.
- Service: https://www.maptiler.com
- Terms of use: https://www.maptiler.com/terms/
- Privacy policy: https://www.maptiler.com/privacy-policy/
Open-Meteo
The Weather & Soil Status module fetches soil moisture, soil temperature, and precipitation forecasts for each network’s centroid coordinates from Open-Meteo’s free public API. No API key is required and no personally identifying information is sent — only the latitude/longitude of the network being polled.
- Service: https://open-meteo.com
- Terms of use: https://open-meteo.com/en/terms
- Privacy policy: https://open-meteo.com/en/privacy-policy
MapLibre GL JS
1).
- Source: https://github.com/maplibre/maplibre-gl-js
- License: BSD-3-Clause
Turf.js
The geospatial analysis library (used for GPS trail snapping) is loaded from the jsDelivr CDN.
- Service: https://www.jsdelivr.com
- Library: https://cdn.jsdelivr.net/npm/@turf/turf@6/turf.min.js
- Privacy policy: https://www.jsdelivr.com/privacy-policy-jsdelivr-net