Opened 7 years ago

Last modified 7 years ago

#4054 new enhancement

Request for a way of restricting the trackpoints API call to a single user

Reported by: SomeoneElse Owned by: rails-dev@…
Priority: minor Milestone:
Component: api Version:
Keywords: Cc:

Description

(this came out of a discussion on IRC - anyone actually familar with the API feel free to have a laugh and then correct this to say what I actually meant it to)

From a user perspective, the problem is "there's no equivalent to G (capital G) in Potlatch 1". In P1 "g" loads all traces in the current bbox (well, most recent ones first) and "G" is similar but for my traces.

As I understand it* the problem is that the track_points_ call isn't possible to be restricted to the current user.

*from reading an IRC message from RichardF.

Change History (2)

comment:1 Changed 7 years ago by SomeoneElse

A workaround for this in P2 itself might be to have a way of loading the last N ways for a user (where N is small enough not to overload the API) loading them in reverse ID order.

This wouldn't restrict to a BBOX of course, but in the absence of an external change would provide nearly the same functionality.

comment:2 Changed 7 years ago by TomH

  • Summary changed from There's no way for Potlatch2 to easily obtain all of a user's GPX traces within a BBOX to Request for a way of restricting the trackpoints API call to a single user

Potlatch 2 is red herring - this is really just a request for a way to limit the trackpoints API call to only returning a single user's trackpoints.

As a note to anybody thinking about implementing this I would point out there are serious performance issues that need to be considered as each point has to be joined to the files table to find out who uploaded it.

Note: See TracTickets for help on using tickets.