Geocaching Australia Development List

From GeoWiki
Revision as of 17:22, 18 October 2018 by Caughtatwork (talk | contribs)
Jump to: navigation, search

This page lists the development ideas for Geocaching Australia. If you want something added to this list, please post your request in the forum.

For changes to the Wiki, see the Wiki Development List.


Where are we heading?

Work in Progress by your developers


Priority set by the GCA Senate:

  • Mid 2019 game (game decided, development in progress)
  • Finish quiz aka FAQ code and administration (image load)


  • OAuth integration to enable site to work with many more mobile applications
  • Forum Upgrade
  • Solr integration and improved map/search performance
  • Add status checkboxes to stats graphs to be able to include for cache status example Hide by Type -> check box for 'show archived' and 'show disabled'

Work on Backlog by your developers


  • Use output of a my query as a restriction list in Geocaching graphs:- Would it be possible to get stats on just the caches returned from a query? (think along the lines of setting a query in GSAK and then running FindStatGen) But this could be extended beyond just found caches. Could be used to answer questions along the lines of, of the caches in the zone x which has the most finds?, what percentage of SA's caches are micros?, In which month were the most events held?, Of the caches hidden by x and found by me what percentage are puzzles?, and so on...
  • Add other described items, crafting and reading to dragonZone
  • Enhance API for access to dragonZone capabilities

Laighside Legends

  • Create map of archived caches by lat and lon search
  • Enhance map so that retrieved caches are not removed from the map as you pan around, but new ones are added.

Work Recently Delivered by your primary developers



  • Code cleanup after responsive code changes for mobile devices (sidebars)


  • Add the ability to select between daily or weekly update emails.
  • Create "postcode" cipher for toolbox.
  • Make trophy layout more responsive by having trophy groups toggle on or off.


  • Add the ability have corrected co-ordinates for any geocache. Private only, available everywhere a set of co-ordinates is used. Could be used with a "GeoArt" cache type to display the cache on the map in the art work, but in GPX files as corrected co-ords to navigate to (delivered and in BETA test): - * Custom list of waypoints - Solved a few puzzles? Place em here so they come up on YOUR map - perhaps link to cache - viewable by user only.


  • Add the ability to set bulk GPX files to only download the last 20 logs instead of all as a default. Default can be overridden on a My Query basis and will not apply to GPX files from a cache page.


  • Upload of MP3 files for podcaches Album


  • Investigate an alternative to nominatim for geocoding locale
  • Add a filter and pagination to the GCA Gallery page
  • Add image rotation service to gallery
  • Change the drop shadow to use css classes and non-fixed image widths to allow for more responsive design opportunities.


  • Add graphs for dZ and GCA well rounded cacher (In fact all of the cacher graphs that logically can have a separation between ALL, GCA and dZ Only have all been prepared)
  • 2018 end of year game development and testing

Work Recently Delivered by your primary developers

Laighside Legends


  • Add geonames as the primary source of elevation data to improve response times when logging caches, but retain OSM and Google as backups in the event of the geonames service being removed or throttled


  • Create list of archived caches by lat and lon search


  • Investigate Create a Geocache page for speed and optimisation improvements.
  • When changing co-ords on the Search for a Geocache (Home or Current Location) box on the home page, update the query string for the map.
  • Finalise conversion of raster images into vectors
  • Upgrade forum software to cater for php7 upgrades
  • Reconfigure user tables to decouple from forum tables
  • Rewrite all cache interactions as a single class
  • Develop log interactions into a single class
  • Enhance header to cater for responsive design and ads and competition banners
  • Fix bounce handler
  • I have recently started researching locationless caches and I frustration I found quite early on is that there are a fair number that aren't technically locationless. I'd love it if these type of locationless could have the state you need to be in to complete them added to the attributes. This way I would stop looking at the Queensland bus one, for example. . There need to be other ways to work out what locationless caches are about, so a text search needs to be allowed, or tagging to categorise them. I'd be looking for a whole of solution approach to locationless cache rather than piecemeal. Tag locationless caches
  • NFC caches
  • Add EPE to cache submission so finder can see how accurate the previous recording was. How to output in GPX file?
  • For My Queries when you use a ZONE ID to restrict the caches archived caches are excluded due to the function that gets caches from the zone. Include archived caches is they are wanted.
  • Downloadable hotlists (csv, gpx etc) e.g :
  • Bulk/batch upload of logs - Have server notify you after it's all updated and processed.
  • Improve Tag and Gallery visualisation
  • Administrative Pages for Tags and Gallery, plus some stat generation
  • Add a notification bar to the header to allow notification of save/edit/addition rather than a blank page with a 'return to what you were doing' link
  • Meetup Events to facilitate group caching (to plan best date and area/geocaches)
  • Add state to to restrict caches to a stated state, even if it's inside the radius selected. i.e. Stops Tasmanian caches showing up in Victorian alerts. Trouble will occur for non-Australia cachers when their state won't be selectable. Want to try and keep the site as international as possible.
  • Add ability for "NOT=Tag" in My Query function so as to ignore things like cache race entrants.
  • Add functionality to alerts to stop alerts on moveables if already found. Should be able to make this user by user selection, but not cache by cache.
  • The "Find a Geocache Zone" page has "Warning Zone Checker" where you put in GPS co-ordinates and click 'Check'. Awesome! Simple request: can you add this "Warning Zone Checker" onto the page used to create new cache, please?
  • Centroid Over Time -
  • Cacher specific galleries in new gallery system
  • Cache(r) half life, plot decline in find frequency
  • Cache(r) find frequency. Straight, and vs diff/terr
  • team v location: where different teams are putting their caches. colours represent teams
  • terrain v difficulty: correlated as most people don't understand the difference?
  • terrain v location: urban are are easy terrain, the ones away are harder?
  • difficulty v location: opposite to above
  • team cache style profiles: terrain v location, coloured blob represents team. colour gets brighter/blob larger as teams plant more caches of that style.
  • hit/miss ratio v terrain, difficulty
  • time to first find v location, time: hypothesis is that ttff is small in sydney but large further out. other hypothsis is that average ttff has decreased significantly over the past 12 months
  • team territorial analysis - thematic plot of where each team is usually active. for each team, assign (say) 5 points for a cache that they have laid, 2 points for a first find and 1 point for a normal find. then start shading areas based on the pointscore and see what you get. should be able to see odlid dave sitting down there in jannali, dogs up in hornsby, etc
  • add more filters eg GCA only , cache-types to maps (along side found, owned, etc).
  • Add API for Cache name search eg Android app (for authenticated users)
  • Advanced" search options: (from search bar - not my query page) * Filter by cache type * Filter by cache owner * Filter by state
  • GeoLists
  • Automatic winners' page for finders
  • HTML export from various cacher statistics pages (allow editing through FCK editor).
  • Generate a GPX file based on the caches visible from a Google Map page.
  • Allow cachers to add listing site prefixes to their ignore lists (like OX, OU, OK, GC, etc).

