| 1 | <!DOCTYPE HTML PUBLIC "-//W4C//DTD HTML 4.0 Transitional//EN"> |
|---|
| 2 | <HTML><HEAD> |
|---|
| 3 | <TITLE>Survex 3d Format Specification</TITLE> |
|---|
| 4 | <STYLE type="text/css"><!-- |
|---|
| 5 | BODY, TD, TH, CENTER, UL, OL {font-family: sans-serif;} |
|---|
| 6 | TD, TH {font-size: 11pt; vertical-align: top;} |
|---|
| 7 | TH {white-space: nowrap; background-color: #ffc;} |
|---|
| 8 | .code {text-align: center; white-space: nowrap;} |
|---|
| 9 | .type {text-align: center; white-space: nowrap;} |
|---|
| 10 | .data {text-align: left; white-space: nowrap;} |
|---|
| 11 | .desc {text-align: left; white-space: wrap;} |
|---|
| 12 | .version {text-align: center; white-space: wrap;} |
|---|
| 13 | TH.data, TH.desc {text-align: center;} |
|---|
| 14 | .reserved {background-color: #ddd;} |
|---|
| 15 | --> |
|---|
| 16 | </STYLE> |
|---|
| 17 | </HEAD><BODY BGCOLOR=white TEXT=black> |
|---|
| 18 | <H1>Survex 3d Format Specification</H1> |
|---|
| 19 | |
|---|
| 20 | <P>If you're writing in C or C++ it's <b>strongly</b> recommended |
|---|
| 21 | that you use the img routine provided with Survex to read and write |
|---|
| 22 | 3d files. Doing so means that you can take advantage of any revisions |
|---|
| 23 | to the 3d format by simply rebuilding your software with the updated |
|---|
| 24 | img routines, rather than having to update your own code. It also |
|---|
| 25 | allows you to read a sub-set of the data in the file, restricted by |
|---|
| 26 | Survey prefix.</P> |
|---|
| 27 | |
|---|
| 28 | <P>This document only describes the more recent revisions of the 3d format |
|---|
| 29 | (versions 3, 4, 5, and 6). |
|---|
| 30 | Version 3 was produced by Survex versions 0.97 and later, |
|---|
| 31 | version 4 by Survex 1.1.0-1.1.3, |
|---|
| 32 | version 5 by Survex 1.1.4-1.1.10, |
|---|
| 33 | and version 6 by versions from 1.1.11.</P> |
|---|
| 34 | |
|---|
| 35 | <P>If you try to use this specification and find details which aren't |
|---|
| 36 | spelled out clearly enough (or at all!) or any errors, please let us know. |
|---|
| 37 | At least two people have successfully written code to read 3d files |
|---|
| 38 | using this document, but that doesn't mean it can't be improved. |
|---|
| 39 | </P> |
|---|
| 40 | |
|---|
| 41 | <H2>File Header</H2> |
|---|
| 42 | |
|---|
| 43 | <P>This consists of:</P> |
|---|
| 44 | |
|---|
| 45 | <ul> |
|---|
| 46 | <li>File ID: the string "Survex 3D Image File" followed by a linefeed |
|---|
| 47 | (decimal 10, hex x0a). [Note: v0.01 files can have a carriage return |
|---|
| 48 | before this and other linefeeds - this is a file format error in any |
|---|
| 49 | other format version]. |
|---|
| 50 | <li>File format version: "v3", "v4", or "v5" followed by a linefeed. |
|---|
| 51 | Any future versions will be "v6", "v7", ..., "v10", "v11", etc. |
|---|
| 52 | Older format versions aren't described here, but had version strings |
|---|
| 53 | "v0.01", "Bv0.01", "bv0.01", and "v2"). |
|---|
| 54 | <li> Survey title: A string followed by a linefeed. There's no length limit on this string. |
|---|
| 55 | <li> Timestamp: A string followed by a linefeed. This is intended to be the |
|---|
| 56 | time the file was generated, rather than the time the survey data was |
|---|
| 57 | collected. The easiest way to generate this is with the strftime() format |
|---|
| 58 | "%a,%Y.%m.%d %H:%M:%S %Z" if you have access to strftime(). An example |
|---|
| 59 | timestamp is "Sun,2002.03.17 14:01:07 GMT". |
|---|
| 60 | </ul> |
|---|
| 61 | |
|---|
| 62 | <H2>Items</H2> |
|---|
| 63 | |
|---|
| 64 | <P>Following the header are a number of items. The last item must be a 0x00 |
|---|
| 65 | byte when the current label is empty, which marks the end of the data. The |
|---|
| 66 | first byte of an item is a code identifying what the item is:</P> |
|---|
| 67 | |
|---|
| 68 | <table border="1" cellpadding="1" cellspacing="0" width="100%"> |
|---|
| 69 | <tr> |
|---|
| 70 | <th class="code">Code</th> |
|---|
| 71 | <th class="code">Type</th> |
|---|
| 72 | <th class="data">Data</th> |
|---|
| 73 | <th class="desc" colspan="2">Meaning</th> |
|---|
| 74 | <th class="version">Version</th> |
|---|
| 75 | </tr> |
|---|
| 76 | <tr> |
|---|
| 77 | <td class="code">0x00</td> |
|---|
| 78 | <td class="type">STOP</td> |
|---|
| 79 | <td class="data"> </td> |
|---|
| 80 | <td class="desc" colspan="2"> |
|---|
| 81 | If the current label is empty, signifies the end of the data in the 3d |
|---|
| 82 | file; if the current label isn't empty, make it empty.</td> |
|---|
| 83 | <td class="version">≥3</td> |
|---|
| 84 | </tr> |
|---|
| 85 | <tr> |
|---|
| 86 | <td class="code">0x01 - 0x0e</td> |
|---|
| 87 | <td class="type">TRIM</td> |
|---|
| 88 | <td class="data"> </td> |
|---|
| 89 | <td class="desc" colspan="2"> |
|---|
| 90 | Trim the last 16 characters of the current label, then trim back N (i.e. |
|---|
| 91 | 1-14) dots ("."), everything after that particular dot. |
|---|
| 92 | It's incorrect if the label ends up empty, or you attempt to trim more |
|---|
| 93 | label than there is. The rationale for removing 16 characters first is |
|---|
| 94 | that removal of 1-16 characters can be encoded by 0x10-0x1f (see below) |
|---|
| 95 | and we can make this encoding more powerful by not |
|---|
| 96 | overlapping what can be encoded.</td> |
|---|
| 97 | <td class="version">≥3</td> |
|---|
| 98 | </tr> |
|---|
| 99 | <tr> |
|---|
| 100 | <td class="code">0x0f</td> |
|---|
| 101 | <td class="type">MOVE</td> |
|---|
| 102 | <td class="data"><x> <y> <z></td> |
|---|
| 103 | <td class="desc" colspan="2"> |
|---|
| 104 | Set current position to the coordinates given. Coordinates |
|---|
| 105 | are 4 byte little-endian signed integers representing |
|---|
| 106 | values in centimetres (0.01 metres).</td> |
|---|
| 107 | <td class="version">≥3</td> |
|---|
| 108 | </tr> |
|---|
| 109 | <tr> |
|---|
| 110 | <td class="code">0x10 - 0x1f</td> |
|---|
| 111 | <td class="type">TRIM</td> |
|---|
| 112 | <td class="data"> </td> |
|---|
| 113 | <td colspan="2"> |
|---|
| 114 | Remove N-15 (i.e. 1-16) characters from the current label. It's |
|---|
| 115 | incorrect if the label ends up empty, or you attempt to trim more label |
|---|
| 116 | than there is.</td> |
|---|
| 117 | <td class="version">≥3</td> |
|---|
| 118 | </tr> |
|---|
| 119 | <tr> |
|---|
| 120 | <td class="code">0x20</td> |
|---|
| 121 | <td class="type">DATE</td> |
|---|
| 122 | <td class="data"><date></td> |
|---|
| 123 | <td colspan="2"> |
|---|
| 124 | Set survey date of legs (date is 4 byte little endian unsigned integer |
|---|
| 125 | counting seconds since 1970) </td> |
|---|
| 126 | <td class="version">≥4</td> |
|---|
| 127 | </tr> |
|---|
| 128 | <tr> |
|---|
| 129 | <td class="code">0x21</td> |
|---|
| 130 | <td class="type">DATE</td> |
|---|
| 131 | <td class="data"><date1><date2></td> |
|---|
| 132 | <td colspan="2"> |
|---|
| 133 | Set survey date of legs to a range (date1, date2 are 4 byte little |
|---|
| 134 | endian unsigned integer counting seconds since 1970) </td> |
|---|
| 135 | <td class="version">≥4</td> |
|---|
| 136 | </tr> |
|---|
| 137 | <tr> |
|---|
| 138 | <td class="code">0x22</td> |
|---|
| 139 | <td class="type">ERROR</td> |
|---|
| 140 | <td class="data"><legs><length><E><H><V></td> |
|---|
| 141 | <td colspan="2"> |
|---|
| 142 | Error information for the current traverse. <legs> is the number of legs. <length> is the total length of the |
|---|
| 143 | traverse in cm (0.01m). E, H and V are the error and thehorizontal and vertical components in cm. (All values are 4 byte little |
|---|
| 144 | endian signed integers) </td> |
|---|
| 145 | <td class="version">≥6</td> |
|---|
| 146 | </tr> |
|---|
| 147 | <tr class="reserved"> |
|---|
| 148 | <td class="code">0x23 - 0x2f</td> |
|---|
| 149 | <td class="type"> </td> |
|---|
| 150 | <td class="data"> </td> |
|---|
| 151 | <td colspan="3">Reserved</td> |
|---|
| 152 | </tr> |
|---|
| 153 | <tr> |
|---|
| 154 | <td class="code" rowspan="3">0x30 - 0x31</td> |
|---|
| 155 | <td class="type" rowspan="3">XSECT</td> |
|---|
| 156 | <td class="data" rowspan="3"><len> <label> <L> <R> <U> <D></td> |
|---|
| 157 | <td colspan="2"> |
|---|
| 158 | Dimensions are 2 byte little-endian signed integers representing values |
|---|
| 159 | in centimetres (0.01 metres). Omitted dimensions are encoded as 0xffff. |
|---|
| 160 | Station flags are (N & 0x01): </td> |
|---|
| 161 | <td class="version" rowspan="3">≥5</td> |
|---|
| 162 | </tr> |
|---|
| 163 | <tr> |
|---|
| 164 | <th>Flag (N & 0x01)</th> |
|---|
| 165 | <th>Meaning</th> |
|---|
| 166 | </tr> |
|---|
| 167 | <tr> |
|---|
| 168 | <td>0x01</td> |
|---|
| 169 | <td>Station is last one in this passage</td> |
|---|
| 170 | </tr> |
|---|
| 171 | <tr> |
|---|
| 172 | <td class="code" rowspan="3">0x32 - 0x33</td> |
|---|
| 173 | <td class="type" rowspan="3">XSECT</td> |
|---|
| 174 | <td class="data" rowspan="3"><len> <label> <L> <R> <U> <D></td> |
|---|
| 175 | <td colspan="2"> |
|---|
| 176 | Dimensions are 4 byte little-endian signed integers representing values |
|---|
| 177 | in centimetres (0.01 metres). Omitted dimensions are encoded as |
|---|
| 178 | 0xffffffff.</td> |
|---|
| 179 | <td class="version" rowspan="3">≥5</td> |
|---|
| 180 | </tr> |
|---|
| 181 | <tr> |
|---|
| 182 | <th>Flag (N & 0x01)</th> |
|---|
| 183 | <th>Meaning</th> |
|---|
| 184 | </tr> |
|---|
| 185 | <tr> |
|---|
| 186 | <td>0x01</td> |
|---|
| 187 | <td>Station is last one in this passage</td> |
|---|
| 188 | </tr> |
|---|
| 189 | <tr class="reserved"> |
|---|
| 190 | <td class="code">0x34 - 0x3f</td> |
|---|
| 191 | <td class="type"> </td> |
|---|
| 192 | <td class="data"> </td> |
|---|
| 193 | <td colspan="3">Reserved</td> |
|---|
| 194 | </tr> |
|---|
| 195 | <!-- Checked to here! --> |
|---|
| 196 | <tr> |
|---|
| 197 | <td class="code" rowspan="13">0x40 - 0x7f</td> |
|---|
| 198 | <td class="type" rowspan="13">LABEL</td> |
|---|
| 199 | <td class="data" rowspan="13"><len> <label> <x> <y> <z></td> |
|---|
| 200 | <td colspan="2"> |
|---|
| 201 | Append label to the current label buffer. The updated contents of the |
|---|
| 202 | label buffer give the survey stations full name. The length of label is |
|---|
| 203 | given by length, which is encoded as follows:</td> |
|---|
| 204 | <td class="version" rowspan="12">≥3</td> |
|---|
| 205 | </tr> |
|---|
| 206 | <tr> |
|---|
| 207 | <th>Length</th> |
|---|
| 208 | <th>Encoding</th> |
|---|
| 209 | </tr> |
|---|
| 210 | <tr> |
|---|
| 211 | <td>0 - 253</td> |
|---|
| 212 | <td>byte 0x00 - 0xfd</td> |
|---|
| 213 | </tr> |
|---|
| 214 | <tr> |
|---|
| 215 | <td>254-65789</td> |
|---|
| 216 | <td>byte 0xfe 2 byte little-endian unsigned integer len-254 0x0000-0xffff</td> |
|---|
| 217 | </tr> |
|---|
| 218 | <tr> |
|---|
| 219 | <td>65790 and greater</td> |
|---|
| 220 | <td>byte 0xff 4 byte little-endian unsigned integer len |
|---|
| 221 | 0x000100fd-0xffffffff</td> |
|---|
| 222 | </tr> |
|---|
| 223 | <tr> |
|---|
| 224 | <td colspan="2"> |
|---|
| 225 | The station flags are encoded in the bottom 6 bits of the item code:</td> |
|---|
| 226 | </tr> |
|---|
| 227 | <tr> |
|---|
| 228 | <th>Flag (N & 0x3f)</th> |
|---|
| 229 | <th>Meaning</th> |
|---|
| 230 | </tr> |
|---|
| 231 | <tr> |
|---|
| 232 | <td>0x01</td> |
|---|
| 233 | <td>Station is on leg above ground</td> |
|---|
| 234 | </tr> |
|---|
| 235 | <tr> |
|---|
| 236 | <td>0x02</td> |
|---|
| 237 | <td>Station is on an underground leg (both may be true at an entrance)</td> |
|---|
| 238 | </tr> |
|---|
| 239 | <tr> |
|---|
| 240 | <td>0x04</td> |
|---|
| 241 | <td>Station is marked as an entrance (with *entrance)</td> |
|---|
| 242 | </tr> |
|---|
| 243 | <tr> |
|---|
| 244 | <td>0x08</td> |
|---|
| 245 | <td>Station is exported (i.e. may be used as a connection point to other |
|---|
| 246 | surveys)</td> |
|---|
| 247 | </tr> |
|---|
| 248 | <tr> |
|---|
| 249 | <td>0x10</td> |
|---|
| 250 | <td>Station is a fixed point (control point)</td> |
|---|
| 251 | </tr> |
|---|
| 252 | <tr class="reserved"> |
|---|
| 253 | <td>0x20</td> |
|---|
| 254 | <td colspan="2">Reserved</td> |
|---|
| 255 | </tr> |
|---|
| 256 | <tr> |
|---|
| 257 | <td class="code" rowspan="8">0x80 - 0xbf</td> |
|---|
| 258 | <td class="type" rowspan="8">LINE</td> |
|---|
| 259 | <td class="data" rowspan="8"><len> <label> <x> <y> <z></td> |
|---|
| 260 | <td colspan="2"> |
|---|
| 261 | Append label to the current label buffer. The length of the label is |
|---|
| 262 | encoded as for a station label above. Return leg from current position |
|---|
| 263 | to coordinates given, and update current position to coordinates given. |
|---|
| 264 | The updated contents of the label buffer give the survey that the leg is |
|---|
| 265 | in.</td> |
|---|
| 266 | <td class="version" rowspan="5">≥3</td> |
|---|
| 267 | </tr> |
|---|
| 268 | <tr> |
|---|
| 269 | <th>Flag (N & 0x3f)</th> |
|---|
| 270 | <th>Meaning</th> |
|---|
| 271 | </tr> |
|---|
| 272 | <tr> |
|---|
| 273 | <td>0x01</td> |
|---|
| 274 | <td>Leg is above ground</td> |
|---|
| 275 | </tr> |
|---|
| 276 | <tr> |
|---|
| 277 | <td>0x02</td> |
|---|
| 278 | <td>Leg duplicates data in another leg (e.g. resurvey along a passage to |
|---|
| 279 | tie into a known station)</td> |
|---|
| 280 | </tr> |
|---|
| 281 | <tr> |
|---|
| 282 | <td>0x04</td> |
|---|
| 283 | <td>Leg is a splay shot in a chamber (radial shots from a central point)</td> |
|---|
| 284 | </tr> |
|---|
| 285 | <tr class="reserved"> |
|---|
| 286 | <td>0x08</td> |
|---|
| 287 | <td colspan="2">Reserved</td> |
|---|
| 288 | </tr> |
|---|
| 289 | <tr class="reserved"> |
|---|
| 290 | <td>0x10</td> |
|---|
| 291 | <td colspan="2">Reserved</td> |
|---|
| 292 | </tr> |
|---|
| 293 | <tr class="reserved"> |
|---|
| 294 | <td>0x20</td> |
|---|
| 295 | <td colspan="2">Reserved</td> |
|---|
| 296 | </tr> |
|---|
| 297 | <tr class="reserved"> |
|---|
| 298 | <td class="code">0xc0 - 0xff</td> |
|---|
| 299 | <td class="type"> </td> |
|---|
| 300 | <td class="data"> </td> |
|---|
| 301 | <td colspan="3">Reserved</td> |
|---|
| 302 | </tr> |
|---|
| 303 | </table> |
|---|
| 304 | |
|---|
| 305 | <H2>Item order</H2> |
|---|
| 306 | <ul> |
|---|
| 307 | <li>A continuous section of centreline is defined by a <MOVE> item, followed |
|---|
| 308 | by one or more <LINE> items.</li> |
|---|
| 309 | <li><LABEL> items may appear anywhere in the file after the header, |
|---|
| 310 | including within a <MOVE><LINE>... sequence.</li> |
|---|
| 311 | <li>Duplicate <LABEL> items are permitted provided they also have identical |
|---|
| 312 | coordinate values. (The same coordinate values may also be shared by any |
|---|
| 313 | number of different <LABEL> items).</li> |
|---|
| 314 | <li>Stations must be defined in a <LABEL> item <u>before</u> being |
|---|
| 315 | referenced (e.g. in <XSECT> items)</li> |
|---|
| 316 | </ul> |
|---|
| 317 | |
|---|
| 318 | <P>Authors: Olly Betts and Mike McCombe, last updated: 2007-06-12</P> |
|---|
| 319 | </BODY></HTML> |
|---|
