Rub21 left a comment (openstreetmap/openstreetmap-website#7089)
### Proposal: keep only two levels
My first idea was to keep `public` and `identifiable`, with unordered and
ordered points in the API. But in the last ops meeting @tomhughes suggested
keeping `trackable` and `identifiable`.
This sounds much better and looks reasonable to me, because it also fixes the
pagination problem: with no more unordered points, the trackpoints query drops
the [`UNION
ALL`](https://github.com/openstreetmap/openstreetmap-website/blob/de04e98147b904b7e79020d5aa7b0f9c3057f040/app/controllers/api/tracepoints_controller.rb#L35-L37)
and pagination becomes much more efficient.
With this proposal we could end up with two visibility options:
| Level | Listed at `/traces` | File downloadable | Points in API |
|---|---|---|---|
| `trackable` | No | No | Yes, anonymous but ordered with timestamps |
| `identifiable` | Yes | Yes | Yes, with user and timestamps |
The real question for us and the community is: **Do we still need to keep
unordered points in the API?**
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/7089#issuecomment-4461840083
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/issues/7089/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
