What we’re shipping. What you’re querying.
Notes from building and running a Wialon extraction in production: where the platform’s API limits actually bite, why a daily row needs a timezone before it means anything, and what becomes answerable once the data sits in a database you can join against. Written for the people who will run the queries.
If you are weighing this up rather than reading for interest, the shorter route is how this compares with Wialon’s own reports and the tables you would be querying.
What lands in a PostgreSQL copy of your Wialon fleet
The tables FleetSQL writes into your database — units, trips, speedings, fuel and EV events, your own Wialon reports — and the queries they answer.
Who drove it before the tracker went offline?
A Wialon integrator needed the last driver of every unit that stopped reporting. Three ways to get it: reports and Excel, FleetTAB, or SQL.
Wialon data extraction: working within the limits
How to pull years of fleet history out of Wialon Hosting without hitting its rate limits, concurrency caps, or report timeouts.
Why and how to extract your Wialon fleet data
Four reasons to get telematics data out of Wialon — and three ways to do it: by hand, a custom ETL pipeline, or FleetSQL straight to PostgreSQL.
No posts in this category yet.