Opened 9 years ago
Closed 3 years ago
#56 closed defect (fixed)
Sort out handling of geoid
Reported by: | Olly Betts | Owned by: | Olly Betts |
---|---|---|---|
Priority: | major | Milestone: | 1.4.0 |
Component: | aven | Version: | 1.2.18 |
Keywords: | Cc: |
Description (last modified by )
Currently the altitude of GPS fixes and hence of cave entrances attached to them doesn't match the altitude of terrain from DEM files very well - the difference seems to be a few 10s of metres.
Newer versions of proj have support for geoids, which should solve this:
https://trac.osgeo.org/proj/wiki/VerticalDatums
I think proj >= 4.8.0 is needed - the release announcement for it includes "Added preliminary vertical datum support". That was released 2012-03-14, so shouldn't be an unreasonable requirement.
It would be good to coordinate how vertical datums are handled with therion, but they didn't respond to my email to their list about doing so.
Change History (8)
comment:1 Changed 9 years ago by
Description: | modified (diff) |
---|
comment:2 Changed 7 years ago by
Milestone: | 1.2.31 → 1.2.32 |
---|
comment:3 Changed 7 years ago by
Milestone: | 1.2.32 → 1.2.33 |
---|
Ticket retargeted after milestone closed
comment:4 Changed 7 years ago by
Milestone: | 1.2.33 → 1.2.34 |
---|
Ticket retargeted after milestone closed
comment:5 Changed 6 years ago by
Milestone: | 1.2.34 → 1.2.36 |
---|
Ticket retargeted after milestone closed
comment:6 Changed 6 years ago by
Milestone: | 1.2.36 → 1.2.37 |
---|
Ticket retargeted after milestone closed
comment:8 Changed 3 years ago by
Milestone: | → 1.4.0 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
This will be addressed by 1.4.0, which now requires PROJ >= 8.2.0 and uses the new PROJ API. This seems to take the vertical datum into account automatically.
Ticket retargeted after milestone closed