Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
ivac2:firdef_map_latlon [2014/02/04 10:11]
filip.jonckers
ivac2:firdef_map_latlon [2015/06/07 22:10]
splendor.bouman [The sectorfile latitude/longitude overflow bug]
Line 25: Line 25:
   * 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 39:
  
 === 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.+