API tools faq
paste
Advertisement
AndrewHaxalot

Instructions For Filling Out IGS Site Logs

AndrewHaxalot
Aug 22nd, 2013
88
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.57 KB | None | 0 0
raw download clone embed print report
  1. Instructions for filling out IGS site logs
  2. Apr 2011
  3.  
  4. See log form at ftp://igs.org/pub/station/general/blank.log
  5.  
  6. General
  7. =======
  8.  
  9. Please prepare site logs in plain ASCII.
  10.  
  11. Line length is limited to 80 characters.
  12.  
  13. See http://igs.org/network/sitelog-submissions.html for
  14. parsing instructions. When ready, submit site logs by sending as a
  15. plain text email message to igscb@igscb.jpl.nasa.gov. Site logs
  16. are usually handled by the CB within about one business day.
  17.  
  18. Date and time formats within the site log follow the basic format
  19. "CCYY-MM-DDThh:mmZ" from ISO 8061; see
  20. http://www.iso.ch/iso/en/prods-services/popstds/datesandtime.html
  21. As a summary, CC=2 digit century
  22. YY=2 digit year
  23. MM=2 digit month
  24. DD=2 digit day of month
  25. T=date/time separator
  26. hh=2 digit hour
  27. mm=2 digit minutes of hour
  28. Z=UTC indicator
  29. /=separator when begin & end times are given
  30.  
  31. A date without a time is specified like "2003-07-30", not "2003-07-30Thh:mmZ"
  32.  
  33. Latitude/Longitude formats are aligned to ISO 6709:
  34. Lat: +/-DDMMSS.SS
  35. Long: +/-DDDMMSS.SS
  36. A + or - sign is required. Leading zeroes must be used as appropriate
  37. to maintain the DDMMSS and DDDMMSS format.
  38.  
  39. Valid latitude range is -90 degrees to +90 degrees.
  40. Valid longitude range is from -180 degrees to (infinitesmally less than) +180
  41. degrees.
  42.  
  43. "etc" indicates you may enter any relevant answer, not just a choice
  44. ofthe suggestions shown.
  45.  
  46. "F7.4," "A4" and so on indicate the FORTRAN-style format which the
  47. response should have.
  48. Example 12345.7 = F7.1
  49. ABCD = A4
  50.  
  51. Blocks which have a "N.x" definition (namely sections 3-10) should
  52. always have the complete historic set of information; when a change is
  53. made, the previous information is left (for example in section 3.1)
  54. and the new information is placed in a new block numbered 3.2. Please
  55. leave the .x sections uncompleted to remind yourself of the format
  56. when the next change occurs.
  57.  
  58. Please remove the response hints such as "(F7.4 N/S)" as you fill out
  59. the log (except in the .x sections and Date Removed fields for
  60. currently installed equipment, which you will not alter). If an
  61. answer in an optional field is unknown, try to learn the answer for
  62. the next log update.
  63.  
  64. If you have any questions not answered here, please feel free to
  65. contact the IGS Central Bureau:igscb@igscb.jpl.nasa.gov
  66.  
  67. Special Instructions by section
  68. ================================
  69.  
  70. 0. Form
  71. -----------
  72.  
  73. If Update:
  74. Previous Site Log : (ssss_CCYYMMDD.log)
  75. If the site already has a log at the IGS Central Bureau, enter
  76. the filename currently found under
  77. ftp://igs.org/pub/station/log/
  78. ssss = 4 character site name
  79.  
  80. If Update:
  81. Modified/Added Sections : (n.n,n.n,...)
  82. Enter the sections which have changed from the previous version
  83. of the log. Example: 3.2, 4.2
  84.  
  85. 1. Site Identification of the GNSS Monument
  86. ---------------------------------------------
  87.  
  88. IERS DOMES Number : (A9)
  89. This is strictly required. See
  90. http://itrf.ensg.ign.fr/domes_request.php to obtain one.
  91.  
  92. Monument Description : (PILLAR/BRASS PLATE/STEEL MAST/FICTIVE/etc)
  93. Enter one or more elements as necessary to describe the monument.
  94.  
  95. Additional Information : (multiple lines)
  96. Suggestions: electrical isolation
  97.  
  98. 2. Site Location Information
  99. -----------------------------
  100.  
  101. Approximate Position (ITRF)
  102. This should be to a one meter precision.
  103. The elevation may be given to more decimal places than F7.1. 7.1 is a
  104. minimum for the SINEX format.
  105.  
  106. 3. GNSS Receiver Information
  107. --------------------------------------
  108.  
  109. Receiver Type : (A20, from rcvr_ant.tab; see instructions)
  110. Please find your receiver in
  111. ftp://igs.org/pub/station/general/rcvr_ant.tab and use
  112. the official name, taking care to get capital letters, hyphens,
  113. etc. exactly correct. If you do not find a listing for your
  114. receiver, please notify the IGS Central Bureau
  115. (igscb@igscb.jpl.nasa.gov).
  116.  
  117. Satellite System : (GPS+GLO+GAL+BDS+QZSS+SBAS)
  118. Indicates the receiver capability with the installed firmware.
  119. Acronyms can be found in the rcvr_ant.tab standard.
  120.  
  121. Serial Number : (A20)
  122. Keep the 5 significant characters of the serial number field in
  123. SINEX in mind: do not enter "S/N 12345" instead of "12345" since
  124. valuable information will be lost.
  125.  
  126. Firmware Version : (A11)
  127. Keep the 11 significant characters of the field in SINEX in mind.
  128.  
  129. Elevation Cutoff Setting : (deg)
  130. Please respond with the tracking cutoff as set in the receiver,
  131. regardless of terrain or obstructions in the area.
  132.  
  133. Temperature Stabiliz. : (none or tolerance in degrees C.)
  134. This refers to the temperature of the room in which the receiver
  135. is housed.
  136.  
  137. Date Removed : (CCYY-MM-DDThh:mmZ)
  138. In the block for the receiver currently in operation, leave this
  139. line as is to remind yourself of the format when the next receiver
  140. change is made.
  141.  
  142. 4. GNSS Antenna Information
  143. ---------------------------------------
  144.  
  145. Antenna Type : (A20 from rcvr_ant.tab; see instructions)
  146. Please find your antenna in
  147. ftp://igs.org/pub/station/general/rcvr_ant.tab and
  148. use the official name, taking care to get capital letters, hyphens,
  149. etc. exactly correct. If you do not find a listing for your
  150. antenna, please notify the IGS Central Bureau
  151. (igscb@igscb.jpl.nasa.gov). Please do not use antenna names from a
  152. "Previously valid" section. Choose the corresponding new antenna
  153. name instead. The radome code from rcvr_ant.tab must be indicated
  154. in columns 17-20 of the Antenna Type, use "NONE" if no radome is
  155. installed.
  156.  
  157. The antenna+radome pair must have an entry in
  158. ftp://igs.org/pub/station/general/igs08.atx with zenith-
  159. and azimuth-dependent calibration values down to the horizon. If not,
  160. notify the CB.
  161.  
  162. Serial Number : (A20)
  163. Keep the 5 significant characters of the serial number field in
  164. SINEX in mind: do not enter "S/N 12345" instead of "12345" since
  165. valuable information will be lost.
  166.  
  167. Antenna Reference Point : (BPA/BCR/XXX from "antenna.gra"; see instructions)
  168. Locate your antenna in the file
  169. ftp://igs.org/pub/station/general/antenna.gra
  170. Indicate the three-letter abbreviation for the point which is
  171. indicated equivalent to ARP for your antenna. Contact the Central
  172. Bureau (igscb@igscb.jpl.nasa.gov) if your antenna does not appear.
  173.  
  174. Marker->ARP Up Ecc. (m) : (F8.4)
  175. This is the antenna height measured to an accuracy of 1mm
  176. and defined as the vertical distance of the ARP from the marker
  177. described in section 1.
  178.  
  179. Marker->ARP North Ecc(m) : (F8.4)
  180. Marker->ARP East Ecc(m) : (F8.4)
  181. These must be filled in if nonzero.
  182.  
  183. Alignment from True N : (deg; + is clockwise/east)
  184. The positive direction is clockwise, so that due east
  185. would be equivalent to a response of "+90"
  186.  
  187. Antenna Radome Type : (A4 from rcvr_ant.tab; see instructions)
  188. Place a Radome code from
  189. ftp://igs.org/pub/station/general/rcvr_ant.tab here.
  190. "NONE" indicates there is no external radome. If an antenna has
  191. a cover which is integral and not ordinarily removable by the
  192. user, it is considered part of the antenna and "NONE" is to
  193. be used for the radome code. The radome code used here has to be
  194. the same as the one in the columns 17-20 of the Antenna Type
  195.  
  196. Date Removed : (CCYY-MM-DDThh:mmZ)
  197. In the block for the antenna currently in operation, leave this
  198. line as is to remind yourself of the format when the next antenna
  199. change is made.
  200.  
  201. 5. Surveyed Local Ties
  202. -------------------------------------------------------------
  203. Local ties to other markers on the site should be determined in ITRF
  204. coordinates to 1mm precision in all 3 dimensions. Offsets are given
  205. in geocentric Cartesian coordinates (ITRF).
  206.  
  207. 8. Meteorological Instrumentation
  208. -------------------------------------------------------------
  209. Height Diff to Ant : (m)
  210. Positive numbers indicate meteorological instrument is ABOVE GPS antenna.
  211.  
  212. 12. Responsible Agency (if different from 11.)
  213. -------------------------------------------------------------
  214. The primary contacts listed here should always be the first choice for
  215. questions about operation of the site. This person will receive
  216. automated emails regarding site log or RINEX errors and should be
  217. someone who can answer questions about the configuration and data
  218. delivery for this site.
  219.  
  220. 13. More Information
  221. -------------------------------------------------------------
  222. Primary Data Center :
  223. Secondary Data Center :
  224. Please list the DC where the station's data ordinarily goes first as
  225. "Primary." Use "Secondary" either for a second location where
  226. the station's data always goes, or would go in the case of a
  227. long-term failure with the Primary DC.
  228.  
  229. Select primary and secondary data centers via centers.html and enter
  230. the abbreviation of the DC name. A geographically-
  231. or functionally- related center is generally preferred. The secondary DC
  232. is where data would be sent if the primary were unavailable for an extended
  233. period. The switchover does not need to be automated, but data transfer
  234. procedures should be verified.
  235.  
  236. URL for More Information :
  237. This will be linked on the igscb's page for this site. It is
  238. not necessary to include "http://".
  239.  
  240. Photos are mandatory. Send all available photos of antenna, radome,
  241. placement and all relevant photos to the CB. Contact the CB if you have photos
  242. which cannot be hosted on a site web page.
  243.  
  244.  
  245. Additional Information:
  246. Anything you feel is important. Some possibilities to consider are:
  247. - Elevation mask table indicating physical mask effects such as
  248. AZ ELEV AZ ELEV AZ ELEV AZ ELEV
  249. 10 8 20 12 30 10 40 8
  250. 50 5 60 12 70 8 80 8
  251. 90 5 100 5 110 5 120 5
  252. 130 5 140 5 150 8 160 8
  253. 170 5 180 3 190 5 200 8
  254. 210 8 220 8 230 5 240 5
  255. 250 5 260 8 270 10 280 12
  256. 290 12 300 12 310 12 320 8
  257. 330 5 340 5 350 8 360 8
  258. (This could also be kept at your local www site and referred to
  259. by URL in the log).
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!