CFGeoRIoT

Context

Field devices are easy to lose track of. A fleet manager needs to know, without digging through spreadsheets, which devices are actually reporting, where a given unit is right now, how its usage has trended, and who’s allowed to see which customer’s devices.

What I built

A backend exposes the transmitted data, with policy-based authorization at every level, so group administrators see only their own fleet while super administrators see everything. Device positions are stored as native MySQL spatial columns; monthly reports run real spatial SQL server-side — convex hulls and bounding boxes — to compute each device’s coverage area, rather than shipping raw coordinates to the client. From the dashboard, you can access the device/user directory, per-device rotation charts linked to a map, and geographic reports rendered as polygons over Google Maps (in this particular case, the measurements corresponded to multiples of the engine’s revolutions).