This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ivac2:firdef_map_latlon [2014/02/04 10:00] filip.jonckers |
ivac2:firdef_map_latlon [2017/04/08 14:27] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | [[ivac2:firdef_toc|Back]] | ||
| - | |||
| ====== Latitude and Longitude attributes ====== | ====== Latitude and Longitude attributes ====== | ||
| Line 25: | Line 23: | ||
| * sssss = seconds with maximum 3 decimal places (max 59.999) | * sssss = seconds with maximum 3 decimal places (max 59.999) | ||
| - | The predefined //<point>// elements are defined in the [[ivac2:firdef_points_xml|points.xml]] file. Use the id attribute to use a predefined //<point>// element. | + | The predefined //<point>// elements are defined in the [[ivac2:firdef_points_xml|points.xml]] file. Use the **ref** attribute to use a predefined //<point>// element. |
| Line 39: | Line 37: | ||
| === Example === | === Example === | ||
| + | <code XML> | ||
| + | <point lat="N0504413" lon="E0043108"/> | ||
| + | <point lat="N0504421" lon="E0042601"/> | ||
| + | <point lat="N0504528" lon="E0042119"/> | ||
| + | </code> | ||
| - | <point lon="N0543000000" lat="W0033535000"/> | ||
| - | <point lon="E0043127" lat="N0511038"/> | ||
| - | <point lon="E0043140" lat="N0511101"/> | ||
| - | <point ref=”REMBA”/> | ||
| - | <point ref=”EBBR-IAF-25L”/> | ||
| - | |||
| + | ===== Sectorfile latitude/longitude overflow bug ===== | ||
| - | ===== The sectorfile latitude/longitude overflow bug ===== | ||
| - | + | Keep a sharp lookout for a major bug in latitude and longitude coordinates which originate from IvAc v1 sectorfiles created with the old //sector file creator website//. Apparently IVAC v1 did not care about this error and just used the data regardless of the overflow value. | |
| - | Keep a sharp lookout for a major bug in sectorfiles which originates in the old sectorfile creation website. | + | |
| - | + | ||
| - | Apparently IVAC v1 did not care about this error and just used the data regardless of the overflow value. | + | |
| Line 64: | Line 58: | ||
| Notice the overflow value in the seconds part: **60 seconds** ?! | Notice the overflow value in the seconds part: **60 seconds** ?! | ||
| - | 60 seconds = 1 minute .... | + | 60 seconds = 1 minute .... The maximum seconds value should be 59.999 seconds - so we have an overflow issue: |
| - | + | ||
| - | The maximum seconds value should be 59.999 seconds - so we have an overflow issue: | + | |
| 002:32:60.000 should be corrected to 002:33:00.000 | 002:32:60.000 should be corrected to 002:33:00.000 | ||
| - | You will also find coordinates like E0082339001 ending in '1' | + | You will also find coordinates like E0082339001 ending in '1'. These are also calculation errors and can be safely set to '0' |
| - | + | ||
| - | These are also calculation errors and can be safely set to '0' | + | |
| E0082339001 -> E0082339000 | E0082339001 -> E0082339000 | ||
| - | |||
| ==== How to find any occurences of the bug? ==== | ==== How to find any occurences of the bug? ==== | ||
| + | Check the log file for errors in *log/ivac.log* for an overflow error similar to: | ||
| + | ERROR Java2D Queue Flusher ... out of range:E0023260000 | ||
| - | Check the log file for errors in *log/ivac.log* | + | Simply use your text editor to search for the listed coordinate. |
| - | There will be an overflow error similar to: | ||
| - | ERROR Java2D Queue Flusher ... out of range:E0023260000 | + | ---- |
| + | |||
| + | [[ivac2:firdef|Back]] | ||
| - | Simply use your text editor to search for the listed coordinate. | ||