Opened 11 years ago
Closed 9 years ago
#316 closed defect (fixed)
Missing values in lat, long, azimuth for ropp_pp_invert_tool
Reported by: | Kent Bækgaard Lauritsen | Owned by: | Stig Syndergaard |
---|---|---|---|
Priority: | normal | Milestone: | DMI ROPP developments |
Component: | ropp_pp | Version: | 6.0 |
Keywords: | Invert | Cc: |
Description
Missing values in lat, long, azimuth for ROPP_Invert
Change history (5)
comment:1 by , 11 years ago
Summary: | Missing values in lat, long, azimuth for ROPP_Invert → Missing values in lat, long, azimuth for ROPP_Invert_tool |
---|
comment:2 by , 11 years ago
Status: | new → accepted |
---|---|
Summary: | Missing values in lat, long, azimuth for ROPP_Invert_tool → Missing values in lat, long, azimuth for ropp_pp_invert_tool |
comment:3 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
comment:4 by , 9 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
The implemented solution does not work across the date-line, or when azimuth changes over 360 deg, or close to the poles.
We need to implement a general solution. E.g. by transforming (lat,lon,azimuth) to cartesian coordinates, then interpolate, and then transform back again (possibly normalizing before back-transformation).
comment:5 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Note:
See TracTickets
for help on using tickets.
When running ropp_pp_invert_tool on a atm file, lat_tp, lon_tp, and azimuth_tp are not transferred to output, so missing values comes out instead.