GeOrg version 1.1.7.4
Another bugfix. If you encountered sporadic inconsistent behaviour between different pages of the app (varying Found-Count, locationprovider, etc.), this bugfix is for you 🙂
Back to working on the next feature release – Happy caching!
GeOrg version 1.1.7.3
This bugfix release contains some smaller fixes for the Field Note-system, especially the Found Count. Also, GeOrg now recognizes your timezone correctly and uses that in the Field Note-export. Make sure you use the same timezone in your Groundspeak profile or else your Field Notes might suffer from jet-lag 😉
Happy caching!
GeOrg version 1.1.7.2
GeOrg 1.1.7.2 is ready and has just been uploaded to the Android Market. Please find the detailed list of changes and fixes is available in the Changelog. The most relevant changes are:
- Field Notes:
The main effort for this release has gone into providing a Field Note-System that not only lets you mark caches as found/dnf, but also tracks the time of the found and saves optional comments, you might want to enter. Later you can export all your Field Notes from a separate menu to your SD-card or as an email-attachment (the latter requiring Android 2.0+) and upload them to Groundspeak to complete your logs.
A more detailed description of the process will be added to the manual soon.
- GPS-compass:
Some of you have asked for switching between the magnetic and the gps-compass. The gps-compass takes its data from the gps-provider. Whenever you are moving, the gps-provider tracks your heading and this is, what is used in the compass. You can configure a threshold speed – below that speed, the magnetic compass is used, above it, the gps-compass kicks in.This feature might make sense for you, if you want to use GeOrg in your car or if you are unsatisfied with the performance of the magnetic compass in your device. Be aware that the gps-compass can only provide useful data when you are moving. If you are standing still (and have configured the threshold to 0 km/h or mph) it won’t work.
- Fast scroll CacheDB:
In bigger CacheDBs, scrolling used to take some time. With the fast scrollbar, you can nearly instantly reach the bottom of your 2K CacheDB.
The next release will still be a 1.1.7.x-version and will contain extended connector-support and more solvers. Stay tuned 🙂
Have fun with the new release and please contact us if you have any problems or feature requests.
GeOrg version 1.1.7.1
This update contains fixes for several smaller issues, some of you were having with 1.1.7. For a detailed list of fixed bugs, please visit the changelog.
Happy GeOrg-Caching 😉
GeOrg version 1.1.7
We just released GeOrg 1.1.7 on the Android Market. As always, the detailed list of changes and fixes is available in the Changelog. These are the main features in this release, tough:
- Additional Waypoints:
You can now add/edit/delete your own additional waypoints. Additional waypoints imported via GPX are unchangeable, but you can duplicate them to make changes to the duplicate. Also you can switch association of waypoints from one cache to another and even make them global waypoints. - Day-Theme:
GeOrg now supports a black-on-white “day-theme”, so you can better read the display in the sun. You can change the current theme in the display-settings. There’s also an “Auto”-setting that make GeOrg switch between the night- and the day-theme when the sun sets/rises. (please note, that due to an android bug the Settings-Page always remains white-on-black in android-versions > 1.6) - Sat-Status-View:
The sat-status-display has gotten a graphical overhaul. If you prefer the old (x/y)-display you can revert to that in the Settings. - Directional icon:
Like what you are used to from geocaching.com – you’ll find a small compass display next to most distances now that gives you an idea as to in what direction a waypoint is in. - Create waypoint on map:
In the Positions-menu in the map you can now enter a mode where you can create a waypoint by touching the map at the position you want the waypoint to be created at. - SunMoon-Solver:
Tells you when the Sun and the Moon rise/set, where they are, how far they are and other geek-stuff. Useful for example if you want to find out when to meet for a night-cache (civil-dusk would probably be a good time)
The next things we’ll work on are Filters and Field Notes. Happy caching with GeOrg 1.1.7 and as always: contact us if you have any problems or feature requests.
GeOrg version 1.1.6.6
Another bugfix for the current release. With 1.1.6 you got the ability to enter comments for geocaches. We have now been made aware of the fact that these comments get deleted, whenever you re-import that geocache, either with a connector of by importing any GPX that contains that geocache. That was not the intended behaviour and it’s fixed with 1.1.6.6.
We are sorry for any inconveniences this might have caused you 🙁
Ok – back to working on 1.1.7 – Happy caching!
GeOrg version 1.1.6.5
Another update for 1.1.6 while we are still working on 1.1.7.
We have had a report about problems when selecting caches on the map on a Nexus One device: In many cases the detail-bubble would point to the wrong cache, making it hard to select the right one. This update should fix this issue. Also deactivating the screensaver for compass & map previously didn’t work for OpenStreetMaps. And … finally, trying to import a zip with no GPX-files or a whole directory without GPX-files shouldn’t cause crashes anymore.
Happy caching! 🙂
A new connector in town: BCaching
A few days ago a new connector for GeOrg has been published in the Android Market. It was written by the owner of www.BCaching.com. With this connector you can access data from your Groundspeak PocketQueries housed at BCaching without importing large gpx-files into GeOrg. Instead, GeOrg displays caches on the Map-Page and within the Find Neaby-Page live from BCaching.
Now, that sounds nearly like what people are doing with the offical Groundspeak iPhone-App all the time. What’s BCaching anyway and is it legal?
First of all, it IS legal. BCaching is operating with Groundspeaks consent. Also, only premium members get to use its features, because you have to define Pocket Queries before getting at any live data at all. That out of the way, this is how it works:
- First you create an account at www.BCaching.com (it’s free)
- Then you initially upload one “My Finds” Pocket Query to bcaching.com
- After that your account is established and you can upload other Pocket Queries. You can also set up your Pocket Queries to be sent directly to your mail-account at BCaching so that BCaching always has the latest information from your Pocket Queries.
You can now access your Pocket Query-data at www.bcaching.com on your computer, from any mobile device via a slim and fast mobile browser-optimized version of the site or – and that’s the news – directly from GeOrg.
Whenever you find a cache you want to do (on the Map-Page or the Find Nearby-Page with the BCaching-Connector configured and enabled), you can choose to download that cache to your CacheDB. If you set up your Pocket Query to automatically update the BCaching-database, you’ll get fresh new information while keeping your CacheDB small and fast.
Also information in the BCaching-database accumulates! You can cover a vast area with Pocket Queries by defining several to run on different days of the week – overcoming the PQ/day-limit and avoiding continually importing all those huge heaps of data.
You can find some more information about BCaching at their site. Expect to see some additional features in GeOrg targeted at the BCaching- and the Opencaching.de-connectors in the future.
Happy caching! 🙂
GeOrg version 1.1.6.4
Just another small bugfix-update for two crashes you reported via mail and one that I found when implementing the new SunMoon-Solver for 1.1.7. Seems like nobody has ever tried to create a waypoint north or south of the 60th parallel. Only traditional caches there? 😉
The fixes are listed in the changelog.
Happy caching! 🙂
GeOrg version 1.1.6.3
Some of you have reported crashes which should be fixed with this small update. Also, GCVote is working again. The fixes are listed in the changelog.
Happy caching! 🙂
