/
index.html.twig
184 lines (179 loc) · 11.8 KB
/
index.html.twig
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
{% extends 'main.html.twig' %}
{# This could use some work #}
{% block body %}
<div class="main">
<div class="links quicklinks">
Quick Links [
<a href='#listenerEdit'>Editing Listener Details</a> |
<a href='#addLogs'>Add Log Data</a> |
<a href='#confirmDetails'>Confirm Details</a>
]
</div>
<h1>Administrator Help</h1>
{% include 'status.html.twig' %}
<p>This page extends from the standard help available to all users.</p>
<h2 class="margin-top-2" id="listenerEdit">Editing Listener Details <small>[ <a href='#top'><strong>Top</strong></a> ]</small></h2>
<p>The Listeners page works as for ordinary users but with these additional features for Administrators:</p>
<ul>
<li>To delete a listener, click the <strong>Delete</strong> link at the end of the appropriate row.
Deleting a listener also deletes their entire logbook, so make sure that you really want to do this.
</li>
<li>To edit listener details, find the listener you wish to edit and click on the name to open the <strong>Listener Profile</strong> screen.
Ordinary users can't change the values here, but administrators can. Remember to <strong>save</strong> your changes.
</li>
<li>To add a new listener, click the Add Listener... button at the bottom of the Listener List and complete the profile form for the listener.
If you have co-ordinates but no grid square for them, use the GSQ converter on the Tools page.
</li>
<li>Use the NDBList approved <a href="{{ path('countries', { 'system' : system, 'filter' : '*' }) }}" data-popup="1">3-letter country codes</a> -
eg <strong>SWE</strong> not S for Sweden, <strong>BRA</strong> not B for Brazil.
</li>
</ul>
<h2 class="margin-top-2" id="addLogs">Add Log Data <small>[ <a href='#top'><strong>Top</strong></a> ]</small></h2>
<p>This function is available by selecting a listener from the Listeners list and clicking on the <strong>Add Log...</strong> link for that listener.<br />
The system adds logs in two phases: <strong>Parse Log</strong> and <strong>Confirm Details</strong>.</p>
<h3>Parse Log</h3>
<p>This phase takes text text containing log entries and prepares to extract data into the standard fields used by the system.
Each listener may have adifferent way of presenting his or her log data and the trick part about the process is defining
the format they have used so that the log data will be correctly interpretted by the Log Upload system.
</p>
<p>
The field on top of the main text area (shaded grey) is the 'Text Format' field and holds the text format defining
how the log data is to be parsed. The values set in this field are saved each time a log is parsed.
</p>
<p>
The log import facility ignores all fields other than those shown below. It is a very good idea to place some extra
spaces and an X at the end of the list as otherwise the contents of the last field may be cropped (e.g. DI shown as Ident instead of DIW).
</p>
<h3 class="h3">Log Format Tokens</h3>
<p>
Here is the full list of field codes that are recognised by the system (these are all CASE SENSITIVE) and Date fields are shown in the table below:
</p>
<h4>Signal Identifiers</h4>
<ul>
<li><b>KHZ</b> Frequency in Kilohertz - the nominal carrier frequency.</li>
<li><b>MHZ</b> Frequency in Megahertz - typically used with HF, VHF and UHF beacon logs.</li>
<li><b>ID</b> The Callsign, or in the case of DGPS stations, the Reference Station Identifier (always prefixed with a #) for the station.</li>
<li><b>GSQ</b> The Grid Square for the beacon - only used when extracting data to add new beacons.</li>
<li><b>PWR</b> The power in watts for the beacon - only used when extracting data to add new beacons.</li>
<li><b>QTH</b> The location for the beacon - only used when extracting data to add new beacons.</li>
<li><b>SP</b> The State or Province for the beacon (USA, Canada and Australia only) - only used when extracting data to add new beacons.</li>
<li><b>ITU</b> The NDBList 3-letter country code for the beacon (e.g. BRA, SWE, ENG) - only used when extracting data to add new beacons.</li>
</ul>
<h4>Log Date - Simple date tokens</h4>
<p>The following tokens can be used in any order to indicate the date for a given logging.<br />
They can also be combined without spaces between them to extract a date from a single combined date column:</p>
<ul>
<li><b>D</b> (one digit for dates 1-9) or <b>DD</b> (two digits, with leading zero for dates 1-9)</li>
<li><b>M</b> (one digit for months 1-9), <b>MM</b> (two digits, with leading zero for months 1-9) or <b>MMM</b> (first 3 letters of month name)</li>
<li><b>YY</b> (two-digit year) or <b>YYYY</b> (four-digit year)</li>
</ul>
<h4>Log Date - Combined date tokens (Date and Month only - you will be prompted for the Year)</h4>
<p>These extract the date from a combined date column having any of these single-character delimiters: <b>.,;:/|\+-*#$%^~</b></p>
<ul class="monospace">
<li><b>D.M</b> <b>DD.M</b> <b>D.MM</b>
<b>DD.MM</b> <b>D.MMM</b> <b>DD.MMM</b>
</li>
<li><b>M.D</b> <b>M.DD</b> <b>MM.D</b>
<b>MM.DD</b> <b>MMM.D</b> <b>MMM.DD</b>
</li>
</ul>
<h4>Log Date - Combined date tokens (with Year)</h4>
<p>These extract the date from a combined date column having any of these single-character delimiters: <b>.,;:/|\+-*#$%^~</b></p>
<ul class="monospace">
<li><b>DD.MM.YY</b> <b>DD.YY.MM</b> <b>DD.MMM.YY</b>
<b>DD.YY.MMM</b> <b>DD.MM.YYYY</b> <b>DD.YYYY.MM</b>
<b>DD.MMM.YYYY</b> <b>DD.YYYY.MMM</b>
</li>
<li><b>MM.DD.YY</b> <b>MM.YY.DD</b> <b>MMM.DD.YY</b>
<b>MMM.YY.DD</b> <b>MM.DD.YYYY</b> <b>MM.YYYY.DD</b>
<b>MMM.DD.YYYY</b> <b>MMM.YYYY.DD</b>
</li>
<li><b>YY.DD.MM</b> <b>YY.MM.DD</b> <b>YY.DD.MMM</b>
<b>YY.MMM.DD</b> <b>YYYY.DD.MM</b> <b>YYYY.MM.DD</b>
<b>YYYY.DD.MMM</b> <b>YYYY.MMM.DD</b>
</li>
</ul>
<h4>Log Time</h4>
<ul>
<li><b>hh:mm</b> The time in UTC when the station was heard, hours and minutes with leading zeros where required (note that these field names are lower case).</li>
<li><b>hhmm</b> As hh:mm, but without the colon separator between hours and minutes (note that these field names are lower case).</li>
</ul>
<h4>Reported Offsets</h4>
<ul>
<li><b>LSB</b> The frequency offset from the nominal carrier frequency for the lower sizeband.</li>
<li><b>USB</b> The frequency offset from the nominal carrier frequency for the upper sizeband.</li>
<li><b>~LSB</b> An approximate frequency offset from the nominal carrier frequency for the lower sizeband.</li>
<li><b>~USB</b> An approximate frequency offset from the nominal carrier frequency for the upper sizeband.</li>
<li><b>+SB-</b> This signifies either one or two separate values using + or - to indicate USB or LSB relative
to the nominal carrier frequency, with ~ to indicate where specific values are approximate.<br />
Examples:
<ul class="no-bullet margin-left-2">
<li>+1023 -1034</li>
<li>~+1023 1034-</li>
<li>-1034 ~1023+</li>
<li>+1022-</li>
</ul>
</li>
<li><b>+~SB-</b> As <b>+SB-</b> ecept that values are approximate. This means that values are included in individual
users logs and in station logs, but are shown prefixed with ~. Also, these values are not used to update the latest
USB and LSB values for the beacon itself, since the accuracy is not sufficient.<br />
Examples:
<ul class="no-bullet margin-left-2">
<li>+1020 -1020</li>
<li>+1020 1020-</li>
<li>-1020 1020+</li>
<li>+1020-</li>
</ul>
</li>
<li><b>+K-</b> Brian Keyte's log format shows values of 0.4 to signify LSB and USB of 400Hz,
while 1 signifies LSB and USB of 1020Hz. A leading + or - signifies only the upper or lower sideband heard.
All values are regarded as approximate.<br />
Examples:
<ul class="no-bullet margin-left-2">
<li>0.4</li>
<li>+0.4</li>
<li>1</li>
<li>-1</li>
</ul>
</li>
<li><b>ABS</b> This signifies either one or two separate values as decimal KHz to indicate absolute values
for USB or LSB respecively.<br />
Examples:
<ul class="no-bullet margin-left-2">
<li>199.023 197.966</li>
<li>199.023</li>
<li>197.966</li>
</ul>
</li>
<li><b>~ABS</b> As ABS but offset values are all considered approximate.</li>
</ul>
<h4>Other Loggable details</h4>
<ul>
<li><b>sec</b> Used to input time for an ident cycle in seconds - where cycles are shown as aa/bb the first
digits indicate the length of the time for the ident code minus any trailing long dash (or dashes), the second
indicates the total time for each repeat.
</li>
<li><b>fmt</b> Used to input the format of a signal - DAID=Dash after ID, DBID=dash before ID, DA2ID=Dash after 2xIDs etc.
These formats are also recognised and parsed if they are contained within a +SB- block - e.g:
<strong>-1040 +1040 DAID</strong>
</li>
<li><b>X</b> Signifies start of one or more fields to be ignored by the log upload facility.</li>
</ul>
<h2 class="margin-top-2" id="confirmDetails">Confirm Details <small>[ <a href='#top'><strong>Top</strong></a> ]</small></h2>
<p>This phase displays the data extracted in the Parse Log phase within a data-grid to allow the user to ensure that the log data was correctly parsed.</p>
<p>If the data-grid reveals errors in parsed data, the user should press the link provided to go back to the previous phase and make corrections as required.</p>
<p>The data grid also indicates which stations shown are new to the database - particular attention should be taken to these entries to ensure that
the details for Frequency and ID are correctly entered.
You will need to add beacons if these are not in the database by using the <strong>Add...</strong> button if the beacon doesn't already appear in the database.</p>
<p>Once you are satisfied that the data entered is correct, they should press the Submit button to update the database.</p>
</div>
<style>
a { text-decoration: underline !important; }
b { color: #0000ff; background: #e0e0ff; font-family: "Courier New", Courier, monospace }
</style>
<script>
$(document).ready( function() {
setExternalLinks();
});
</script>
{% endblock %}