Opened 12 years ago
Closed 9 years ago
#155 closed defect (fixed)
egm96 grid files should be precompiled
| Reported by: | ravenAtSafe | Owned by: | Norm Olsen |
|---|---|---|---|
| Priority: | major | Milestone: | 3.0 |
| Component: | Library | Version: | svn-trunk |
| Keywords: | Cc: |
Description
Just like Ticket#151, CSmkBinaryEgm96() compiles WW15MGH.GRD on the fly. I don't know if the compiled version of this file is platform agnostic, but on-the-fly compilation certainly causes problems when CS-MAP doesn't have write permissions to the source grid directory.
Change History (2)
comment:1 by , 9 years ago
| Owner: | changed from to |
|---|
comment:2 by , 9 years ago
| Milestone: | → 3.0 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
| Version: | → svn-trunk |
Note:
See TracTickets
for help on using tickets.
Corrected at revision 2675. This issue exists only in the Linux /Unix environment. A new environmental variable reference was added. There are five modules which produce a binary shadow file: OSGM91, OSTN97, OSTN02, JPN GDK2000, and EGM96. In all cases, if the primary dictionary directory is write protected (thus preventing the creation of a new file in the directory) the shadow file is created in the directory indicated by the value of the CS_MAP_DIR_RW environmental variable. Iterative environmental variable replacement is performed on this value prior to its use.
Should this environmental variable change the location, or if the primary dictionary directory becomes writable, the only harm done is a onnne time regeneration of a new binary shadow file.