User:MiniMapper/Oakley
The following are the rules.
Forest
Forest makes up about 3/4 of Oakley.
Each township has a forest relation.
The forest should not have any tags unless it is also used be another thing. It should be in the relation like for example Rivister Township Wood. See how everything forest is in the relation.
Rivers
Rivers usually have detailed coasts. It adds detail and gives others an idea of how large the river is. Most of the time I will find a river with similar watershed size in New England and find its width around that area then use the Parallel Tool (SHIFT + P) and split the width in half and put that on both ends. Then, add two or four more rows 10ft to any side. Once that it done you use the Draw Tool (Plugin, look it up in the plugins area. SHIFT + F) and try to draw within those lines. You try to have the line go in all areas and also out or in. Not in by far (no less than 10ft) but for out you can go about 20ft out. Anything past that distance should become small marshes.
Creeks
Creeks don't need to be detailed. They can, but it is not needed. An example of a detailed stream is the Rest Creek. Look! It even has the marsh sides on it! NOTE: The marshes are in the Rest Creek due to how flat it is there and almost always has a marsh except in Dry Seasons. A smaller example of a undetailed creek is this unnamed creek by What. If you want one that is detailed without the mash sides there is the Werser Creek. Some of my older work in Oakley
Presets
Oakley comes with a set of presets. They are made for many random things. It is best to map with them due to them being made to streamline the process for almost anything that I deem too slow. There should be a download button here for them if you want to download them sometime when I get a website for this. It would be more like copy the code into an .xml file.
Towns
The rules for towns are quite delusional lmao
Node
The node part of the town (or where the name is seen) has a few rules.
- The node should be placed in the center or a central point of that city or town.
- The node should have 'is_in:county','is_in:township', and 'is_in:state=Oakley'
- The node should have its population
The easiest way to fill in these requirements is by using the Oakley Location Preset. It will show all the fields and let you fill them in without going to another town and doing the classic CTRL + C CTRL + V move.
Relation
All towns should have their border and have it as a relation. It has the same requirements as far as the same is_in tags and its population. There is also a table for what admin level does what. Prepare for the most broken and painful table of your life.
Admin Level (4/State) | 5 | 6 | 7 | 8 | 9 | 10 |
---|---|---|---|---|---|---|
Oakley | TBD | County | Township | Town | Borough | TBD |
City | TBD | |||||
Patch | TBD |
Highways
Primary
Number | Length (miles) | To-From | Status |
---|---|---|---|
1 | 79.2 | North-South | |
2 | IP | North-South | |
3 | IP | IP | |
4 | IP | IP | |
5 | IP | Coast-OA-2 | |
6 | IP | IP | |
7 | IP | IP | |
8 | IP | IP | |
9 | IP | IP | |
10 | IP | IP | |
11 | IP | IP | |
12 | IP | IP | |
13 | IP | IP | |
14 | IP | IP | |
15 | IP | IP | |
16 | IP | IP | |
17 | IP | IP | |
18 | IP | IP | |
19 | IP | IP | |
20 | IP | IP | |
21 | IP | IP | |
22 | IP | IP | |
23 | IP | IP | |
24 | IP | IP | |
25 | IP | IP | |
26 | IP | IP | |
27 | IP | IP | |
28 | IP | IP | |
29 | IP | IP | |
30 | IP | IP | |
31 | IP | IP | |
32 | IP | IP | |
33 | IP | IP | |
34 | IP | IP | |
35 | IP | IP | |
36 | IP | IP | |
37 | IP | IP | |
38 | IP | IP | |
39 | IP | IP | |
40 | IP | IP | |
41 | IP | IP | |
42 | IP | IP | |
43 | IP | IP | |
44 | IP | IP | |
45 | IP | IP | |
46 | IP | IP | |
47 | IP | IP | |
48 | IP | IP | |
49 | IP | IP | |
50 | IP | IP | |
51 | IP | IP | |
52 | IP | IP | |
53 | IP | IP | |
54 | IP | IP | |
55 | IP | IP | |
56 | IP | IP | |
57 | IP | IP | |
58 | IP | IP | |
59 | IP | IP | |
60 | IP | IP | |
61 | IP | IP | |
62 | IP | IP | |
63 | IP | IP | |
64 | IP | IP | |
65 | IP | IP | |
66 | IP | IP | |
67 | IP | IP | |
68 | IP | IP | |
69 | IP | IP | |
70 | IP | IP | |
71 | IP | IP | |
72 | IP | IP | |
73 | IP | IP | |
74 | IP | IP | |
75 | IP | IP | |
76 | IP | IP | |
77 | IP | IP | |
78 | IP | IP | |
79 | IP | IP | |
80 | IP | IP | |
81 | IP | IP | |
82 | IP | IP | |
83 | IP | IP | |
84 | IP | IP | |
85 | IP | IP | |
86 | IP | IP | |
87 | IP | IP | |
88 | IP | IP | |
89 | IP | IP | |
90 | IP | IP | |
91 | IP | IP | |
92 | IP | IP | |
93 | IP | IP | |
94 | IP | IP | |
95 | IP | IP | |
96 | IP | IP | |
97 | IP | IP | |
98 | IP | IP | |
99 | IP | IP | |
100 | IP | IP |
Subroutes
1
Number | Length (miles) | Location | Status |
---|---|---|---|
1A | 5.1 | Tanbrow-FS-1 | |
1B | IP | IP |
12
Number | Length (miles) | Location | Status |
---|---|---|---|
12A | 6.0 | Downtown Fallport-OA-271 |
92
Number | Length (miles) | Location | Status |
---|---|---|---|
92S | IP | IP |