#92 closed enhancement (fixed)
Results of declination auto in log file
| Reported by: | Rob Eavis | Owned by: | Olly Betts |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.4.2 |
| Component: | Other | Version: | |
| Keywords: | Cc: |
Description
When using *declination auto <x> <y> <z> it is hard to check if it is actually working correctly. It would be helpful therefore if the declination value used (based on location and date) was recorded in the process log file.
Change History (7)
comment:1 Changed 5 years ago by
comment:2 Changed 3 years ago by
It would also be useful to report the convergence values. Those at least don't vary by date, only location, so it would probably be feasible to just report as a "note: convergence correction 1.07° applied" each time *declination auto is used.
comment:3 Changed 15 months ago by
| Milestone: | → 1.4,1 |
|---|
I think we could report a declination range (with dates for the extremes) and convergence correction for each declination auto (of which there's typically just one). That would allow checking that it's working correctly without logging an overwhelming amount of extra information for some larger datasets.
I'll see if I can sort this out for 1.4.1.
comment:4 Changed 15 months ago by
I had a go at this, and have a prototype (pushed as branch report-calculated-declinations).
For the CUCC Austria dataset mentioned above this reports:
Declination at (47.68750°, 13.82103°, 1904m): -0.4° @ 1977-07-02 to 3.8° @ 2018-07-21, convergence = -0.9°
Those are the extreme declination values calculated, and the dates at which they were calculated.
You'd get a line like this for each *declination auto ... (ignoring any which don't actually get applied to any data). This dataset specifies a single location, so you get a single line.
I think we probably should make these info messages with the location being the *declination auto ... command in question. This location in the survey data may be useful in itself, but also provides the location in a more natural coordinate system. So the output might be:
kataster/1623.svx:20: info: Calculated declination range: -0.4° @ 1977-07-02 to 3.8° @ 2018-07-21, convergence = -0.9° *declination auto 36670.37 83317.43 1903.97
I need to make a quick 1.4.1 release to fix the testsuite problem with 1.4.0, but hopefully I can get this finished off and merged soon.
comment:6 Changed 15 months ago by
| Milestone: | 1.4.1 → 1.4.2 |
|---|
Ticket retargeted after milestone closed
comment:7 Changed 12 months ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Implemented in 37d6b84fb1ac772bf44344230af23bba127d321b. Should be in upcoming 1.4.2 release.
Final version of the message looks like:
/home/ol/1623.svx:20: info: Declination: -0.4° @ 1977-07-02 / 3.8° @ 2018-07-21, grid convergence: -0.9° *declination auto 36670.37 83317.43 1903.97
The problem is the sheer amount of declination information that there is for a larger dataset - even if you only specify one location to calculate declinations at there's a separate declination value for every different date. For example, in CUCC's Austria dataset there are currently 702 different dates so at least 702 declination values to report. To be useful I think it would have to be shown as some sort of graph or chart, or stored in the 3d file so you could check what it was for a particular leg (or even colour by declination).