Rejected or not Required / Pursued

Ideas that have been proposed in the past but were rejected or did not progress at the time. These may always be brought up again in the future as times, minds and attitudes change with the influx of new players or the changing of the game over time.

  • Codeword caches. As an add on to a cache you may be required to locate the codeword at the location. These may be too similar to virtual caches which have no box, history caches which require Q&A and not a box. Geocaching is about a box, not finding a codeword in a message on a plaque.
  • Regular "Virtual" Event Activities _i.e. a scavenger hunt). A geocaching adventure where your location is independent of physical geocaches. A set of "requirements" is published in the event listing. The requirements are all virtual requirements in that they do not require a physical cache find, but virtual activities which can be achieved anywhere.
  • Hunt the wocket (cache). A wocket is a cache. You have an event ... but it's a special event where people gather at a starting spot. There are 3 (or any number up to n depending on how many participants you have) special caches at the gathering spot. Each one with the organisers (need 1 organiser for each special cache (wocket)). The event starts. Each organiser heads off in a direction. They can be similar or different. 10 minutes later they stop and hide the geocache. They update the co-ordinates of their cache. The game is now on. Each of the teams at the event move towards a cache. They are not going to be in the same park, they're most likely a few km away by now. They will need to choose which one they head towards. They have 15 minutes to find the cache. The first person to find the cache gets 10 points. The next person gets 9, then 8, 7, 6 etc., until there are no more points to allocate or the time has expired. One you've found the cache you can head off to find one of the other in the game or you can wait. There's some strategy needed to decide how and where you are going. Your team cannot split up. After the 15 minutes is up the game piece moves on. Again a 10 minute travel time for the cache, hide and update the co-ords. The participants now have 15 minutes to get to the cache and collect some more points. After a few hours, the game is over and everyone gathers back at a central location for the rest of the event which is congratulating the winners (points are added up obviously), commiserating the losers, bitching about inaccurate co-ordinates or how much the rules of hunt the wocket suck.
  • Geocaching Australia organises an Australia wide Rubber Duck Race. It's held in one town on a flowing body of water -- OR -- in each capital city. Permission is sought from the water owner (all capitals is going to be a logistical nightmare). People sponsor their way into the Rubber Duck Race for a nominal amount, (making numbers up), say $5.00. The winner, er, wins (something). The ducks are extracted from the body of water (including any who got lost along the way). The ducks are then released as movable Geocaching Australia Rubber Duck Geocaches. A few hundred identical Rubber Ducks are now available as Geocaching Australia geocaches. The race does not have to be along a river. The ducks could start at one event per state and then travel from that state. The duck further away from the start point when the game finishes is the winner.
  • Confluence caches - We are not restricted to just the degree confluence. If there are a number of degree confluences which are restricted by being on private property, we could increase the scope of the confluence caches by allowing a high frequency. e.g. Instead of just S37 E144 we could have S37 45 E144 45. Although that would increase the total number of possible confluences by a factor of 360 (60 x 60) to around 36,000. That seems a little over the top to me and I'd suspect that a significant number would be inaccessible as they would be on private property, especially in the urban areas. S37 10 E 144 10, S37 10 E 144 20, S37 10 E 144 20, etc would increase the CC's to around 8,000, again private property being most likely to kill a huge swathe of them.
  • A Geocaching Australia version of the CITO event cache type. No traction and no interest.
  • Geocaching Australia version of "challenge" caches. No traction and no interest.
  • Geocaching Australia "Environment" cache. Better than a CITO by making the environment, not just cleaning it up. Small interest, no traction, no progress.
  • Change the icons on the logs to a drop down list to save space / make look consistent.
  • Integrate GPSBabel to support zillions of formats (GPSBabel is already integrated into the Route functionality and can be extended to cover any required format of data or use), so not required for any specific action.