forked from Novean-Institute-of-Standards/NIS-Standards
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathNIS.html
1016 lines (876 loc) · 42.5 KB
/
NIS.html
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
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="generator" content="crowbook">
<meta name="viewport" content="width=device-width">
<meta name="author" content="Novean Institute of Standards">
<title>NIS Standards</title>
<style type = "text/css">
body {
font-family: "Linux Libertine", "Georgia", serif;
text-align: justify;
font-size: 100%;
}
p {
text-indent: 1.25em;
margin:0;
hyphens: auto;
}
blockquote {
margin: 1em;
font-style: italic;
}
code {
font-size: 80%;
font-family: "Linux Libertine Mono", monospace;
background-color: #F0F0F0;
}
pre {
font-family: "Linux Libertine Mono", monospace;
margin: 1em;
padding-top: 0;
background-color: #F0F0F0;
white-space: pre-wrap;
word-wrap: break-word;
}
/* Try to disable hyphenation in titles */
h1, h2, h3, h4, h5, h5 {
adobe-hyphenate: none;
-ms-hyphens: none; /* Trident (Windows) */
-moz-hyphens: none; /* Gecko (Firefox) */
-webkit-hyphens: none; /* Webkit */
-epub-hyphens: none; /* EPUB 3 */
hyphens: none; /* Futur standard */
}
h1, h2, h3, h4, h5, h6 {
text-align: left;
font-family: Linux Biolinum, sans-serif;
font-variant: small-caps;
}
/* Title of a part */
h1.part {
font-size: 250%;
text-align: center;
}
/* The `Part X` section of a part */
h2.part {
font-size: 175%;
text-align: center;
}
/* The "Chapter X" section of a chapter */
span.chapter-header {
font-size: 75%;
}
/* Title of the book */
h1.title {
text-align: center;
font-size: 300%;
}
/* Author */
h2.author {
text-align: right;
font-size: 200%;
}
/* Subtitle */
h2.subtitle {
text-align: center;
font-size: 200%;
}
/* When toc is displayed inlined */
#toc ol, #toc ul {
padding: 0;
margin-left: 1em;
}
#toc li {
list-style-type: none;
margin: 0; padding: 0;
}
#toc li:before {
content: none;
}
#cover img {
width: 100%;
max-height: 100%;
}
.image {
margin: auto;
width: 80%;
}
.image img {
width: 100%;
max-height: 100%;
}
.rule {
text-align: center !important;
margin-top: 1em;
margin-bottom: 1em;
font-weight: bold;
page-break-inside: avoid;
break-inside: avoid;
page-break-after: avoid;
break-after: avoid;
}
/* The number of the note in an expanded footnote (e.g. [3]) */
.note-number {
font-weight: bold;
margin-right: 1em;
}
td.note-number {
vertical-align: top;
}
/* When footnotes (try to) be diplayed as margin notes */
.sidenote {
display: block;
float: right;
width: 30%;
border: 1px solid black;
margin: 1em;
padding: .5em;
margin-right: -1.5em;
}
.sidenote .note-number {
float: left;
}
/* The div class displaying notes at the end of a chapter */
div.notes {
text-align: justify;
border-top: thin dashed black;
margin-top: 1em;
}
table.notes {
border-collapse: collapse;
border-style: hidden;
}
table.notes tr td {
margin-left: 1em;
margin-right: 1em;
}
table.notes tr td p {
text-indent: 0;
}
/* Every markdown table is included in a <div class = "table"> */
.table {
margin: 1em;
}
.table table {
width: 80%;
margin: 0 auto;
border-style: solid;
border-width: thin;
border-color: black;
border-collapse: collapse;
}
.table table th, .table table td {
border-style: solid;
border-width: 1px;
text-align: center;
}
.table table th {
font-weight: bold;
font-variant: small-caps;
}
span.initial {
float: left;
font-size: 285%;
font-weight: bold;
margin-right: 0.05em;
line-height: 0.8em;
}
p.first-para {
text-indent: 0;
}
/* Use this for escape narrow space so it is non-breaking */
.nnbsp {
/* white-space: nowrap;*/
word-spacing: -0.13em;
/* Following necessary for Kobo EPUB3 reader??? */
margin: 0;
padding: 0;
}
/* Default HTML CSS file includes default EPUB CSS file */
/* Colors for the navigation menu (toc) */
nav {
background: #CBBFCC;
color: black;
border-right-color: black;
}
#nav a:link {
color: black;
}
#nav a:visited {
color: black;
}
/* Colors for top and footer */
#top {
background-color: #444343;
color: white;
}
footer {
background-color: #444343;
color: white;
}
footer a, #top a {
color: #fc71ff;
}
footer a:hover, #top a:hover {
color: #b743fe;
}
/* Additional elements, only use for proofreading */
/* Grammar error */
.grammar-error {
color: red;
text-decoration-line: underline;
text-decoration-style: double;
/* background: #d966ff;*/
}
p.first-para:first-letter {
font-size: 300%;
float: left;
font-weight: bold;
margin-right: 0.05em;
line-height: 1em;
}
/* The nav element corresponding to the navigation menu */
nav {
z-index: 2;
position: fixed;
left: 0;
top: 0;
bottom: 0;
width: 20%;
overflow-y: auto;
font-size: 80%;
margin-left: 0;
border-right-width: 2px;
border-right-style: dashed;
}
#nav code {
background-color: transparent;
}
#nav a:link {
text-decoration: none;
}
#nav a:visited {
text-decoration: none;
}
#nav {
text-align: left;
}
#nav h2 {
text-align: center;
}
#nav li {
list-style-type: none;
text-indent: -1em;
}
#nav li:before {
content: none;
}
#nav ul {
padding-right: 1em;
padding-left: 1.5em;
}
/* The menu containing the button to display the navigation bar */
#menu {
position: fixed;
z-index: 2;
top: 0em;
left: 1em;
transition: left 1s;
}
#menu img {
opacity: 0.5;
}
#menu img:hover {
opacity: 1.0;
cursor: pointer;
}
#menu-button {
height: 1.5em;
padding: 0.5em;
}
#book-button {
height: 1.5em;
padding: 0.5em;
float: left;
}
/* Hide navigation bar */
#nav {
left: -21%;
transition: left 1s;
}
/* The main content of the book */
#content {
overflow-y: auto;
margin-left: 0;
margin-right: 0;
margin-top: 0;
margin-bottom: 0;
transition: margin-left 1s;
}
/* Used for multifiles HTML */
.prev_chapter {
text-align: left;
text-indent: 0;
margin-bottom: 1em;
font-size: 120%;
font-variant: small-caps;
font-weight: bold;
}
.next_chapter {
text-align: right;
margin-top: 1em;
margin-bottom: 1em;
font-size: 120%;
font-variant: small-caps;
font-weight: bold;
}
/* Improving readability for the HTML format only */
p, blockquote, li, .image {
margin-right: auto;
max-width: 33em;
}
blockquote {
padding: 1em;
}
#content {
text-align: center;
}
#page {
display: inline-block;
text-align: justify;
max-width: 33em;
}
#nav-container {
top: 0;
width: 100%;
}
#nav-title {
top: 0;
}
#toolbar {
top: 0;
float: left;
}
#toolbar img {
cursor: pointer;
}
footer {
margin-top: 2em;
margin-bottom: 0;
}
#top {
margin-top: 0;
margin-bottom: 1em;
}
#top p {
font-family: "Linux Biolinum";
font-weight: bold;
font-variant: small-caps;
}
footer, #top {
padding-top: .25em;
padding-bottom: .25em;
margin-left: 0;
margin-right: 0;
text-align: center;
transition: margin-left 1s;
}
footer a, #top a {
text-decoration: none;
}
footer p, #top p {
text-indent: 0;
margin-left: auto;
margin-right: auto;
margin-bottom: 0.5em;
margin-top: 0.5em;
max-width: 33em;
}
</style>
<style type = "text/css" media = "print">
#page {
display: block;
}
.chapter {
page-break-before: always;
}
#menu {
display: none;
}
#nav {
display: none;
}
</style>
<script>
function on(name) {
var elements = document.getElementsByClassName(name);
for (var i = 0; i < elements.length; i++) {
var elem = elements[i];
elem.style.backgroundColor = "pink";
}
}
function off(name) {
var elements = document.getElementsByClassName(name);
for (var i = 0; i < elements.length; i++) {
var elem = elements[i];
elem.style.backgroundColor = "white";
}
}
var display_menu = false;
function toggle() {
if (display_menu == true) {
display_menu = false;
document.getElementById("nav").style.left = "-21%";
document.getElementById("content").style.marginLeft = "0%";
document.getElementById("menu").style.left = "1em";
/* if(document.getElementById("top")) {
document.getElementById("top").style.left = "0";
}
if(document.getElementById("footer")) {
document.getElementById("footer").style.marginLeft = "0%";
}*/
} else {
display_menu = true;
document.getElementById("nav").style.left = "0";
document.getElementById("content").style.marginLeft = "20%";
document.getElementById("menu").style.left = "20%";
/* if(document.getElementById("top")) {
document.getElementById("top").style.left = "20%";
}
if(document.getElementById("footer")) {
document.getElementById("footer").style.marginLeft = "20%";
}*/
}
}
</script>
</head>
<body>
<script type = 'application/ld+json'>
{
"@context": "http://schema.org/",
"@type": "Book",
"author": "Novean Institute of Standards",
"name": "NIS Standards",
"version": "0.0.0",
"about": "The NIS Standards for Aviation and Port Interchange Procedures",
"inLanguage": "en"
}
</script>
<nav id = "nav">
<div id = "nav-title">
<h2><a href = "#link-0">NIS Standards</a></h2>
</div>
<ul>
<li><a href="#link-1">Acknowledgements</a></li>
<li><a href="#link-2">Introduction</a></li>
<li><a href="#link-3">Guidelines</a>
<ul><li><a href="#link-4">1.1. Changing Standards</a>
<ul><li><a href="#link-5">1.1.1. What is a SIP?</a></li>
<li><a href="#link-6">1.1.2. SIP Types</a></li>
<li><a href="#link-7">1.1.3. SIP Workflow</a></li>
</ul>
</li>
<li><a href="#link-8">1.2. Writing and Formatting</a>
<ul><li><a href="#link-9">1.2.1. SIP Formatting</a>
<ul><li><a href="#link-10">1.2.1.1. Terms</a></li>
<li><a href="#link-11">1.2.1.2. SIP Guides</a>
<ul><li><a href="#link-12">1.2.1.2.1. Fundamentals SIP</a></li>
<li><a href="#link-13">1.2.1.2.2. Recommendation SIP</a></li>
<li><a href="#link-14">1.2.1.2.3. Emergency SIP</a></li>
<li><a href="#link-15">1.2.1.2.4. Errata SIP</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li><a href="#link-16">1.3. Appeals</a></li>
</ul>
</li>
<li><a href="#link-17">Identification</a>
<ul><li><a href="#link-18">2.1. Semiotics</a>
<ul><li><a href="#link-19">2.1.1. Flagging</a></li>
<li><a href="#link-20">2.1.2. Signs</a>
<ul><li><a href="#link-21">2.1.2.1. Atmospheric Signs</a></li>
<li><a href="#link-22">2.1.2.2. Atmospheric Billboards</a></li>
<li><a href="#link-23">2.1.2.3. Space Signs</a></li>
<li><a href="#link-24">2.1.2.4. Space Billboards</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li><a href="#link-25">Navigation</a>
<ul><li><a href="#link-26">3.1. Port Interchange Protocol: 1ST DRAFT - PROPOSAL</a>
<ul><li><a href="#link-27">3.1.1. Introduction</a>
<ul><li><a href="#link-28">3.1.1.1. Motivation</a></li>
<li><a href="#link-29">3.1.1.2. Key Concepts</a></li>
<li><a href="#link-30">3.1.1.3. Issues not addressed by this proposal</a></li>
</ul>
</li>
<li><a href="#link-31">3.1.2. The Port Interchange</a>
<ul><li><a href="#link-32">3.1.2.1. Speed Zone</a></li>
<li><a href="#link-33">3.1.2.2. Alignment Zone</a></li>
<li><a href="#link-34">3.1.2.3. Transition Zone</a>
<ul><li><a href="#link-35">3.1.2.3.1. Approach and Take-off Vectors</a></li>
<li><a href="#link-36">3.1.2.3.2. Vertical Take-off and Landing (VTOL) concepts</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="#link-37">3.1.3. Implementation</a>
<ul><li><a href="#link-38">3.1.3.1. For Pilots and Navigators</a></li>
<li><a href="#link-39">3.1.3.2. For Facility Owners</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</nav>
<div id = "content">
<div id = "top"><p id = "para-123">NIS Standards 0.0.0</p>
</div>
<div id = "page">
<header>
<div id = "menu">
<img id = "menu-button" onclick="toggle();"
src="data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9Im5vIj8+CjwhLS0gQ3JlYXRlZCB3aXRoIElua3NjYXBlIChodHRwOi8vd3d3Lmlua3NjYXBlLm9yZy8pIC0tPgoKPHN2ZwogICB4bWxuczpkYz0iaHR0cDovL3B1cmwub3JnL2RjL2VsZW1lbnRzLzEuMS8iCiAgIHhtbG5zOmNjPSJodHRwOi8vY3JlYXRpdmVjb21tb25zLm9yZy9ucyMiCiAgIHhtbG5zOnJkZj0iaHR0cDovL3d3dy53My5vcmcvMTk5OS8wMi8yMi1yZGYtc3ludGF4LW5zIyIKICAgeG1sbnM6c3ZnPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIKICAgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIgogICB4bWxuczpzb2RpcG9kaT0iaHR0cDovL3NvZGlwb2RpLnNvdXJjZWZvcmdlLm5ldC9EVEQvc29kaXBvZGktMC5kdGQiCiAgIHhtbG5zOmlua3NjYXBlPSJodHRwOi8vd3d3Lmlua3NjYXBlLm9yZy9uYW1lc3BhY2VzL2lua3NjYXBlIgogICB3aWR0aD0iMjAwbW0iCiAgIGhlaWdodD0iMjAwbW0iCiAgIHZpZXdCb3g9IjAgMCA3MDguNjYxNDIgNzA4LjY2MTQxIgogICBpZD0ic3ZnMiIKICAgdmVyc2lvbj0iMS4xIgogICBpbmtzY2FwZTp2ZXJzaW9uPSIwLjkxIHIxMzcyNSIKICAgc29kaXBvZGk6ZG9jbmFtZT0ibWVudS5zdmciPgogIDxkZWZzCiAgICAgaWQ9ImRlZnM0IiAvPgogIDxzb2RpcG9kaTpuYW1lZHZpZXcKICAgICBpZD0iYmFzZSIKICAgICBwYWdlY29sb3I9IiNmZmZmZmYiCiAgICAgYm9yZGVyY29sb3I9IiM2NjY2NjYiCiAgICAgYm9yZGVyb3BhY2l0eT0iMS4wIgogICAgIGlua3NjYXBlOnBhZ2VvcGFjaXR5PSIwLjAiCiAgICAgaW5rc2NhcGU6cGFnZXNoYWRvdz0iMiIKICAgICBpbmtzY2FwZTp6b29tPSIwLjQ5NDk3NDc1IgogICAgIGlua3NjYXBlOmN4PSIxMDUuNjEyNzUiCiAgICAgaW5rc2NhcGU6Y3k9IjQwNy4wNjM5MSIKICAgICBpbmtzY2FwZTpkb2N1bWVudC11bml0cz0icHgiCiAgICAgaW5rc2NhcGU6Y3VycmVudC1sYXllcj0ibGF5ZXIxIgogICAgIHNob3dncmlkPSJmYWxzZSIKICAgICBpbmtzY2FwZTp3aW5kb3ctd2lkdGg9IjEzNjYiCiAgICAgaW5rc2NhcGU6d2luZG93LWhlaWdodD0iNzA0IgogICAgIGlua3NjYXBlOndpbmRvdy14PSIwIgogICAgIGlua3NjYXBlOndpbmRvdy15PSIyNyIKICAgICBpbmtzY2FwZTp3aW5kb3ctbWF4aW1pemVkPSIxIiAvPgogIDxtZXRhZGF0YQogICAgIGlkPSJtZXRhZGF0YTciPgogICAgPHJkZjpSREY+CiAgICAgIDxjYzpXb3JrCiAgICAgICAgIHJkZjphYm91dD0iIj4KICAgICAgICA8ZGM6Zm9ybWF0PmltYWdlL3N2Zyt4bWw8L2RjOmZvcm1hdD4KICAgICAgICA8ZGM6dHlwZQogICAgICAgICAgIHJkZjpyZXNvdXJjZT0iaHR0cDovL3B1cmwub3JnL2RjL2RjbWl0eXBlL1N0aWxsSW1hZ2UiIC8+CiAgICAgICAgPGRjOnRpdGxlPjwvZGM6dGl0bGU+CiAgICAgIDwvY2M6V29yaz4KICAgIDwvcmRmOlJERj4KICA8L21ldGFkYXRhPgogIDxnCiAgICAgaW5rc2NhcGU6bGFiZWw9IkxheWVyIDEiCiAgICAgaW5rc2NhcGU6Z3JvdXBtb2RlPSJsYXllciIKICAgICBpZD0ibGF5ZXIxIgogICAgIHRyYW5zZm9ybT0idHJhbnNsYXRlKDAsLTM0My43MDA3OSkiPgogICAgPHBhdGgKICAgICAgIHN0eWxlPSJmaWxsOm5vbmU7ZmlsbC1ydWxlOmV2ZW5vZGQ7c3Ryb2tlOiMwMDAwMDA7c3Ryb2tlLXdpZHRoOjEwMDtzdHJva2UtbGluZWNhcDpyb3VuZDtzdHJva2UtbGluZWpvaW46cm91bmQ7c3Ryb2tlLW1pdGVybGltaXQ6NDtzdHJva2UtZGFzaGFycmF5Om5vbmU7c3Ryb2tlLW9wYWNpdHk6MSIKICAgICAgIGQ9Im0gMTA0LjMzMDcxLDQ2OS41MDUxIDUwMCwwIgogICAgICAgaWQ9InBhdGg0MTM2IgogICAgICAgaW5rc2NhcGU6Y29ubmVjdG9yLWN1cnZhdHVyZT0iMCIgLz4KICAgIDxwYXRoCiAgICAgICBzdHlsZT0iZmlsbDpub25lO2ZpbGwtcnVsZTpldmVub2RkO3N0cm9rZTojMDAwMDAwO3N0cm9rZS13aWR0aDoxMDA7c3Ryb2tlLWxpbmVjYXA6cm91bmQ7c3Ryb2tlLWxpbmVqb2luOnJvdW5kO3N0cm9rZS1taXRlcmxpbWl0OjQ7c3Ryb2tlLWRhc2hhcnJheTpub25lO3N0cm9rZS1vcGFjaXR5OjEiCiAgICAgICBkPSJtIDEwNC4zMzA3MSw3MDQuNTA1MSA1MDAsMCIKICAgICAgIGlkPSJwYXRoNDEzNi01IgogICAgICAgaW5rc2NhcGU6Y29ubmVjdG9yLWN1cnZhdHVyZT0iMCIKICAgICAgIGlua3NjYXBlOnRyYW5zZm9ybS1jZW50ZXIteD0iNzEuNDI4NTcyIgogICAgICAgaW5rc2NhcGU6dHJhbnNmb3JtLWNlbnRlci15PSItMjQyLjg1NzE2IiAvPgogICAgPHBhdGgKICAgICAgIHN0eWxlPSJmaWxsOm5vbmU7ZmlsbC1ydWxlOmV2ZW5vZGQ7c3Ryb2tlOiMwMDAwMDA7c3Ryb2tlLXdpZHRoOjEwMDtzdHJva2UtbGluZWNhcDpyb3VuZDtzdHJva2UtbGluZWpvaW46cm91bmQ7c3Ryb2tlLW1pdGVybGltaXQ6NDtzdHJva2UtZGFzaGFycmF5Om5vbmU7c3Ryb2tlLW9wYWNpdHk6MSIKICAgICAgIGQ9Im0gMTA0LjMzMDcxLDkzOS41MDUwNiA1MDAsMCIKICAgICAgIGlkPSJwYXRoNDEzNi01LTMiCiAgICAgICBpbmtzY2FwZTpjb25uZWN0b3ItY3VydmF0dXJlPSIwIgogICAgICAgaW5rc2NhcGU6dHJhbnNmb3JtLWNlbnRlci14PSI3MS40Mjg1NzIiCiAgICAgICBpbmtzY2FwZTp0cmFuc2Zvcm0tY2VudGVyLXk9Ii0yNDIuODU3MTYiIC8+CiAgPC9nPgo8L3N2Zz4K"
alt = "Table of contents" title = "Table of contents" />
</div>
<h2 class="author">Novean Institute of Standards</h2>
<h1 id = "link-0" class="title" >NIS Standards</h1>
</header>
<div id = "toc">
<h1>Table of contents</h1>
<ul>
<li><a href="#link-1">Acknowledgements</a></li>
<li><a href="#link-2">Introduction</a></li>
<li><a href="#link-3">Guidelines</a>
<ul><li><a href="#link-4">1.1. Changing Standards</a>
<ul><li><a href="#link-5">1.1.1. What is a SIP?</a></li>
<li><a href="#link-6">1.1.2. SIP Types</a></li>
<li><a href="#link-7">1.1.3. SIP Workflow</a></li>
</ul>
</li>
<li><a href="#link-8">1.2. Writing and Formatting</a>
<ul><li><a href="#link-9">1.2.1. SIP Formatting</a>
<ul><li><a href="#link-10">1.2.1.1. Terms</a></li>
<li><a href="#link-11">1.2.1.2. SIP Guides</a>
<ul><li><a href="#link-12">1.2.1.2.1. Fundamentals SIP</a></li>
<li><a href="#link-13">1.2.1.2.2. Recommendation SIP</a></li>
<li><a href="#link-14">1.2.1.2.3. Emergency SIP</a></li>
<li><a href="#link-15">1.2.1.2.4. Errata SIP</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li><a href="#link-16">1.3. Appeals</a></li>
</ul>
</li>
<li><a href="#link-17">Identification</a>
<ul><li><a href="#link-18">2.1. Semiotics</a>
<ul><li><a href="#link-19">2.1.1. Flagging</a></li>
<li><a href="#link-20">2.1.2. Signs</a>
<ul><li><a href="#link-21">2.1.2.1. Atmospheric Signs</a></li>
<li><a href="#link-22">2.1.2.2. Atmospheric Billboards</a></li>
<li><a href="#link-23">2.1.2.3. Space Signs</a></li>
<li><a href="#link-24">2.1.2.4. Space Billboards</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li><a href="#link-25">Navigation</a>
<ul><li><a href="#link-26">3.1. Port Interchange Protocol: 1ST DRAFT - PROPOSAL</a>
<ul><li><a href="#link-27">3.1.1. Introduction</a>
<ul><li><a href="#link-28">3.1.1.1. Motivation</a></li>
<li><a href="#link-29">3.1.1.2. Key Concepts</a></li>
<li><a href="#link-30">3.1.1.3. Issues not addressed by this proposal</a></li>
</ul>
</li>
<li><a href="#link-31">3.1.2. The Port Interchange</a>
<ul><li><a href="#link-32">3.1.2.1. Speed Zone</a></li>
<li><a href="#link-33">3.1.2.2. Alignment Zone</a></li>
<li><a href="#link-34">3.1.2.3. Transition Zone</a>
<ul><li><a href="#link-35">3.1.2.3.1. Approach and Take-off Vectors</a></li>
<li><a href="#link-36">3.1.2.3.2. Vertical Take-off and Landing (VTOL) concepts</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="#link-37">3.1.3. Implementation</a>
<ul><li><a href="#link-38">3.1.3.1. For Pilots and Navigators</a></li>
<li><a href="#link-39">3.1.3.2. For Facility Owners</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
<div id = "chapter-0" class = "chapter">
<h1 id = 'link-1'>Acknowledgements</h1><p id = "para-1">A special thank you is extended to all organizations and individuals who have contributed to this document, and have tested these procedures on the field.</p>
</div><div id = "chapter-1" class = "chapter">
<h1 id = 'link-2'>Introduction</h1><p id = "para-2">This space serves as a home to a developing set of standards for aviation communication and port interchange policies.</p>
</div><div id = "chapter-2" class = "chapter">
<h1 id = 'link-3'><span class = 'chapter-header'>Section 1</span><br />Guidelines</h1><p id = "para-3">The guidelines for the formatting NIS standards contained in this book.</p>
<ul>
<li><p id = "para-4"><a href = "#chapter-3">Changing Standards</a></p>
</li>
<li><p id = "para-5"><a href = "#chapter-4">Writing and Formatting</a></p>
</li>
<li><p id = "para-6"><a href = "#chapter-5">Appeals</a></p>
</li>
</ul>
</div><div id = "chapter-3" class = "chapter">
<h2 id = "link-4">1.1. Changing Standards</h2>
<p id = "para-7">The guidelines for submitting a modification to the NIS Standards.</p>
<ul>
<li><p id = "para-8"><a href = "Guidelines/#what-is-a-sip">What is a SIP?</a></p>
</li>
<li><p id = "para-9"><a href = "Guidelines/#sip-types">SIP Types</a></p>
</li>
<li><p id = "para-10"><a href = "Guidelines/#sip-workflow">SIP Workflow</a></p>
</li>
</ul>
<h3 id = "link-5">1.1.1. What is a SIP?</h3>
<p id = "para-11">SIP stands for Standards Improvement Proposal. A SIP is a design document providing information to NIS describing a new standard, recommendation, or a change to an existing standard. The SIP should provide a concise specification of the feature and a rationale for the feature.</p>
<p id = "para-12">SIPs are intended to be the primary mechanisms for proposing new standards, for collecting input on an issue, and for documenting the design decisions that have gone into the NIS Standards. The SIP author is responsible for building consensus and documenting dissenting opinions.</p>
<p id = "para-13">Because standards are maintained as text files in a versioned repository, their revision history is the historical record of the NIS Standards.</p>
<h3 id = "link-6">1.1.2. SIP Types</h3>
<p id = "para-14">The following is a brief outline of the various types of SIPs, however each is covered in full detail in their respective sections.</p>
<ul>
<li><p id = "para-15"><a href = "#chapter-4"><b>Fundamentals SIP</b></a> - Will cover a standards proposal that will be required fundamental knowledge for all users impacted. If a Fundamentals SIP is accepted, a grace period will be enacted so that users can train and/or adapt to the changes as needed.</p>
<p id = "para-16">An example of a Fundamentals SIP would be the usage of UTC as the base time, in which all traffic controllers and pilots would need to be adapt to communicating only in UTC time.</p>
</li>
<li><p id = "para-17"><a href = "#chapter-4"><b>Recommendation SIP</b></a> - Will cover a standards proposal for non-binding guidance or best practice recommendations. If a Recommendation SIP is accepted, it’s not expected that any parties adhere to it, though it’s understood that following it may lead to a better experience for impacted users.</p>
<p id = "para-18">An example of a Recommendation SIP would be using Illuminated Voxels in a specific pattern on a landing pad to denote nearby amenities for specific ship classes. While not necessary, it may improve the pilot landing experience.</p>
</li>
<li><p id = "para-19"><a href = "#chapter-4"><b>Emergency SIP</b></a> - Will cover a standards proposal for emergency changes needed to adapt to a rapidly evolving situation. Typically this type of SIP will involve many partners working together to address an issue quickly so that the impact of the situation can be minimized.</p>
<p id = "para-20">An example of an Emergency SIP would be a change in LUA functionlity that removes a feature, or changes the way a feature works, that would require codes changes and operational changes immediately.</p>
</li>
<li><p id = "para-21"><a href = "#chapter-4"><b>Errata SIP</b></a> - These are brief SIPs for fixing misspellings and other errors in the standards.</p>
</li>
</ul>
<h3 id = "link-7">1.1.3. SIP Workflow</h3>
<ul>
<li><p id = "para-22">(Errata SIPs are exempted from this workflow; see <a href = "#chapter-4">Errata SIP</a>)</p>
</li>
</ul>
<p id = "para-23">The SIP process begins with a new idea for the NIS Standards. Each potential SIP must have a champion (someone who writes the SIP using the style and format described below and shepherds the discussions in the appropriate channels) who must attempt to build consensus around the idea.</p>
<p id = "para-24">The SIP champion (a.k.a. Author) should first attempt to ascertain whether the idea is SIP-able. Using <a href = "https://discord.gg/jetkCs3">Discord</a> is the best avenue for starting this and discussing ideas with others involved.</p>
<p id = "para-25">Vetting an idea publicly before going as far as writing a SIP is meant to save both the potential author and other contributers time. Asking the NIS community first if an idea is original helps prevent too much time being spent on something that is guaranteed to be rejected based on prior discussions.</p>
<p id = "para-26">It also helps to make sure the idea is applicable to others and not just the author.</p>
<p id = "para-27">Once the champion has asked the NIS community as to whether an idea has any chance of acceptance, a draft SIP should be presented to the appropriate discord #SIP-drafts channel. This gives the author a chance to flesh out the draft SIP to make it properly formatted, of high quality, and to address additional concerns about the proposal.</p>
<p id = "para-28">Following a discussion, the proposal should be submitted for a decision by the partner standards members on discord. This draft must be written in SIP style as described below, or else it will be sent back until proper formatting rules are followed. The standards partner members will determine the impact of the proposal and notify the author.</p>
<p id = "para-29">It is highly recommended that a single SIP contain a single key proposal or new idea. The more focused the SIP, the more successful it is likely to be. If in doubt, split your SIP into several well-focused ones.</p>
<p id = "para-30">Once a SIP has been accepted, the reference implementation must be completed with a pull request to the <a href = "https://github.com/Novean-Institute-of-Standards/NIS-Standards">Github Repo</a>, with the SIP attached to the description field where it will be verified and merged into this document if accepted.</p>
</div><div id = "chapter-4" class = "chapter">
<h2 id = "link-8">1.2. Writing and Formatting</h2>
<p id = "para-31">The formatting guidelines and rules for formatting a SIP</p>
<ul>
<li><p id = "para-32"><a href = "Guidelines/#sip-formatting">SIP Formatting</a></p>
<ul>
<li><p id = "para-33"><a href = "Guidelines/#terms">Terms</a></p>
</li>
<li><p id = "para-34"><a href = "Guidelines/#sip-guides">SIP Guides</a></p>
<ul>
<li><p id = "para-35"><a href = "Guidelines/#fundamentals-sip">Fundamentals SIP</a></p>
</li>
<li><p id = "para-36"><a href = "Guidelines/#recommendation-sip">Recommendation SIP</a></p>
</li>
<li><p id = "para-37"><a href = "Guidelines/#emergency-sip">Emergency SIP</a></p>
</li>
<li><p id = "para-38"><a href = "Guidelines/#errata-sip">Errata SIP</a></p>
</li>
</ul>
</li>
</ul>
</li>
</ul>
<h3 id = "link-9">1.2.1. SIP Formatting</h3>
<h4 id = "link-10">1.2.1.1. Terms</h4>
<p id = "para-39">Each SIP (depending on the type) will have at least one of the following parts:</p>
<ul>
<li><p id = "para-40"><b>Preamble</b> - A header containing meta-data about the SIP, including the SIP number, a short descriptive title, the names, and optionally the contact info for each author, etc.</p>
</li>
<li><p id = "para-41"><b>Abstract</b> - a short (~200 word) description of the issue being addressed.</p>
</li>
<li><p id = "para-42"><b>Specification</b> - The technical specification should describe the syntax and semantics of any new standard proposal. The specification should be detailed enough to allow for a complete understanding by impacted parties.</p>
</li>
<li><p id = "para-43"><b>Motivation</b> -- The motivation is critical for SIPs. It should clearly explain why the existing standards specification are inadequate to address the problem that the SIP solves. SIP submissions without sufficient motivation may be rejected.</p>
</li>
<li><p id = "para-44"><b>Rationale</b> - The rationale fleshes out the specification by describing what motivated the standards change and why particular decisions were made. It may also describe alternate ideas that were considered. Ideally it should provide evidence of consensus within the standards community and discuss important objections or concerns raised during discussion.</p>
</li>
<li><p id = "para-45"><b>Reference Text</b> - The reference standards text to be added or changed should accompany all SIPs. Any SIP that does not contain a reference text will be rejected.</p>
</li>
</ul>
<h4 id = "link-11">1.2.1.2. SIP Guides</h4>
<h5 id = "link-12">1.2.1.2.1. Fundamentals SIP</h5>
<h5 id = "link-13">1.2.1.2.2. Recommendation SIP</h5>
<h5 id = "link-14">1.2.1.2.3. Emergency SIP</h5>
<h5 id = "link-15">1.2.1.2.4. Errata SIP</h5>
<p id = "para-46"><b>Submission</b></p>
<p id = "para-47">An errata SIP may be submitted directly to the <a href = "https://github.com/Novean-Institute-of-Standards/NIS-Standards">Github Repo</a> without needing to go through a standards partners approval process.</p>
<p id = "para-48">If it is determined that the scope of the SIP is beyond an errata change, it may be rejected and sent back for escalation as one of the other SIP types.</p>
<p id = "para-49"><b>Template</b></p>
<pre><span style="color:#839496;"> Type: Errata
Title: <SIP title>
Author: <Author Name/Discord ID>
Created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
Reference Text: <A description of the change needed>
</span></pre>
</div><div id = "chapter-5" class = "chapter">
<h2 id = "link-16">1.3. Appeals</h2>
<p id = "para-50">Appealing a decision on a submission.</p>
</div><div id = "chapter-6" class = "chapter">
<h1 id = 'link-17'><span class = 'chapter-header'>Section 2</span><br />Identification</h1><p id = "para-51">Identification is the process of self-identify yourself to a port, waystations and other ships.</p>
<ul>
<li><p id = "para-52"><a href = "#chapter-7">Semiotics</a></p>
</li>
</ul>
</div><div id = "chapter-7" class = "chapter">
<h2 id = "link-18">2.1. Semiotics</h2>
<p id = "para-53">The standards for signs and symbols and their use or interpretation.</p>
<ul>
<li><p id = "para-54"><a href = "Identification/Semiotics/#flagging">Flagging</a></p>
</li>
<li><p id = "para-55"><a href = "Identification/Semiotics/#signs">Signs</a></p>
<ul>
<li><p id = "para-56"><a href = "Identification/Semiotics/#atmospheric-signs">Atmospheric Signs</a></p>
</li>
<li><p id = "para-57"><a href = "Identification/Semiotics/#atmospheric-billboards">Atmospheric Billobards</a></p>
</li>
<li><p id = "para-58"><a href = "Identification/Semiotics/#space-signs">Space Signs</a></p>
</li>
<li><p id = "para-59"><a href = "Identification/Semiotics/#space-billboards">Space Billboards</a></p>
</li>
</ul>
</li>
</ul>
<h3 id = "link-19">2.1.1. Flagging</h3>
<h3 id = "link-20">2.1.2. Signs</h3>
<h4 id = "link-21">2.1.2.1. Atmospheric Signs</h4>
<h4 id = "link-22">2.1.2.2. Atmospheric Billboards</h4>
<h4 id = "link-23">2.1.2.3. Space Signs</h4>
<h4 id = "link-24">2.1.2.4. Space Billboards</h4>
</div><div id = "chapter-8" class = "chapter">
<h1 id = 'link-25'><span class = 'chapter-header'>Section 3</span><br />Navigation</h1><p id = "para-60">The guidelines for Navigation as defined by NIS.</p>
<ul>
<li><p id = "para-61"><a href = "#chapter-9">Port Interchange</a></p>
</li>
</ul>
</div><div id = "chapter-9" class = "chapter">
<h2 id = "link-26">3.1. Port Interchange Protocol: 1ST DRAFT - PROPOSAL</h2>
<p id = "para-62"><em>Summary: A standard of customs to be utilized for take-off from, and landing at, locations in</em> Dual Universe.</p>
<ul>
<li><p id = "para-63"><a href = "Navigation/PortInterchange/#introduction">Introduction</a></p>
<ul>
<li><p id = "para-64"><a href = "Navigation/PortInterchange/#motivation">Motivation</a></p>
</li>
<li><p id = "para-65"><a href = "Navigation/PortInterchange/#key-concepts">Key Concepts</a></p>
</li>
<li><p id = "para-66"><a href = "Navigation/PortInterchange/#issues-not-addressed-by-this-proposal">Issues not addressed by this proposal</a></p>
</li>
</ul>
</li>
<li><p id = "para-67"><a href = "Navigation/PortInterchange/#the-port-interchange">Port Interchange</a></p>
<ul>
<li><p id = "para-68"><a href = "Navigation/PortInterchange/#speed-zone">Speed Zone</a></p>
</li>
<li><p id = "para-69"><a href = "Navigation/PortInterchange/#alignment-zone">Alignment Zone</a></p>
</li>
<li><p id = "para-70"><a href = "Navigation/PortInterchange/#transition-zone">Transition Zone</a></p>
<ul>
<li><p id = "para-71"><a href = "Navigation/PortInterchange/#approach-and-take-off-vectors">Approach and Take-off Vectors</a></p>
</li>
<li><p id = "para-72"><a href = "Navigation/PortInterchange/#vertical-take-off-and-landing-vtol-concepts">Vertical Take-off and Landing concepts</a></p>
</li>
</ul>
</li>
</ul>
</li>
<li><p id = "para-73"><a href = "Navigation/PortInterchange/#implementation">Implementation</a></p>
<ul>
<li><p id = "para-74"><a href = "Navigation/PortInterchange/#for-pilots-and-navigators">For Pilots and Navigators</a></p>
</li>
<li><p id = "para-75"><a href = "Navigation/PortInterchange/#for-facility-owners">For Facility Owners</a></p>
</li>
</ul>
</li>
</ul>
<h3 id = "link-27">3.1.1. Introduction</h3>
<p id = "para-76">This document describes a proposal for a set of standards, customs, and definitions for a protocol to be used when travelling from one player-made point of interest to another, specifically for those that provide <em>Port Facilities</em>.</p>
<p id = "para-77">It contains guidelines for a set of customs for players to follow when near such a location, and to define a set standards and practices to be implemented by Port Facility owners.</p>
<h4 id = "link-28">3.1.1.1. Motivation</h4>
<p id = "para-78">The primary motivation for this proposal is safety - to offer players a way to travel from one location to another while mitigating concerns of collisions with the landscape, buildings, players, and other vehicles.</p>
<p id = "para-79">If a player can be assured that they have a specific plan to arrive at or depart from any given location, and that other players in the vicinity also have a similar plan, that player may develop a stronger sense of community within the game, simply because the act of travelling itself would be less worrisome.</p>
<p id = "para-80">Another motivation for this proposal is simplicity. As of this document’s creation, Dual Universe has only one navigational indicator - the destination. This indicator is simply a representation of a point in space relative to the player, along with the relative distance from the player to the location.</p>
<p id = "para-81">This proposal currently utilizes this indicator, and builds its concepts around it.</p>
<h4 id = "link-29">3.1.1.2. Key Concepts</h4>
<p id = "para-82">Key concepts and definitions used in this section.</p>
<p id = "para-83"><b>Dead Reckoning.</b> All elements of this standard are centered around information provided by waypoints (Destinations), therefore any element dealing with distance will use the player’s distance from a particular waypoint.</p>
<p id = "para-84"><b>Zones.</b> A <em>Zone</em> is an area, defined in its simplest form as a circle, and extended into cylinders and spheres, whose radii are derived from the distance from a location’s waypoint, Indicating a specific pattern of behavior for a pilot to adhere to within the specified area.</p>
<p id = "para-85"><b>Port Facilities.</b> A <em>Port Facility</em> in the scope of this proposal is a specific, centralized location that any number of players may travel to and from using vehicles, and usually provides dedicated areas for landing, refitting/refueling, and take-off.</p>
<p id = "para-86">Examples of port facilities are organization headquarters, surface-borne player-made spaceports and space stations.</p>
<p id = "para-87"><b>Navigational Aids.</b> A <em>Navigational</em> Aid can be a waypoint(destination), or a vector indicator - a physical representation of the direction a vehicle should be travelling along when taking off or landing.</p>
<p id = "para-88">Currently, the waypoint and vector indicator are the only tools provided in-game.</p>
<p id = "para-89"><b>Pilots’ priorities.</b> Due to the nature of the information available to pilots and the current limitation, this proposal cannot completely ensure safe and unobstructed travel near port facilities.</p>
<p id = "para-90">Therefore, pilots must still maintain situational awareness during flight within zones, and should yield to traffic already present in applicable zones.</p>
<p id = "para-91"><b>Space.</b> For the purposes of this document, the term <em>space</em> will refer to both “airspace” - the area above ground in relation to various concepts, as well as the “space” around an asteroid or space station.</p>
<h4 id = "link-30">3.1.1.3. Issues not addressed by this proposal</h4>
<p id = "para-92">As of this document’s creation, its sole purpose is to provide a singular standard for navigating the space associated with a location, using only in-game information available to any player.</p>
<p id = "para-93">It <em>does not</em> define a standard for any other aspect of navigation associated with landing and take-off, whether done through active interaction with other players(Air Traffic Controllers), or with the use of in-game scripting.</p>
<p id = "para-94">This standard also does not define any sort of its own enforcement, and its utilization should be done through mutual acceptance, or enforced from within a player’s organization.</p>
<h3 id = "link-31">3.1.2. The Port Interchange</h3>
<p id = "para-95">All zones of the Port Interchange will be concentric to a waypoint, placed just above the landing/take-off area of a location.</p>
<p id = "para-96">Typically, a map-generated waypoint will be inaccurate for the purposes of this standard, and therefore should be manually generated by a player/organization.</p>
<p id = "para-97">In addition, this waypoint should be shared with all players who would have access to its associated location.</p>
<h4 id = "link-32">3.1.2.1. Speed Zone</h4>
<p id = "para-98">The <em>Speed Zone</em> of a location is the outermost boundary of the port interchange. It is the first interaction with an interchange for players arriving to a location, and the last interaction for players travelling away from a location.</p>
<p id = "para-99">For surface-based locations, it is a cylinder with a radius of <em>N</em> meters(m), with the base of which is coplanar with the surface around a location, extending upwards through a location’s space.</p>
<p id = "para-100">For locations <em>in space</em>, it is a sphere with a radius of <em>N</em> m. While the player is inside of this zone, a vehicle’s speed should remain as close to <em>N</em> kilometers per hour(km/h) as possible.</p>
<h4 id = "link-33">3.1.2.2. Alignment Zone</h4>
<p id = "para-101">The <em>Alignment Zone</em> of a location is next closest boundary of the Port Interchange, and is concentric with the Speed Zone. For planar locations, it is a cylinder with a radius of <em>N</em> m, extending upward into the space around a location.</p>
<p id = "para-102">For space-based locations, it is a sphere of <em>N</em> m, which is concentric to the Speed Zone. The purpose of the Alignment Zone is to define an area from which a vehicle will change from travelling in a straight line towards/away from a location into the “circling” pattern defined by the Transition Zone.</p>
<p id = "para-103">All guidelines for vehicles in the Speed zone also apply to this zone.</p>
<h4 id = "link-34">3.1.2.3. Transition Zone</h4>
<p id = "para-104">The <em>Transition Zone</em> of a location defines the path to be taken by vehicles before turning into <em>Approach</em> and <em>Take-off Vectors</em>. For planar locations, this zone will be a circle with a radius of <em>N</em> m, and runs parallel at a pre-defined height above the surface.</p>
<p id = "para-105">For orbital locations, this zone will be a circle that is coplanar with the approach and take-off vectors and aligned with the locations gravity(if any). pilots will use this zone to maintain a set distance from the location’s waypoint.</p>
<p id = "para-106">Like the Alignment zone, the Transition zone is also within the speed zone, and all guidelines for vehicles within the speed zone apply to this zone as well.</p>
<h5 id = "link-35">3.1.2.3.1. Approach and Take-off Vectors</h5>
<p id = "para-107">The <em>Approach Vector</em> and <em>Take-off Vector</em> are separate direction indicators moving towards and away from a location, respectively.</p>
<p id = "para-108">For vehicles on an Approach Vector, a location may have a lower speed and right-of-way guidelines for the purpose of taxiing out of the vector and onto a final landing point. For vehicles intending to take off, location-specific guidelines may be made concerning right-of-way when entering a Take-off Vector.</p>
<h5 id = "link-36">3.1.2.3.2. Vertical Take-off and Landing (VTOL) concepts</h5>
<p id = "para-109">further discussion on this set of concepts is needed.</p>
<h3 id = "link-37">3.1.3. Implementation</h3>
<h4 id = "link-38">3.1.3.1. For Pilots and Navigators</h4>
<p id = "para-110">Guidelines for Pilots and Navigators</p>
<p id = "para-111"><b>Speed Zone.</b> For pilots approaching a location piloting vehicles that may not be able to completely slow their vehicle to the indicated limit <em>before</em> approaching the alignment zone, <em>must</em> start to reduce speed <em>before</em> entering the speed zone to ensure this limit is attainable.</p>
<p id = "para-112">Along with adhering to the speed limits, a pilot approaching a location and moving within the speed zone should begin to alter their course from a straight line pointing towards a location’s waypoint, to one that is a tangent to the boundary of the alignment zone, placing the waypoint on the L/R side of the approaching vehicle.</p>
<p id = "para-113"><b>Alignment Zone.</b> This zone may also have a higher density of traffic, therefore pilots must be increasingly more cautious when entering and leaving this zone.</p>
<p id = "para-114">When pilots are departing from a location and are in the Alignment zone to the speed zone, their waypoint can be changed another in regards to their destination, and then may proceed in a straight vector towards it, while yielding to any traffic merging in from the Speed Zone.</p>
<p id = "para-115"><b>Transition Zone.</b> Approaching vehicles <em>must</em> remain in this zone until both a transition to the Approach Vector can be made without further intrusion into the location, and when there is no traffic blocking such a maneuver.</p>