GeoPulse
GeoPulse is a self-hosted location tracking and visualization platform.
Setup
- Install GeoPulse - follow the GeoPulse documentation
- Add a Colota location source in GeoPulse under Location Sources
- Set a username and password for the Colota source
- Configure Colota:
- Go to Settings > API Settings
- Select the GeoPulse template
- Set your endpoint:
https://geopulse.yourdomain.com/api/colota - Go to Settings > Authentication
- Enable Basic Auth and enter the username and password from step 3
Payload Format
The GeoPulse template uses Colota's default field names with no custom fields:
{
"lat": 51.495065,
"lon": -0.043945,
"acc": 12,
"alt": 519,
"vel": 0,
"batt": 85,
"bs": 2,
"tst": 1704067200,
"bear": 180.5
}
Field Mapping
| Colota Field | GeoPulse Field | Description |
|---|---|---|
lat | lat | Latitude |
lon | lon | Longitude |
acc | acc | GPS accuracy (meters) |
alt | alt | Altitude (meters) |
vel | vel | Speed (m/s) |
batt | batt | Battery level (0-100) |
bs | bs | Battery status |
tst | tst | Unix timestamp |
bear | bear | Bearing (degrees) |
Geofence Compatibility
GeoPulse needs multiple points clustered at your arrival location to confirm a trip has ended there - a single point is indistinguishable from a brief stop at a traffic light. Colota handles this automatically: when you enter a pause zone, it keeps logging real GPS points for 3.5× your tracking interval before pausing, producing several arrival points for GeoPulse to finalize trip arrival.
Note: GeoPulse also supports OwnTracks as a location source. If you prefer, you can use the OwnTracks template with the endpoint https://geopulse.yourdomain.com/api/owntracks instead.