391:
I didn't create the current rows, but they actually make sense to me: they basically describe the reception characteristics. Satellite services have weak sources, and they're moving, so you need a view of a good chunk of sky area, but they work worldwide. Longwave penetrate buildings well. Defunct
453:
trying to think about a good name of similar length to the current ones, "Multi-source" might not be a bad category name. I'm going through a lot of words: secondary, piggyback, convenience, low-precision, auxiliary, common, protocol, standardized, But the fact that there are multiple independent
399:
You're right that defunct can be considered a different dimension rather than a navbox row, but it's nice that it produces a reasonable sized group, and I think it ends up being comprehensible and useful to the reader, even if not perfectly consistent (Besides, I just got through an argument about
395:
Of course, another point for the current rows is that they are reasonably evenly balanced. That's an editorial/wikipedia factor more than a technical one, but also important to making a navbox useful to a reader for navigation. A bunch of single-item categories and everything else lumped together
345:
RDS CT is a service not bound to a single station, although a user will most probably use a single station to receive it at a given time. GPS/GLONASS etc. are not bound to a single station either, these are services using multiple transmitters at the same time. Both are - in different ways - quite
376:
And, as you say, the existence of articles is also a factor. Are we listing time signals, or wikipedia articles? Really, it's both, and again there's no simple rule; you're trying to find a defensible threshold of notability, where the existence of an article is a major factor, but not the only
349:
Thinking about it, rows like "xyz wave", "satellite" and "defunct" discuss completely different qualities. So, perhaps we could solve the problem by renaming the template from "stations" to "services" and regroup the information into "stationary" (sub-divided into "xyz wave"), "satellite", ... or
433:
Piggyback protocols are prone to suffering from unnoticed errors and outages, because they're very much a minor "convenience" feature dependent on the individual station to get right And it can be hard to find who's responsible for fixing it if it's wrong. With the exception of CDMA, which is
422:"GPS/GLONASS etc. are not bound to a single station either, these are services using multiple transmitters at the same time. Both are - in different ways - quite different from the other stationary time signal services." Yes, which is exactly why they're in a separate category. And they're
372:
information gets lost among the clutter. There's no simple rule; you just have to look for a good sized gap or jump in relevance which is also at a suitable distance. If the rules were simply "time dissemination" and "radio broadcast", I'd also have to mention top-of-the-hour station
341:
Hi! I see your point but I think the purpose of navigation boxes is to help find related information. It should be up to the reader to decide if the quality is good enough or nor. Perhaps with the exception of "really obscure stuff"(tm), existance should be enough to include it in a
140:
I see that WWV and WWVB are identified by the US flag, but WWVH is identified by the
Hawaiian flag. If there is a reason why WWVH should use the Hawaiian flag instead of the US flag, then why doesn't it apply to using the flag of Colorado to identify WWV and WWVB?
287:
While GPS and GLONASS aren't single transmitters, they are centrally administered and arguably a single "station" with multiple transmitters, not unlike many commercial radio and TV stations, or JJY. (Even WWVB has two transmitters, although very close.)
283:
prominence. It's a whole category, far worse than everything else listed, and not a station. Put together, my take on those three factors is "doesn't belong here". (It's also not a dedicated time service, but that's a lesser factor in my view.)
121:
page to illustrate the difference in layout between the old and new versions. There's no real reason to use a column layout here; the standard navbox layout works fine. I reckon the sandbox version should be deployed.
350:"primary", "secondary", ... (TBD)? "Defunct" should not be a separate group at all, but be indicated by an attribute (coded by color, italics, underline etc.) "Dedicated" could be another attribute. --
326:(Arguably, TDF belongs in this category, but I'm inclined to leave it alone, since the time signal is much more strongly separated from the underlying transmission than these other systems.)
169:
241:
384:
time signal that's significantly different from the existing collection, but not following a new consistent inclusion rule. I'd be much happier with a new row with
434:
actually used for precise timing, they also tend to have crappy accuracy. I see a distinct category there; the challenge is to find a short descriptive label.
261:
39:
463:
445:
359:
392:
can't be received at all. "Piggybacked time signal" works well in this, because you have to be able to receive the "main" signal to get a time code.
252:
Thanks for the heads-up, and I hope for more, but until there's an article about it, or at least a lot more information, there's not much to do.
335:
245:
411:
finding a name for each group. (If I wanted to be pedantic, I could argue that HBG doesn't belong in longwave or shortwave because it doesn't
199:
74:
187:
454:
generators of the same code is perhaps the most significant characteristic of the group, and one that includes high-precision CDMA.
204:
Given the conflict with the standard navboxes on most pages where they are used, really these templates should use default width.
118:
316:
80:
237:
130:
455:
437:
327:
279:
My objection is that a whole category ("Ultrashortwave") for one frankly-bad (100 ms accuracy) time service is giving it
253:
213:
267:
150:
107:
221:
295:
support, OTOH, is a category of non-dedicated/secondary/piggybacked (wording TBD) radio time services. RDS-CT,
320:
20:
69:
24:
276:
added it, I removed it, and he (I'm assuming, based on the name) re-added it, it's time for a discussion...
60:
135:
426:
in that category because they're much more like each other than they are like other categories. They
388:
entries unless you can argue that a particular time code is really unique (e.g. optical frequencies).
430:
use multiple satellites to get continuous coverage, they all have one controlling organization, etc.
404:
entries on a navbox and the votes went to "better to not list it at all than such ugly typography.")
407:
Basically, don't get hung up on the wavelength; what we're going is finding a useful grouping and
459:
441:
331:
257:
368:
I agree about the purpose of a navbox, but you have to have a boundary around "related". or the
355:
312:
296:
127:
233:
209:
181:
160:
8:
50:
98:
I shall add pages for OLB5 and Y3S former stations and for HD2IOA (Equador Navy) soon.
65:
351:
273:
173:
145:
93:
46:
300:
123:
280:
205:
178:
103:
112:
227:
304:
193:
144:
Not to cause a ruckus, but I am curious about the apparent inconsistency. â–
308:
99:
319:, page 63: 6.4.3.9 Time and date information data entity - type 8),
226:
Is there also a time signal station in China, working on 77.5 kHz (
419:
transmission characteristics, not historical ones like KK2XEI.)
172:
lists Hawaii separate from the
Continental United States on its
346:
different from the other stationary time signal services.
15:
380:My complaint is particularly that you're including
200:Template_talk:Satellite_navigation_systems#Width
228:https://www.youtube.com/watch?v=ZrB1MQrDu9k
163:comment added 04:53, 22 April 2010 (UTC).
170:North American Shortwave Association
23:for discussing improvements to the
13:
14:
477:
303:p.13), time-from-CDMA receivers (
40:Click here to start a new topic.
214:08:31, 25 September 2010 (UTC)
124:Chris Cunningham (not at work)
1:
415:a wavelength. We're listing
311:), the optional time code in
108:15:21, 13 February 2008 (UTC)
37:Put new text under old text.
246:06:00, 7 February 2015 (UTC)
188:01:02, 1 February 2011 (UTC)
131:03:03, 25 October 2009 (UTC)
7:
45:New to Knowledge? Welcome!
10:
482:
268:On the inclusion of RDS CT
222:Further stations in China
75:Be welcoming to newcomers
464:23:42, 26 May 2015 (UTC)
446:22:34, 26 May 2015 (UTC)
360:15:07, 26 May 2015 (UTC)
336:13:28, 26 May 2015 (UTC)
299:(time code described in
262:13:34, 26 May 2015 (UTC)
313:Digital Radio Mondiale
297:Extended Data Services
70:avoid personal attacks
155:2010-04-22T04:53:28Z
25:Time signal stations
301:this NIST document
136:US v. Hawaii flags
81:dispute resolution
42:
274:User:Matthiaspaul
248:
236:comment added by
91:
90:
61:Assume good faith
38:
473:
231:
186:
164:
157:
156:
16:
481:
480:
476:
475:
474:
472:
471:
470:
403:
373:identification.
270:
224:
196:
177:
158:
154:
153:
148:
138:
117:I've started a
115:
96:
87:
86:
56:
12:
11:
5:
479:
469:
468:
467:
466:
448:
435:
431:
420:
405:
401:
397:
393:
389:
378:
374:
363:
362:
347:
343:
269:
266:
265:
264:
238:217.228.18.162
223:
220:
218:
195:
192:
191:
190:
149:
137:
134:
114:
111:
95:
92:
89:
88:
85:
84:
77:
72:
63:
57:
55:
54:
43:
34:
33:
30:
29:
28:
9:
6:
4:
3:
2:
478:
465:
461:
457:
456:71.41.210.146
452:
449:
447:
443:
439:
438:71.41.210.146
436:
432:
429:
425:
421:
418:
414:
410:
406:
398:
396:isn't useful.
394:
390:
387:
383:
379:
375:
371:
367:
366:
365:
364:
361:
357:
353:
348:
344:
340:
339:
338:
337:
333:
329:
328:71.41.210.146
324:
322:
318:
314:
310:
306:
302:
298:
294:
289:
285:
282:
277:
275:
263:
259:
255:
254:71.41.210.146
251:
250:
249:
247:
243:
239:
235:
229:
219:
216:
215:
211:
207:
202:
201:
189:
185:
184:
180:
175:
174:country list.
171:
167:
166:
165:
162:
152:
147:
142:
133:
132:
129:
125:
120:
110:
109:
105:
101:
82:
78:
76:
73:
71:
67:
64:
62:
59:
58:
52:
48:
47:Learn to edit
44:
41:
36:
35:
32:
31:
26:
22:
18:
17:
450:
427:
423:
416:
412:
408:
385:
381:
369:
352:Matthiaspaul
325:
292:
290:
286:
278:
271:
232:— Preceding
225:
217:
203:
197:
182:
168:Because the
146:NeoAmsterdam
143:
139:
116:
97:
19:This is the
281:unwarranted
159:—Preceding
400:my use of
321:Marine AIS
206:ChiZeroOne
119:test cases
402:struckout
94:New pages
83:if needed
66:Be polite
27:template.
21:talk page
424:together
317:the spec
309:CellSync
234:unsigned
179:Denelson
51:get help
417:current
386:several
370:desired
342:navbox.
323:, etc.
291:What I
161:undated
305:EndRun
272:Since
113:Layout
293:would
194:Width
151:Edits
100:Sv1xv
79:Seek
460:talk
451:P.S.
442:talk
413:have
409:then
377:one.
356:talk
332:talk
307:and
258:talk
242:talk
230:)?
210:talk
198:Re:
128:talk
104:talk
68:and
428:all
382:one
176:--
462:)
444:)
358:)
334:)
260:)
244:)
212:)
183:83
126:-
106:)
49:;
458:(
440:(
354:(
330:(
315:(
256:(
240:(
208:(
102:(
53:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.