GCDroid V2.0.0 has been release to the play store
GCDroid V2.0.0 steht im Google Play Store zur verfuegung!
Welcome to GCDroid - create topics and leave suggestions for new feature
Willkommen zu GCDroid - erstelle Themen und hinterlasse Vorschläge für neue Funktionen
A common use case (for me) is this:
A group of geocachers are out on a trip. They have a pre-compiled GPX file created via Project-GC or Geocaching.com. This contains all geocaches that they want to log during the trip. I myself might have an agenda of my own as well. That agenda might include geocaches that I would like to log, but aren't too important to the others. A new D/T combo for myself, a challenge, or something that others has already logged. If we are passing close enough to them it might be worth the extra stop.
This is why I would like to be able to use more than one offline database simultaneously. I can then have the "group list" enabled, and also at the same time see for example "my own needed D/T".
I would like the cache icons to have some form of indicator showing that they are from different lists, so that I can easily see which ones are the groups main goal. It could be color coding by adding circles around the cache icons or a small number in a corner.
In my opinion, 3-5 simultaneous lists should be enough. The first one selected of them is the most important to visually stick out from the others.
Wenn ein Link zu einem Cache angewählt wird (E-Mail, Messenger ...) die Datenbank zum Import auswählbar machen.
Neongeo had a very nice feature. One could create waypoints that are completely independent from geocaches.
An example use case is when planning to place new geocaches. Easy way to save notes on a map where I can see circles around other geocaches (and the distance to them when clicking them).
An option to export these extra waypoints in CSV form or similar would be sexy, but definitely not a requirement to make it useful.
So phase one done :-)
Here what will be released in the next RC beta.
All new waypoints will be added from map. All waypoints will be added as 'dummy caches' with an '!' as icon.
Before the waypoint is created a name can be given.
a) averaging, which will allow start/stop of averaging and once stopped the avg location will be used to create new 'cache'.
b) waypoint from map, a crosshair will show in the center of the screen and you can move the map around. whatever is under the crosshair will be the location used.
Currently no special icons can be used! Since waypoints need a parent cache to work I made these waypoints 'dummy caches'. And icons for caches are definded by type. Long story short, no custom icons. Maybe in the future....
For now I consider it done. Will come in next RC beta. Maybe tonight, maybe this weekend.
I geocache quite a lot in other countries, mostly in Denmark and Germany, besides my home country Sweden then. Since I don't really speak German there is a lot of guessing and translations. The flow today is to "open in browser" from the app, if lucky, Chrome suggests to translate. If not, I have to mark the blob, copy that, paste into the Translate app and then finally I am where I want to be.
Therefore I propose to add an option to (Google) translate the cache description and log texts. C:geo has this feature. I would be happy enough with 1-2 clicks for cache description and 1-2 clicks per log entry.
I assume Google Translate is free to use for Android apps just like Google Maps is.
Es wäre super hilfreich wenn man einen Annäherungsalarm einstellen könnte.
Bei x Meter bis zum Wegpunkt einmal Piepen zum Beispiel. Dann muss man nicht ständig aufs Handy schauen und man läuft nicht mehr zu weit wenn man Mal kurz das Handy wegsteckt um die Natur zu genießen.
Store the geocachers position every minute or so and show as a trail on the map, with small dots. Probably only store the last hour. This should be something that can be turned on/off directly from the Map.
Most Garmin users I know uses the track feature in those GPS devices, and I know I did myself back in the days. I used it when using Neongeo as well.
This idea is 100% inspired by Garmin and Neongeo (obsolete app).
OK, so I have an implementation... couple questions...
How many 'datapoints' are a good value? currently sampling every 1s if distance is at least 1m.
3600 points/h. So 10000 points are about 3h.
How much tracking history is useful?
I guess there should be some limit.
What about opening/closing the map? I assume I would need to remember the track.
What about screen locked? Keep tracking? For how long? -> currently not tracking. would impact battery!
Many things to consider.
What does the author think? Or anyone that voted?
Customer support service by UserEcho