Open following5 opened 6 years ago
I think we could also allow full access to log entries for the log authors (e.g. via services/logs/userlogs).
Add a
status2
field for geocaches, which supports all the new status.
Better: Add a boolean parameter, which enables the retrieval of nonpublic caches; then no new status field is needed. Otherwise existing apps would treat non-public caches like public caches, which could lead to logical errors.
But a status2
parameter will be needed in the searching methods.
@following5, please explain to me: why we can't just extend the list values of current status field + add bool. switch which enable this wider list. Then we don't need additional status2 which can be a little confusing...
I was thinking of the size/size2 search options, and of backward compatibility to old OKAPI installations (currently OC.US and OC.DE) which will throw a HTTP 400 error when searching for unknown statuses.
But size/size2 is another issue (different parameter formats), and status2
also would throw an error on old installations. Better: Add a statuses
field to services/caches/capabilities, which returns a list of statuses that can be searched for.
Better: Add a statuses field to services/caches/capabilities
done
Note: For OCDE "Locked" caches, the old "XML Interface" API does not expose coordinates; it gives 0/0 coords instead. Maybe we should do the same in OKAPI (or return a null
location).
Could this be related to the fact that not-published caches cannot be visible on the map at this time? see also https://github.com/opencaching/opencaching-pl/issues/602
Yes.
Please fix, f.e. all mo-caches Seem Go be still available in c:Geo, even after Update, although Archived/locked
This is low prio, as long there are no OKAPI methods for preparing new caches (e.g. #440) or for OC admin functions.
Generally, current OKAPI versions do not allow to access nonpublic (unpublished, blocked etc.) and semipublic (OCDE locked) caches. There are a few exceptions, not intentionally but by accident:
There would be no point in protecting that, because it all is allowed (for the log authors) on the OC websites.
Implementation idea for full owner access:
status2
field for geocaches, which supports all the new status.