forked from TravelMapping/Web
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathparticipate.php
618 lines (507 loc) · 28.8 KB
/
participate.php
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
<?php require $_SERVER['DOCUMENT_ROOT'] . "/lib/tmphpuser.php" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<?php require $_SERVER['DOCUMENT_ROOT']."/lib/tmphpfuncs.php" ?>
<title>Travel Mapping Manual: How to participate in the project</title>
<link rel="stylesheet" type="text/css" href="/css/travelMapping.css">
<link rel="shortcut icon" type="image/png" href="favicon.png">
</head>
<body>
<?php require $_SERVER['DOCUMENT_ROOT']."/lib/tmheader.php"; ?>
<?php
if ($tmmode_s == "railway") {
echo "<p class='errorbar'>The TM Manual has not yet been updated with information specific to TM Railways!</p>";
}
?>
<h1>Travel Mapping Manual: How to participate in the project</h1>
<p class="heading">
Contents</p>
<div class="text">
<ul>
<li><a href="#userlistfile">How to create a user list file</a></li>
<ul>
<li><a href="#tmdata">Travel Mapping data basics</a></li>
<li><a href="#firststeps">First steps with email submission</a></li>
<li><a href="#problems">Solutions to common problems</a></li>
<li><a href="#examples">More examples of how to break down your travels</a></li>
<li><a href="#advanced">Advanced features</a></li>
</ul>
<li><a href="#hwydatamanager">How to become a highway data manager</a></li>
</ul>
</div>
<p class="heading"><a name="userlistfile"></a><a style="text-decoration:none" href="#userlistfile">🔗</a>
How to create a user list file</p>
<div class="text">
The basic idea is to make a list of highway sections you have traveled and collect them into a <em>plain text file</em>
to be submitted to Travel Mapping. The text file will be
processed to populate a set of custom stats pages and maps
describing your travels.<br />
<br />
For examples, you can browse the <a href="stat.php">travel summaries</a> of any of our users.
</div>
<p class="subheading"><a name="tmdata"></a><a style="text-decoration:none" href="#firststeps">🔗</a>
Travel Mapping data basics</p>
<div class="text" >
All routes mappable by Travel Mapping can be found organized by <a
href="/devel/manual/sysdef.php">highway system</a> in the <a
href="/hb/">Highway Browser</a> and are listed in the <a
href="/hb/findroute.php">Route Finder</a>. Selecting a route through
the Highway Browser or Route Finder brings up that route in the
<i>showroute</i> tool. You can also get to <i>showroute</i> for any
route by clicking on a segment on any <I>Mapview</I> map, then
clicking on the route name in the popup that appears. <br /><br />
To keep the size of the project's data manageable, routes are
approximated by <i>waypoints</i> located at interchanges, major
intersections, and borders. <i>showroute</i> provides a list of
<i>waypoints</i> that you use specify the start and end points of
each segments of the route that you have traveled.
By default, <i>showroute</i> shows a route within a single region
(e.g., state, province). Routes that span multiple regions (like
U.S. Interstate highways), the entire route can be viewed by clicking
on the "View Connected Route" link under the highway shield in the
upper left of the <i>showroute</i> window. You will learn below how
to create entries in either case.<br /><br />
<i>showroute</i> gives all of the information you need to create the
entries for your user list file that will represent your traveled
segments: ".list Name" for the route, and the labels of the waypoints
at the ends of your traveled segments. For routes within a region,
you will find the .list Name under the shield in the upper left, and
waypoint labels can be found in the table on the left side of the
window or by clicking any of the waypoints on the map. When viewing a
connected route, the .list Name is in the waypoint table above the
points in each region, and the waypoint labels are in the table and
again can be found by clicking on waypoints on the map.<br /><br />
</div>
<p class="subheading"><a name="firststeps"></a><a style="text-decoration:none" href="#firststeps">🔗</a>
First steps with email submission</p>
<div class="text" >
<ol>
<li><a name="username"></a><a style="text-decoration:none" href="#username">🔗</a>
<b>Choose an alphanumeric username.</b><br />
<br />
Use only English letters (<code>A-Z</code> or <code>a-z</code>),
numbers (<code>0-9</code>), and underscores (<code>_</code>) in your
username, and keep the name at or under 48 characters long. Avoid
characters with diacritical marks, and characters from other
alphabets; otherwise your file will not be processed.
</li>
<br />
<li><a name="plainfile"></a><a style="text-decoration:none" href="#plainfile">🔗</a>
<b>Create a plain text file.</b><br />
<br />
Name the file <code>username.list</code>, replacing
<code>username</code> with the username you chose. For example, if
you choose the name <code>highwayguy</code>, name your file
<code>highwayguy.list</code> .
</li>
<br />
<li><a name="userentry"></a><a style="text-decoration:none" href="#userentry">🔗</a>
<b>Make a list of highway sections you have traveled.</b><br />
<br />
Break up your travels into the traveled sections on each route. For
each route section, add one line to your <code>.list</code> file with
the single-region format:<br /> <br />
<code>Region Route Waypoint1 Waypoint2</code><br /><br />
or the multi-region format (which can be used any time but is most useful for multi-region connected routes): <br /><br />
<code>Region1 Route1 Waypoint1 Region2 Route2 Waypoint2</code><br /><br />
For example, if you traveled in the United States on Interstate 70 between Exit 52 in Illinois and Exit 249 in Missouri, you could specify that with two single-region lines:<br /><br />
<code>IL I-70 52 MO/IL</code><br />
<code>MO I-70 MO/IL 249</code><br /><br />
or with a single mutli-region line:<br /><br />
<code>IL I-70 52 MO I-70 249</code><br /><br />
All of the information can be gathered from the <i>showroute</i> page
for the route. However, the easiest and least error-prone way to
generate your <code>.list</code> file entries is to use
<i>showroute</i>'s .list Tool. You can enable this on any
<i>showroute</i> page by enabling the checkbox next to ".list Tool" at
the top of the window.<br /><br />
This brings up the ".list Toolbox" at the upper right. As segments of
the route are selected or unselected, the entry or entries that would
need to be added to your <code>.list</code> file will appear and those
segments are highlighted on the map. Segment selections can be
manipulated in a few ways:<br /><br />
<ul>
<li>Click on any segment on the map to toggle whether it is selected
or not.</li>
<li>Click on a segment then hold the SHIFT key while clicking on
another segment selects/unselects those segments and all in
between.</li>
<li>The "Clear Selection" button unselects all segments and the
"Select All Segments" button selects them all.</li>
<li>If you already have any segments mapped for the route in Travel
Mapping from a previous <code>.list</code> file submission, the
"Select Clinched Segments" button will select them.</li>
</ul>
<br /><br />
Once you have the segments that represent your travels selected, you
can copy the text from the .list Toolbox into your <code>.list</code>
file. The "Copy to Clipboard" button copies all of the text to your
system's clipboard for easy pasting into your <code>.list</code>
file.<br /><br />
Continue adding entries for routes to complete your travels. <a
href="#examples">See below</a> if you need more examples on how to
break down your travels into "sections" to enter into the file.<br
/><br />
Note that a mechanism is in place to automatically include concurrent
highways and credits you for all of them as long as the segment is
included in at least one of them.<br /><br />
We recommend starting with a small number of routes and submitting an
initial draft to be included in the site update to make sure that you
understood the procedure well.<br /></li>
<br />
<li><a name="checkwork"></a><a style="text-decoration:none" href="#checkwork">🔗</a>
<b>Check your work.</b><br /><br />
Make sure the following items are correct:<br /><br />
<ul>
<li><b>Each line has exactly the four or six required fields:</b>
<code>Region Route Waypoint1 Waypoint2</code> or <code>Region1 Route1
Waypoint1 Region2 Route2 Waypoint2</code></li>
<li><b>The fields have only spaces or tabs between them.</b> Other
delimiters may prevent the site update program from parsing your file
correctly.</li>
<li><b>The file is saved as plain text with a <code>.list</code>
extension.</b> Word processor files (Microsoft Word, Open Office
Write, etc.) and rich-text formats will not work. If you use a word
processor to create your file, be sure to select "Save As..." and save
the file in a plain text format.</li>
</ul>
</li>
<br />
<li><a name="emailsubmission"></a><a style="text-decoration:none" href="#emailsubmission">🔗</a> <b>Send your <code>.list</code> file as an email attachment to <code>[email protected]</code></b>.<br /><br />
Mention in the subject line that your username is a new one.
You're set -- just wait for the next site update after which you will see your maps and stats live on the site. Site updates typically occur nightly between 9 and 11 PM US/Eastern.<br /></li>
<br />
<li><a name="aftersiteupdate"></a><a style="text-decoration:none"
href="#aftersiteupdate">🔗</a> <b>After the next site update,
look for your name on the <a href="stat.php">Traveler List</a>.</b><br
/> <br />
Once your file has been processed, your name will appear in this list
along with all the other travelers. Click on your username and enjoy
your traveled highway stats and maps.<br />
Additional stats are available in csv files linked from <a
href="/stats/">https://travelmapping.net/stats/</a>.</li> <br />
<li><a name="errorlog"></a><a style="text-decoration:none"
href="#errorlog">🔗</a> <b>Check the user log file.</b><br /><br
/>
Check your <a href="/logs/users/">online log file</a> (also directly
linked on your user stats page). If you included a highway or point
label that the mapping script does not recognize, it will tell you in
the first segment of your log file. Sometimes highway data is updated,
and this may generate a new error. You can find a note in the first
lines of your log file. Check <a href="devel/updates.php">the updates
page</a> for info on what has been changed to the route.<br /><br />
Route updates that don't break your <code>.list</code> file are also
reported in your log file. Notes to changes since the last update of
your <code>.list</code> file are found at the beginning, older changes
at the very end of the log file. You should also check the updates
page frequently to find added routes or highway systems. Changes to
<a href="devel/manual/sysdef.php#preview">systems in preview state</a>
are not notified.
</li> <br />
<li><a name="nextupdate"></a><a style="text-decoration:none"
href="#nextupdate">🔗</a> <b>Update your file as needed by
emailing an updated copy.</b><br /><br />
If you do more traveling, you can update your <code>.list</code> file
to reflect the new highways on which you have traveled. To submit your
updated file, just email it again, and it will be processed in the
subsequent site update. Feel free to update as often as you wish!</li>
</ol> Travel Mapping's volunteers hope that you enjoy your maps and
stats pages from this free service! </div>
<p class="subheading"><a name="problems"></a><a
style="text-decoration:none" href="#problems">🔗</a> Solutions
to common problems</p>
<div class="text">
<ol>
<li><a name="invaliduser"></a><a style="text-decoration:none" href="#invaliduser">🔗</a>
<b>An invalid username was chosen.</b><br />
<br />
Only the characters <code>A-Z</code>, <code>a-z</code>, <code>0-9</code>, and the underscore <code>_</code>
are allowed in usernames. If you used other
characters, such as non-English characters or symbols, remove them.
</li>
<br />
<li><a name="namemismatch"></a><a style="text-decoration:none" href="#namemismatch">🔗</a>
<b>The filename does not match the username.</b><br /><br />
If the username is <code>highwayguy80</code>, then the filename should
be <code>highwayguy80.list</code>, not <code>highwayguy80.txt</code>,
<code>HighwayGuy80.list</code>, <code>arkansas.list</code>,
<code>motorways.list</code>, etc.<br /><br />
Note that since modern desktop operating systems hide the file
extension <code>.list</code> by default and/or include an extra,
hidden <code>.txt</code> extension, files with a
<code>.list.txt</code> extension are also accepted (e.g.,
<code>highwayguy80.list.txt</code>) and do not cause any problems for
the site update process.
</li>
<br />
<li><a name="notemailed"></a><a style="text-decoration:none" href="#notemailed">🔗</a>
<b>The file was not emailed.</b><br /><br />
Check that you attached your file to your email and that you finished
sending it. Obviously files that are not received cannot be processed!
</li>
<br />
<li><a name="notprocessed"></a><a style="text-decoration:none" href="#notprocessed">🔗</a>
<b>The file was sent but has not yet been processed.</b><br />
<br />
Site updates typically occur daily, and the time of the last update
(currently <?php echo tm_update_time(); ?> US/Eastern) can always be
found at the bottom of the project's home page. Expected disruptions in the site update schedule will be mentioned in the project forum.
If your file was sent more than about 30 minutes before the most
recent update and you don't see your changes reflected on the site,
you can check on its status with an additional email or simply
resend. <br />
</li>
<br /> <li><a name="vanished"></a><a style="text-decoration:none"
href="#vanished">🔗</a> <b>The new file was processed, but all
the highways from the previous file are no longer shown.</b><br /><br />
Each new file you submit should contain all your traveled highways,
not just additions to those from a previously submitted file. The new
file always replaces the previous file rather than supplementing
it. This allows users to not only add or modify lines in their file
but also to delete them as needed. </li>
</ol>
</div>
<p class="subheading"><a name="examples"></a><a style="text-decoration:none" href="#examples">🔗</a>
More examples of how to break down your travels</p>
<div class="text">
Below are several example entries for a user's <code>.list</code> file.<br />
<br />
<ul>
<li><a name="exsingleregion"></a><a style="text-decoration:none"
href="#exsingleregion">🔗</a> <b>Highway segment within a single
region.</b><br /><br />
For the segment of I-80 between Exits 161 and 224 in Pennsylvania,
USA, look up the highway and waypoint labels for those interchanges in
<a href="/hb/showroute.php?r=pa.i080"><i>showroute</i></a>. The
highway is <code>PA I-80</code> and the waypoints are <code>161</code>
and <code>224</code>. Enter the following line into your
<code>.list</code> file:<br />
<pre>
PA I-80 161 224
</pre></li>
<li><a name="exmultipleregions"></a><a style="text-decoration:none"
href="#exmultipleregions">🔗</a> <b>Highway segment crossing
into multiple regions.</b><br /><br />
To enter the segment of I-81 between Exit 300 in Virginia and Exit 10
in New York, the easiest approach is to add a <a
href="#multiregion">multi-region</a> line by specifying the first
waypoint in West Virgina and the last waypoint in New York only:<br />
<pre>
VA I-81 300 NY I-81 10
</pre>
Alternately, you can break up the segment into smaller pieces by
region. The Virginia segment begins at Exit 300 and ends at the West
Virginia border, so use waypoints <code>300</code> and
<code>VA/WV</code> for the Virginia segment. I-81 runs from border to
border in West Virginia, Maryland, and Pennsylvania, so use waypoints
<code>WV/MD</code>, <code>MD/PA</code>, and <code>PA/NY</code> for
these states. The New York segment begins at the Pennsylvania border
and ends at Exit 10, so use waypoints <code>PA/NY and 10</code>. All
of these waypoints are listed in <i>showroute</i>. Start with <a
href="/hb/showroute.php?r=va.i081">Virgina</a> and click on the
intersecting route links to change the regions until you've reached
New York.<br /> <br />
Ultimately your <code>.list</code> should contain all of the following
to map the whole segment:<br />
<pre>
VA I-81 300 VA/WV
WV I-81 VA/WV WV/MD
MD I-81 WV/MD MD/PA
PA I-81 MD/PA PA/NY
NY I-81 PA/NY 10
</pre>
</li>
<li><a name="exbeltway"></a><a style="text-decoration:none"
href="#exbeltway">🔗</a> <b>Beltways (full loop highways) within
a single region.</b><br /><br />
The .list Tool in <i>showroute</i> is especially helpful in creating
<code>.list</code> file entries for beltways. The remaining
description here is included as an explanation for those who wish to
construct <code>.list</code> file entries manually.<br /><br />
In single-region beltways, a waypoint has been selected as both the
highway's <i>beginning</i> and <i>end</i>. This location is used for
both the first and last waypoints of the highway, with a different
waypoint label for each end. If the segment you wish to enter into
your <code>.list</code> file crosses that point, split your segment
into two at that point.<br /> <br />
Consider first the segment of the Baltimore Beltway (<a
href="/hb/showroute.php?r=md.i695">MD I-695</a>) between Exits 17 and
31 along the <i>northern</i> side of Baltimore. I-695 begins and ends
at a southern waypoint called both 0 and 48. Since the waypoints run
continuously from 17 to 31 without crossing that southern point
(compare to next example), treat this segment simply as beginning at
waypoint <code>17</code> and ending at waypoint <code>31</code>:<br />
<pre>
MD I-695 17 31
</pre>
Now consider the <i>southern</i> segment of the Baltimore Beltway
between the same Exits 17 and 31. The waypoints numbers reset in this
range: 17, 16, ..., 1, 0, 48, 44, ..., 31. Waypoints 0 and 48 refer to
the same point. With this in mind, treat your whole segment as two,
one with ends at <code>0</code> and <code>17</code>, and the other
with ends at <code>31</code> and <code>48</code>:<br />
<pre>
MD I-695 0 17
MD I-695 31 48
</pre>
To enter the entire Baltimore Beltway, use the two labels for the
common end points, which are the first and last labels shown in
<i>showroute</i>:<br />
<pre>
MD I-695 0 48
</pre></li>
<li><a name="exbeltwaymultiregions"></a><a
style="text-decoration:none"
href="#exbeltwaymultiregions">🔗</a> <b>Beltways crossing into
multiple regions.</b><br /> <br />
Treat segments along these beltways just as you would any other
segment that crosses into multiple regions: one <code>.list</code>
file line per region, or a multi-region 6-field entry that spans
regions. Again, the .list Tool in <i>showroute</i> is especially
helpful in creating <code>.list</code> file entries for beltways. <br
/><br /></li>
<li><a name="nearbywp"></a><a style="text-decoration:none" href="#nearbywp">🔗</a> <b>No waypoint where your travel started or ended.</b><br /><br />
If the route does not have a waypoint where your travel on this
highway started or ended, you need to find a nearby waypoint in
<i>showroute</i>. Our manual includes <a
href="/devel/manual/includepts.php">a section on how we determine
which points are included in each route</a>. </li>
</ul>
</div>
<p class="subheading"><a name="advanced"></a><a style="text-decoration:none" href="#advanced">🔗</a>
Advanced features</p>
<div class="text">
<ul>
<li><a name="comment"></a><a style="text-decoration:none" href="#comment">🔗</a>
Using comments<br />
<br />
Just as is the case in programming languages, Travel Mapping
allows you to add <i>comments</i> to your <code>.list</code>
file. All text on a given line after a <code>#</code> is treated
as a comment, and is ignored by the site update process. You can
comment out entire lines, or use them to include an annotatation at
the end of the line.<br />
<br />
<code>#My first travel section</code><br />
<code>IL I-70 52 MO/IL #This is the section in Illinois</code><br />
<code>MO I-70 MO/IL 249 #This is the section in Missouri</code>
<br />
<br />
</li>
<li><a name="structure"></a><a style="text-decoration:none" href="#structure">🔗</a>
Structure <code>.list</code> file<br />
<br />
Many users break up <code>.list</code> files into chunks by system, region
or individual travel to make it easier to read or manage.
You can also use blank lines as desired to enhance readability.
<br />
<br />
</li>
<li><a name="githubsubmit"></a><a style="text-decoration:none" href="#githubsubmit">🔗</a> GitHub submission<br /><br />
When you submit a <code>.list</code> file, it is placed under source
code control using GitHub. Instead of emailing updates, some users
fork our GitHub repository at <a
href="https://github.com/TravelMapping/UserData">https://github.com/TravelMapping/UserData</a>
and submit a pull request.<br /><br />
Using GitHub directly is by no means required. Unless you are an
experienced Git/GitHub user, it's usually best to submit at least your
initial file by <a href="#emailsubmission">email</a> to ensure it ends
up in the correct location and does not have any problems that would
cause errors during the site update process.<br /> <br />
<a name="gitinit"></a><a style="text-decoration:none" href="#gitinit">🔗</a> <b>Initial setup to use GitHub directly:</b><br />
<ol>
<li><a name="gitsign"></a><a style="text-decoration:none" href="#gitsign">🔗</a>
Sign up on <a href="https://github.com">https://github.com</a> and create your own GitHub user.</li>
<li><a name="gitrepo"></a><a style="text-decoration:none" href="#gitrepo">🔗</a>
Go to <a href="https://github.com/TravelMapping/UserData">https://github.com/TravelMapping/UserData</a>.</li>
<li><a name="gitfork"></a><a style="text-decoration:none" href="#gitfork">🔗</a>
Press <code>Fork</code> at top of the page.</li>
<li><a name="gitforkexe"></a><a style="text-decoration:none" href="#gitforkexe">🔗</a>
Click on your <i>GitHub user name</i> icon.</li>
</ol>
<br />
<a name="gitmod"></a><a style="text-decoration:none" href="#gitmod">🔗</a>
<b>To be done with every modification of your user list file:</b>
<ol>
<li><a name="gitopen"></a><a style="text-decoration:none" href="#gitopen">🔗</a>
Go to your user list file:
<span style="color: brown;">https://github.com/<i><your <b>GitHub</b> user name></i>/UserData/blob/master/list_files/<i><your <b>Travelmapping</b> user name></i>.list</span>.</li>
<li><a name="gitedit"></a><a style="text-decoration:none" href="#gitedit">🔗</a>
Click on the <i>Edit this file</i> icon.</li>
<li><a name="gitchange"></a><a style="text-decoration:none" href="#gitchange">🔗</a>
Make your edits or copy the content of your offline user list file.</li>
<li><a name="gitcommitdir"></a><a style="text-decoration:none" href="#gitcommitdir">🔗</a>
Select <code>Commit directly to the master branch</code> on the bottom of the page.</li>
<li><a name="gitcommit"></a><a style="text-decoration:none" href="#gitcommit">🔗</a>
Press <code>Commit changes</code>.</li>
<li><a name="gitswitch"></a><a style="text-decoration:none" href="#gitswitch">🔗</a>
Go to <span style="color: brown;">https://github.com/<i><your <b>GitHub</b> user name></i>/UserData</span> (link on top of the page).</li>
<li><a name="gitnewpull"></a><a style="text-decoration:none" href="#gitnewpull">🔗</a>
Press <code>Pull request</code>.</li>
<li><a name="gitcheck"></a><a style="text-decoration:none" href="#gitcheck">🔗</a>
Check your changes indicated in <span style="color: green; background-color: #CCFFCC;">green</span> and <span style="color: red; background-color: #FFCCCC;">red</span>.</li>
<li><a name="gitcreatepull"></a><a style="text-decoration:none" href="#gitcreatepull">🔗</a>
Press <code>Create pull request</code>.</li>
<li><a name="gitcreatepullagain"></a><a style="text-decoration:none" href="#gitcreatepullagain">🔗</a>
Press <code>Create pull request</code> again.</li>
</ol>
Your pull request will be merged by an admin before the next site update.<br />
To undo your changes, press <code>Close pull request</code>.
<br />
<br />
</li>
<li><a name="verification"></a><a style="text-decoration:none" href="#verification">🔗</a>
Data verification<br />
<br />
For advanced users, it is possible to check the changes to the <code>.list</code> file by running the site update to
create the user log file before <a href="#gitnewpull">submitting the GitHub pull request</a>. You can use the
<a href="https://github.com/TravelMapping/DataProcessing/blob/master/SETUP.md">data verification</a> tool.
<br />
<br />
</li>
</ul>
</div>
<p class="heading"><a name="listfileinfo"></a><a style="text-decoration:none" href="#hwydatamanager">🔗</a>
Specifiying unranked users and additional traveler info</p>
<div class="text">
In the <a
href="https://github.com/TravelMapping/UserData"><tt>UserData</tt> repository</a>, a csv file <tt>listfileinfo.csv</tt> is maintained where additional information can be specified.
Lines in the file have three semicolon-separated fields:
<pre>
listname;description;includeInRanks
</pre>
The <tt>listname</tt> is the TM username (case sensitive), <tt>description</tt> is a brief description of the meaning of the file (e.g., your actual name, or what subset of your travels the file contains, etc.), and <tt>includeInRanks</tt> is 1 for normal users and 0 for users that should be excluded from rankings on the site because it does not represent the actual lifetime travels of an individual. All list files that do not represent actual lifetime travels of an individual should be given an entry. An entry to specify a description can optionally be added for any user. These can be added by email request to <code>[email protected]</code> or by submitting a pull request in the repository.
</div>
<p class="heading"><a name="hwydatamanager"></a><a style="text-decoration:none" href="#hwydatamanager">🔗</a>
How to become a highway data manager</p>
<div class="text">
Some experienced users volunteer to help the project. If this interests you, start by reporting problems with existing highway data.
Those who have learned the project's structure and highway data rules and guidelines can help greatly by providing review of new highway
systems in development. Highly experienced users can learn how to plot new highway systems under the guidance of experienced contributors.
<br />
The steps to become a highway data manager are as follows:
<ol>
<li><a name="activeuser"></a><a style="text-decoration:none" href="#activeuser">🔗</a>
Become an active user and get familiar with the project structure. Create a <a href="#userlistfile">list files</a> and understand how routes are organized into highway systems.</li>
<li><a name="follow"></a><a style="text-decoration:none" href="#follow">🔗</a>
Catch up on previous discussions and follow current discussions <a href="https://forum.travelmapping.net/">on the forum</a> about highway data updates.</li>
<li><a name="report"></a><a style="text-decoration:none" href="#report">🔗</a>
Report updates and problems in existing highway systems <a href="https://forum.travelmapping.net/">on the forum</a>.</li>
<li><a name="manual"></a><a style="text-decoration:none" href="#manual">🔗</a>
Read and understand the <a href="devel/devel.php#participate">developer manual</a>.</li>
<li><a name="review"></a><a style="text-decoration:none" href="#review">🔗</a>
Participate in <a href="devel/manual/sysrev.php">peer review</a> of a preview highway system.</li>
<li><a name="structure"></a><a style="text-decoration:none" href="#structure">🔗</a>
Understand the project structure and how highway data is <a href="https://github.com/TravelMapping/HighwayData/blob/master/README.md">organized on GitHub</a>.</li>
<li><a name="develop"></a><a style="text-decoration:none" href="#develop">🔗</a>
Develop a <a href="devel/manual/sysnew.php">new highway system</a></li>
<li><a name="maintain"></a><a style="text-decoration:none" href="#maintain">🔗</a>
Take <a href="devel/manual/maintenance.php">responsibility for updates</a> in an unclaimed region, or by requesting to become the maintainer for a region from someone looking to unload some of theirs</li>
</ol>
</div>
<?php require $_SERVER['DOCUMENT_ROOT']."/lib/tmfooter.php"; ?>
</body>
</html>