Problem
The /api/eud response includes a last_point field, but in current builds it always returns null. To get the latest known position for each EUD, clients must issue a separate /api/point?uid=… request per EUD (or a bulk /api/point query and dedupe client-side). Both patterns multiply round-trips for what should be a single call.
Proposal
Populate last_point with the EUD's most recent point row (same shape as /api/point results) when the field is present in the schema. Optionally, expose a query param like include=last_point to keep responses lean for clients that don't need it.
Why
Collapses EUD discovery + position fetch into a single HTTP request. For clients implementing offline catchup against OTS, this is the difference between O(1) and O(N) round-trips on every reconnect.
Problem
The
/api/eudresponse includes alast_pointfield, but in current builds it always returnsnull. To get the latest known position for each EUD, clients must issue a separate/api/point?uid=…request per EUD (or a bulk/api/pointquery and dedupe client-side). Both patterns multiply round-trips for what should be a single call.Proposal
Populate
last_pointwith the EUD's most recent point row (same shape as/api/pointresults) when the field is present in the schema. Optionally, expose a query param likeinclude=last_pointto keep responses lean for clients that don't need it.Why
Collapses EUD discovery + position fetch into a single HTTP request. For clients implementing offline catchup against OTS, this is the difference between O(1) and O(N) round-trips on every reconnect.