1.3.Name Component Descriptions

This page contains detailed suggestions for components of names to use when creating files containing cave survey and related data.  It is also relevant to creation of objects within various cave surveying applications, such as PocketTopo and Therion, or whatever it is you use.

As on the previous page, the general form of a file (or other object) name should be based on;

CaveName-SurveyPrefix-PassageName-Projection-TypeOfData-Date-Pg00of99.ext for data, and
CaveName - Projection - Locality, Region - Format - Date.ext for finished maps.


If necessary, a concise cave name comprehensible by humans

Example: MiddleEarth


A concise passage identifier comprehensible by your cave software

Examples: DB, 27

This is preferably determined prior to the day of the survey taking place, so that survey markers can be annotated appropriately in the cave. The Bulmer convention is a good one. A 2-letter code, the first letter indicating the year of the survey, the second the survey trip, however this limits the cave survey duration to 26 years, which has proved to be unreasonably short.

Reasonable software (such as Therion!) should allow any character that your computer operating system can handle in a file name, but many cave applications can only handle numeric or alpha characters.  You will need to choose survey numbering scheme that is compatible with your chosen software.


A concise passage name comprehensible by humans

Example: WetWay

Projection [Plan|ElevXXX] 

Plan or ElevXXX if relevant to the type of data

Elevations should be identified with the type or projection angle. 

  • ElevEXTfor extended (or developed) elevations
  • Elev000for projected elevations looking north (in the co-ordinate system used for the final map*)
  • Elev270for projected elevations looking 270 deg (in the co-ordinate system used for the final map*)

* The co-ordinate system could be local magnetic arbitrarily based on the cave itself, NZMG or NZTM. 

TypeOfData [Access|SurveyNotes|Sketches|Photos] 

Access = requirements for permission to access, contact details, route(s) to take
 = raw survey notes and sketches as recorded in the cave (multipage files preferred)
Sketches = careful drawings over plotted centreline ready for tracing or transcription into final cartography (single page files preferred)
Photo(s) = photos relating to this part of the cave
In the case of aerial photos the filename form could be AerialPhoto .ext where if the photo is from LINZ it describes the map reference. (Remember to credit the source for copyright reasons). 


The size of the paper that a full sized print will use ie A4, A3, A2 roll as appropriate.
You can also indicate the scale ie A4 1000, A3 500, A2 roll 250.


Format yyyymmdd so they sort in chronological order. The date should in general be the SURVEY DATE, except that in cases when the sketch is a conglomeration of surveys, a more recent date is probably more appropriate.
In the case of 'finished maps', the date would be the completion or compilation date of the map.
For finished maps it is OK to use the format Mmmyyyy (eg Sep2014 or 09Sep2014) as for these, sometimes, readability is more important than strict sorting. 


Page numbering.  Clearly state what pages and sequence context of those pages is, as in these examples.

Examples: Pg01, Pg01to06, Pg01of06 as appropriate. 


The file extension appropriate to its data type and intended use.  For finished maps pdf or svg is preferred for two dimensional presentation.  Models can be in any appropriate format.

Yes No Suggest edit
Last updated on April 30, 2020
0 of 0 users found this section helpful
Help Guide Powered by Documentor
Suggest Edit