+hxdimpf Posted January 21 Posted January 21 When working on solving Mysterys, there are two user specific properties of a geocache object that need to be updated by a user on a regular basis: (1) Corrected Coordinates and (2) Personal Cache Notes. Using the existing API methods , two API requests are required to accomplish this, however one API request could be sufficient. This not only improves performance, it also makes better use of the daily quota. Therefore I would like to kindly propose the following method: Geocache Methods -> Upsert User Data /v1/geocaches/{referenceCode}/UserData It can be a PUT or a POST, the payload is structured like this: "userData" : { "foundDate" : "2018......", "correctedCoordinates" : { "latitude" : 41......, "longitude" : 6...... }, "isFavorited" : false, "note" : "AB=27\nCDE=120\nN41 33.333 E06 11.111", "watched" : false, "ignored" : false } It may not be possible to upsert foundDate, isFavorited, watched, and ignored but "correctedCoordinates: and "note" clearly make sense. So in essence the minimal payload would be: "userData" : { "correctedCoordinates" : { "latitude" : 41....., "longitude" : 6.... }, "note" : "AB=27\n2CDE=120\nN41 11.111 E06 22.222", } please consider adding this method. P.S. This would also complement the Setter / Getter paradigm since it is now possible to do a GET and specify &fields=userData which would yield exactly that structure. Now with the method I am proposing we would have a symmetrical way of Getting and Setting user specific properties of a geocache object. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.