| 1 | <HTML><HEAD> |
|---|
| 2 | <TITLE>Survex To-Do List</TITLE> |
|---|
| 3 | <STYLE type="text/css"><!-- |
|---|
| 4 | BODY, TD, CENTER, UL, OL {font-family: sans-serif;} |
|---|
| 5 | --> |
|---|
| 6 | </STYLE> |
|---|
| 7 | </HEAD><BODY BGCOLOR=white TEXT=black> |
|---|
| 8 | <H1>Survex To-Do List</H1> |
|---|
| 9 | |
|---|
| 10 | <H2>3d format</H2> |
|---|
| 11 | |
|---|
| 12 | <ul> |
|---|
| 13 | |
|---|
| 14 | <li>sort out XSECT - I'm sure I meant there to be 1 and 2 byte forms, not 2 |
|---|
| 15 | and 4 - 4 byte is only useful if a passage dimension is > 327.67m! |
|---|
| 16 | |
|---|
| 17 | <li>store equated stations in some way |
|---|
| 18 | |
|---|
| 19 | <li>store legs by end stations rather than repeating coordinates over and |
|---|
| 20 | over? |
|---|
| 21 | |
|---|
| 22 | </ul> |
|---|
| 23 | |
|---|
| 24 | <H2>Aven</H2> |
|---|
| 25 | |
|---|
| 26 | <ul> |
|---|
| 27 | |
|---|
| 28 | <li>loading a .3d file with no survey data (or which has a valid header but is broken later) with a survey already loaded doesn't work well. |
|---|
| 29 | |
|---|
| 30 | <li>After keyboard controlled movement, the measuring line/circle doesn't |
|---|
| 31 | reappear until the mouse is moved (e.g. plan/elevation transition with P/L). |
|---|
| 32 | |
|---|
| 33 | <li>Fix depth clipping on grid |
|---|
| 34 | |
|---|
| 35 | <li>Does anyone use Controls->"Reverse Sense"? It made some sense with |
|---|
| 36 | caverot but now seeing the mouse pointer makes people expect the default |
|---|
| 37 | motions (for right button drag particularly). |
|---|
| 38 | |
|---|
| 39 | <li>Clean up export.cc and allow line width, etc to be specified |
|---|
| 40 | |
|---|
| 41 | <li>Better handling of missing LRUD values |
|---|
| 42 | |
|---|
| 43 | <li>Smooth wrinkles in presentation code (stop pres on Open or |
|---|
| 44 | New, changing focus on listctrl as presentation plays doesn't really work |
|---|
| 45 | properly) |
|---|
| 46 | |
|---|
| 47 | <li>Draw the measuring line directly onto the front buffer, so we can remove it |
|---|
| 48 | with a copy from the back buffer and redraw it in the new position without a |
|---|
| 49 | re-render. |
|---|
| 50 | |
|---|
| 51 | <li>Process all pending input before rerendering to improve responsiveness. |
|---|
| 52 | |
|---|
| 53 | <li>Check timing code - we need to glFinish to ensure it's all drawn, and that |
|---|
| 54 | may be needed to get meaningful timing info. |
|---|
| 55 | |
|---|
| 56 | <li>Allow control of colours in "colour by survey"; allow controlling what level |
|---|
| 57 | colours are applied at e.g. colour by cave (and more generally by sub-prefix) |
|---|
| 58 | |
|---|
| 59 | <li>Implement "Skip blank pages" in aven printing |
|---|
| 60 | |
|---|
| 61 | <li>different keyboard layouts mean that some key choices don't make much sense... |
|---|
| 62 | |
|---|
| 63 | <li>File->Extended Elevation - provide a way to specify a spec file? Or |
|---|
| 64 | better a UI to control the extending. |
|---|
| 65 | |
|---|
| 66 | <li>Optional lazy label redraw during drags? Or turn on at some redraw time |
|---|
| 67 | threshold... |
|---|
| 68 | |
|---|
| 69 | <li>Some way to view older/newer version of survey |
|---|
| 70 | |
|---|
| 71 | <li>Label lengths aren't considered when working out image size when |
|---|
| 72 | printing so a long label can spill off the edge of the printout |
|---|
| 73 | |
|---|
| 74 | <li>print to an image file? |
|---|
| 75 | |
|---|
| 76 | <li>grid on printouts |
|---|
| 77 | <ul> |
|---|
| 78 | <li>grid crosses option (only draw cross at intersections, not a full grid). |
|---|
| 79 | <li>[(x,y) of a point to go through (easting, northing) |
|---|
| 80 | <li>x spacing, y spacing (default to x spacing) |
|---|
| 81 | <li>orientation (bearing of y-axis?) (defaults to 0)] |
|---|
| 82 | </ul> |
|---|
| 83 | |
|---|
| 84 | <li>Profile aven further (for both speed and memory usage) |
|---|
| 85 | |
|---|
| 86 | <li>by default put crosses on those points with no legs attached (unused |
|---|
| 87 | fixed points)? |
|---|
| 88 | |
|---|
| 89 | <li>label junctions/dead ends? |
|---|
| 90 | |
|---|
| 91 | <li>section colouring/selective labelling |
|---|
| 92 | |
|---|
| 93 | <li>clipping - want to select a clip sphere (or maybe cube) centred on |
|---|
| 94 | centre on rotation I think. |
|---|
| 95 | |
|---|
| 96 | <li>Some way to display all the names of an equated station (e.g. in pop-up |
|---|
| 97 | window or the info panel). |
|---|
| 98 | |
|---|
| 99 | <li>check on monochrome, 16, and 256 colour displays - especially that depth |
|---|
| 100 | colouring looks OK |
|---|
| 101 | |
|---|
| 102 | <li>Feed back redraw time to key based movement as in caverot? Or perhaps best |
|---|
| 103 | not to? It depends on whether we expect people to hold down keys or not... |
|---|
| 104 | Perhaps something smart where the first press is a fixed size, then after that |
|---|
| 105 | it depends on the redraw? |
|---|
| 106 | |
|---|
| 107 | <li>improve .plt export to include less crude survey structure. |
|---|
| 108 | |
|---|
| 109 | <li>If multiple methods for drawing crosses and/or blobs pass the |
|---|
| 110 | visual fidelity check, check which is fastest. |
|---|
| 111 | |
|---|
| 112 | <li>Lots of aven things need documenting. |
|---|
| 113 | |
|---|
| 114 | <li>Stats reporting in aven - more helpful there than at end of cavern run as |
|---|
| 115 | user can check at any point and we can report for a subsurvey. NSEWUD-most |
|---|
| 116 | stations; node stats; count of stations with other than two legs or which are |
|---|
| 117 | fixed?; flag counts (#fixed stations, #exported stations, etc) with way to see |
|---|
| 118 | list of all such stations. |
|---|
| 119 | </ul> |
|---|
| 120 | |
|---|
| 121 | <H2>Documentation</H2> |
|---|
| 122 | |
|---|
| 123 | <ul> |
|---|
| 124 | |
|---|
| 125 | <li>Platform specific versions of docs? |
|---|
| 126 | |
|---|
| 127 | <li>Put more terms in terminology in docs ? trip, instrument, ... |
|---|
| 128 | |
|---|
| 129 | <li>Finish off manual loose ends. |
|---|
| 130 | |
|---|
| 131 | <li>Look at rewording extend.sgml (AndyA comments) |
|---|
| 132 | |
|---|
| 133 | </ul> |
|---|
| 134 | |
|---|
| 135 | <H2>Internationalisation and Localisation</H2> |
|---|
| 136 | |
|---|
| 137 | <ul> |
|---|
| 138 | |
|---|
| 139 | <li>Update translations. |
|---|
| 140 | |
|---|
| 141 | <li>length units in .err file? |
|---|
| 142 | |
|---|
| 143 | </ul> |
|---|
| 144 | |
|---|
| 145 | <H2>Test Suite</H2> |
|---|
| 146 | |
|---|
| 147 | <ul> |
|---|
| 148 | |
|---|
| 149 | <li>test diving data with compass omitted (plumbed) |
|---|
| 150 | |
|---|
| 151 | <li>more tests for direction |
|---|
| 152 | |
|---|
| 153 | <li>improve 3d torture test and try to automate its use if possible. |
|---|
| 154 | |
|---|
| 155 | </ul> |
|---|
| 156 | |
|---|
| 157 | <H2>Miscellaneous</H2> |
|---|
| 158 | |
|---|
| 159 | <ul> |
|---|
| 160 | |
|---|
| 161 | <li>resolve FIXMEs in code |
|---|
| 162 | |
|---|
| 163 | <li>diffpos: compare connectivity (i.e legs as well as stations) - e.g. |
|---|
| 164 | |
|---|
| 165 | <pre> |
|---|
| 166 | foo.1 moved by (0.02, 0.10, -0.06) |
|---|
| 167 | leg between foo.1 and bar.2 removed |
|---|
| 168 | ... |
|---|
| 169 | bar.2 moved by (-0.02, -0.05, 0.03) |
|---|
| 170 | </pre> |
|---|
| 171 | |
|---|
| 172 | </ul> |
|---|
| 173 | |
|---|
| 174 | <H2>Cavern</H2> |
|---|
| 175 | |
|---|
| 176 | <ul> |
|---|
| 177 | |
|---|
| 178 | <li>This gives "*** Singular!!!" warning with DEBUG_INVALID on: |
|---|
| 179 | <pre> |
|---|
| 180 | 1 2 50000 0 - |
|---|
| 181 | 1 2 5 0 -30 |
|---|
| 182 | </pre> |
|---|
| 183 | |
|---|
| 184 | <li>Default variance for topofil counter? (currently same as that of tape) |
|---|
| 185 | |
|---|
| 186 | <li>Don't split other traverses at articulating traverses when reporting error |
|---|
| 187 | stats. |
|---|
| 188 | |
|---|
| 189 | <li>sort out title which goes in .3d file for this (if no *includes in ... |
|---|
| 190 | it gets the title of the leafname of this .svx file, otherwise it's the |
|---|
| 191 | leafnames of the *include-d files, comma-separated): |
|---|
| 192 | |
|---|
| 193 | <pre> |
|---|
| 194 | *begin mycave |
|---|
| 195 | *title "My Cave" |
|---|
| 196 | ... |
|---|
| 197 | *end mycave |
|---|
| 198 | </pre> |
|---|
| 199 | |
|---|
| 200 | <li>look at solution by QR factorisation in matrix.c more |
|---|
| 201 | |
|---|
| 202 | <li>consider disabling the more expensive asserts - turning them all off |
|---|
| 203 | speeds up cavern by about 10%. |
|---|
| 204 | |
|---|
| 205 | <li> |
|---|
| 206 | Warn bearings not 3 digits, gradient not <sign><digit><digit> |
|---|
| 207 | |
|---|
| 208 | <li>Sort out gross error detection code |
|---|
| 209 | |
|---|
| 210 | <li>For warnings such as "Negative adjusted tape reading" report the |
|---|
| 211 | value of the adjusted tape reading (currently we just highlight the |
|---|
| 212 | reading as it appears in the Survex file). |
|---|
| 213 | |
|---|
| 214 | <li>legs: implied flags: inloop/plumb |
|---|
| 215 | |
|---|
| 216 | <li>legs: "dubious" for "tapeless" legs - bearing along continuation... |
|---|
| 217 | |
|---|
| 218 | <li>station flags: "important" - e.g. top camp "fixed" point / |
|---|
| 219 | junction,deadend (implied by order) / |
|---|
| 220 | articulation pt (know for nodes I think a station is if at least one |
|---|
| 221 | of its nodes is) |
|---|
| 222 | |
|---|
| 223 | <li>Maybe station lists should know how long they are? |
|---|
| 224 | |
|---|
| 225 | <li>Articulation point code: ideally the articulation point code should allow |
|---|
| 226 | further network reductions to happen after splitting at articulation |
|---|
| 227 | points? |
|---|
| 228 | |
|---|
| 229 | </ul> |
|---|
| 230 | |
|---|
| 231 | <H2>Survex file format</H2> |
|---|
| 232 | |
|---|
| 233 | <ul> |
|---|
| 234 | |
|---|
| 235 | <li>*data chamber ... |
|---|
| 236 | |
|---|
| 237 | <li>*data nsew ... for pitches (bearings rather than having to be NSEW) |
|---|
| 238 | |
|---|
| 239 | <li>Allow angles as deg/min/sec (for theodolite data) (060°10'15" as 060 10 |
|---|
| 240 | 15, or 060.1005 (crap notation)) |
|---|
| 241 | |
|---|
| 242 | <li>should % after a clino reading work? |
|---|
| 243 | |
|---|
| 244 | <li>Fixing a point by triangulation? |
|---|
| 245 | |
|---|
| 246 | <li>multiple readings: |
|---|
| 247 | <p> |
|---|
| 248 | average bearings specially - they don't average like normal numbers |
|---|
| 249 | <p> |
|---|
| 250 | %age gradients should probably average the same as angle gradients |
|---|
| 251 | <p> |
|---|
| 252 | Document - works like so: |
|---|
| 253 | <pre> |
|---|
| 254 | *set open { |
|---|
| 255 | *set close } |
|---|
| 256 | *calibrate compass {000.5 001.0 001.25} |
|---|
| 257 | 1 2 10.23 {000 001} -02 |
|---|
| 258 | 2 3 {10.16 10.17} 127 {+06 +05} |
|---|
| 259 | 3 4 11.98 007 {+03 +03} |
|---|
| 260 | </pre> |
|---|
| 261 | Implement as extension to number format so any suitable numeric value to be |
|---|
| 262 | repeated? |
|---|
| 263 | <li>Theodolite + level: |
|---|
| 264 | <ul> |
|---|
| 265 | <li>delta(bearing (relative to 0 at start) |
|---|
| 266 | <li>delta(horizontal) |
|---|
| 267 | <li>delta(vertical) / maybe "clino" instead |
|---|
| 268 | </ul> |
|---|
| 269 | |
|---|
| 270 | <li>Theodolite only: |
|---|
| 271 | <ul> |
|---|
| 272 | <li>delta(bearing (relative to 0 at start) |
|---|
| 273 | <li>delta(horizontal) |
|---|
| 274 | <li>infinite sd for z |
|---|
| 275 | </ul> |
|---|
| 276 | |
|---|
| 277 | <li>Infinite sds so we can fix in x and y only (or z only)? |
|---|
| 278 | |
|---|
| 279 | <li>legs: hydrology - fossil/active/not recorded/static water/underwater |
|---|
| 280 | (sump) [diving underwater by default? except style can mean altimeter |
|---|
| 281 | too...] |
|---|
| 282 | |
|---|
| 283 | <li>legs: floor type - mud/sand/breakdown/flowstone/etc and can then used |
|---|
| 284 | LRUD to draw crude survey... |
|---|
| 285 | |
|---|
| 286 | <li>Allow valid range for an instrument to be specified. Tie in with |
|---|
| 287 | *instrument. *units date - ranges for dates - e.g. "1990-" or |
|---|
| 288 | "jun-aug"... |
|---|
| 289 | |
|---|
| 290 | <li>cope with any combination of readings which gives enough info ??? |
|---|
| 291 | |
|---|
| 292 | <li>leg and station "comments": |
|---|
| 293 | |
|---|
| 294 | <pre>*data passage station left right up down comment |
|---|
| 295 | |
|---|
| 296 | 1 1.0 - 50+ 0.5 "large cairn" |
|---|
| 297 | |
|---|
| 298 | 2 ... |
|---|
| 299 | |
|---|
| 300 | *data normal station l r u d comment newline tape compass clino |
|---|
| 301 | |
|---|
| 302 | 1 1.0 - 50+ 0.5 "large cairn" |
|---|
| 303 | |
|---|
| 304 | 10.78 123 -03 |
|---|
| 305 | |
|---|
| 306 | 2 ... |
|---|
| 307 | </pre> |
|---|
| 308 | |
|---|
| 309 | comment can be omitted "-" or not present if at end of line...? |
|---|
| 310 | commentall? |
|---|
| 311 | |
|---|
| 312 | <li>Allow covariances to be specified in cartesian style? |
|---|
| 313 | |
|---|
| 314 | <li>flag legs as "skeletal" or something? (i.e. not in the cave passage) - |
|---|
| 315 | e.g. a radiolocation leg from one passage to another isn't surface, |
|---|
| 316 | but it isn't in the cave itself either (it's through rock). You could |
|---|
| 317 | just call it surface but maybe later we want to use the surface |
|---|
| 318 | flag to produce points for a surface triangulation... |
|---|
| 319 | |
|---|
| 320 | <li>?outlaw prefixes on stations in data legs (as Todd has lobbied for) |
|---|
| 321 | and then the prefix of a leg == prefix of each end...? |
|---|
| 322 | |
|---|
| 323 | <li>Units in *fix (currently metres) |
|---|
| 324 | |
|---|
| 325 | </ul> |
|---|
| 326 | |
|---|
| 327 | <H2>img library</H2> |
|---|
| 328 | |
|---|
| 329 | <ul> |
|---|
| 330 | |
|---|
| 331 | <li>make img more modular (convert to C++?) |
|---|
| 332 | |
|---|
| 333 | </ul> |
|---|
| 334 | |
|---|
| 335 | </BODY></HTML> |
|---|
