Your first port of call should be to look at some existing Routes in our database for a good idea of what to write.

The first thing you should consider is, "Is it a circular walk, or a A to B walk".  If it's a circular route, think about noting a recommended place to park.  If it's a straight route, with a start and an end, you could consider mentioning any public transport back to the start, or a place near the end to leave a second car.

Where ever possible, try to link to cache listings over on the gc.com website.  To do this, type out the text, highlight it and click on the "Insert/Edit Link"  button if you are using the default WYSIWYG editor.

You might also want to consider pointing out facilities along the way, such as public toilets and picnic areas. 

Maps:

You may have seen some Google Maps images with a route overlay on some of the existing routes.   These are actually quite easy to create if you are already familar with the Google Earth application.

Just us the "Add Path" button to trace the route as close to any footpaths as possible, then export the path as a .kml file.

Once the .kml file has been generated, upload it into our Repository (found in the Resources section of the website), then drop me a message and I'll work my magic and insert the map into your route description.

It is also possible to create route .kml files using the basic Google Maps website.  You will need to have a Google account, and there is a good set of instructions over on their website.

---