6-mile Hex Map - Revision history

Tao alexis at 17:39, 19 March 2025

2025-03-19T17:39:13Z

Tao alexis at 16:37, 17 February 2025

2025-02-17T16:37:46Z

Tao alexis: /* Colour */

2025-02-17T16:36:57Z

Colour

Tao alexis at 16:30, 17 February 2025

2025-02-17T16:30:41Z

Tao alexis at 19:11, 14 December 2022

2022-12-14T19:11:21Z

Tao alexis: /* Colour */

2022-12-14T18:50:26Z

Colour

Tao alexis: /* Routes */

2022-12-14T18:24:34Z

Routes

Tao alexis: /* Routes */

2022-12-14T18:21:04Z

Routes

Tao alexis: /* Routes */

2022-12-14T18:20:04Z

Routes

Tao alexis: /* Routes */

2022-12-14T18:19:25Z

Routes

@@ Line 18: / Line 18: @@
 These coordinates are in decimal format, whereas Google Earth interprets coordinates in degrees, minutes, and seconds. To use them effectively, they must be converted and formatted in a way that allows for direct copying and pasting into the Google Earth search window.
-To accomplish this, we draw out the four corners of both orange-coloured hexes in the table below, applying Excel formulas for conversion. A final column provides a "pastable" result, allowing instant input into Google Earth for precise navigation. Once entered, the program zooms in dynamically, revealing a landscape that may feature a dense forest, a rugged mountain, a quiet village, or an open field—bringing the map to life in real-world imagery.
+To accomplish this, we draw out the four corners of both orange-coloured hexes in the table below, applying Excel formulas for conversion. A final column provides a "pastable" result, allowing instant input into Google Earth for precise navigation. Once entered, the program zooms in dynamically, revealing a landscape that may feature a dense forest, a rugged mountain, a quiet [[Village|village]], or an open field—bringing the map to life in real-world imagery.
 {| class="wikitable" style="float:left; margin-right: 25px; text-align: center; background-color:#d4f2f2;"

@@ Line 1: / Line 1: @@
 <div><ul>
-<li style="display: inline-block; float: right; margin-left: 15px;"> [[File:Lower Bukovina.png|thumb|none|490px|6-mile map of Lower Bukovina, in central Ukraine.]]</li>
+<li style="display: inline-block; float: right; margin-left: 0px;"> [[File:Lower Bukovina.png|thumb|none|525px|6-mile map of Lower Bukovina, in central Ukraine.]]</li>
-<li style="display: inline-block; float: right; margin-left: 15px; "> [[File:Divided 20-mile hex.jpg|thumb|none|210px|]]</li>
+<li style="display: inline-block; float: right; margin-left: 15px; "> [[File:Divided 20-mile hex.jpg|thumb|none|280px|]]</li>
 </ul></div>

← Older revision		Revision as of 16:36, 17 February 2025
Line 134:		Line 134:

	For those who may be interested in more content about mapmaking, since Alexis' blog, [https://tao-mapmaking.blogspot.com/ Tao's Mapmaking].		For those who may be interested in more content about mapmaking, since Alexis' blog, [https://tao-mapmaking.blogspot.com/ Tao's Mapmaking].
		+
		+	== Conclusion ==
		+	The process can be repeated with patience to produce truly startling extensive game maps that makes a powerful impression with players. As more sections are generated, the realism of the world comes to life and the setting grows in continuity and depth.
		+
		+
		+	See [[6-mile Sheet Maps]]
		+
		+	[[Category: Reviewed]]

@@ Line 6: / Line 6: @@
 '''6-mile hex maps''' are zoomed-in maps derived from [[20-mile Hex Map|20-mile hex maps]], using a complex procedure of map drawing and random generation deriving from a map's [[Infrastructure|infrastructure]] and real-world topography and place names.
 __TOC__
-The designation "6-mile" is an inaccurate description.  6-mile hexes are derived from splitting a 20-mile hex, as shown in the image below, and are in fact 6.67 mi. in diameter, not six.  Nonetheless, the "6-mile" appellation is used as a simplification.
+The designation "6-mile" is an inaccurate description. 6-mile hexes are derived from splitting a 20-mile hex, as shown in the image below, and are in fact 6.67 miles in diameter, not six. Nonetheless, the "6-mile" appellation is used as a simplification.
 == Generation Procedure ==
-Once the infrastructure of a given 20-mile hex has been determined, and all of its surrounding hexes as well, it's possible to create a rectangular "section" of 6-mile hexes.
+Once the infrastructure of a given 20-mile hex and its surrounding hexes has been determined, a rectangular "section" of 6-mile hexes can be created.
 [[File:Falling Rain Elevation Data.png|right|350px|thumb]]
-This section includes two 20-mile hexes.  Each 20-mile hex, everywhere in the world, is designated according to the latitude and longitude it represents.  This enables us to locate that section on [https://earth.google.com/web/ GoogleEarth].
+This section includes two 20-mile hexes. Each 20-mile hex, regardless of location, is designated based on its corresponding latitude and longitude. This allows us to precisely place the section on [https://earth.google.com/web/ Google Earth].
-The image on the right provides a cacophony of numbers that we use to identify which hex falls into which set of coordinates.  These are organised by "rings," the number of hexes this particular line of hexes is from the North Pole (ring 1).  In the image shown, "ring 143" indicates the North Pole is 142 x 20 miles away.  The latitude of ring 143 is between 48.51 N and 48.79 N.  The left-hand hex, containing the [[Settlement|settlement]] of Uman in Kiyev, has a longitude between 30.21 E and 30.62 E.  The right-hand hex, in Vassia, has a longitude between 30.63 E and 31.04 E.
+The image on the right presents a dense array of numbers used to determine which hex corresponds to specific coordinates. These coordinates are organized by "rings," which indicate how many hexes a particular row is from the North Pole (ring 1). In the given image, "ring 143" means the North Pole is 142 × 20 miles away. The latitude of ring 143 falls between 48.51° N and 48.79° N. The left hex, containing the [[Settlement|settlement]] of Uman in Kiyev, is situated between 30.21° E and 30.62° E longitude. The right hex, located in Vassia, spans from 30.63° E to 31.04° E longitude.
-These coordinates are in decimal format, while GoogleEarth comprehends coordinates in degrees, minutes and seconds.  So these numbers have to be translated - and, to save time, put into a format that can be copied and pasted into the GoogleEarth search window.
+These coordinates are in decimal format, whereas Google Earth interprets coordinates in degrees, minutes, and seconds. To use them effectively, they must be converted and formatted in a way that allows for direct copying and pasting into the Google Earth search window.
-Thus we draw out the four corners of both orange-coloured hexes on the table below, showing the excel formulas we'll use and a final column for "pastable" answer.  This last can be copied and pasted into the GoogleEarth search window and it will take us right to the correct spot.  For anyone familiar with GoogleEarth, it's fascinating to watch the program zoom into the data once it's entered, bringing us close up to a group of trees, a mountain, a little village or a field:
+To accomplish this, we draw out the four corners of both orange-coloured hexes in the table below, applying Excel formulas for conversion. A final column provides a "pastable" result, allowing instant input into Google Earth for precise navigation. Once entered, the program zooms in dynamically, revealing a landscape that may feature a dense forest, a rugged mountain, a quiet village, or an open field—bringing the map to life in real-world imagery.
 {| class="wikitable" style="float:left; margin-right: 25px; text-align: center; background-color:#d4f2f2;"
@@ Line 50: / Line 50: @@
 As can be seen, the 6-mile hexes can be seen overlaid atop the 20-mile hexes beneath, one with the settlement of Uman and one without.  To the west and north are 6-mile hexes that have been created.  Large white numbers indicate the infrastructure for each 20-mile hex.  These numbers are important for indicating the direction of roads into and out of the section we're mapping.
-Our first steps will be to provide basic information for these two hexes based on GoogleEarth's information.  Take note of the blue [[River |rivers]] that have already been added to the map.  These are ''guesses'' ... including the thicker blue river that is part of the 20-mile map underneath.  We'll want to correct those river courses.
+Our first steps will be to provide basic information for these two hexes based on GoogleEarth's information.  Take note of the blue [[River |rivers]] that have already been added to the map.  These are ''guesses''... including the thicker blue river that is part of the 20-mile map underneath.  We'll want to correct those river courses.
 We also want to get a more accurate location for Uman.  Occasionally the initial plotting is significantly incorrect.  In addition, a series of brown dirt roads are also shown, cut-off at the edge of those hexes that are undone.  The location of these roads is also a ''guess''.  We don't know yet, except for Uman, what villages or towns might be here, not until we generate that information.  For now, however, our first step is to address the section's topography.

@@ Line 74: / Line 74: @@
 These 14 points are distributed throughout the 20-mile hexes '''seven''' 6-mile hexes.  These seven hexes are called a "[[Hex Group|hex group]]."  Note that Ulan is in none of these.  To save time, I've built an [https://docs.google.com/spreadsheets/d/1OD6XRL4yDHfS5N0F7SFIspfWpy72bYB2/edit#gid=1269951915 excel program] that generates the distribution automatically, which the reader can use.  By putting 14 in the yellow box, I can generate which hex type occurs in which part of the hex group, as shown.
-The image indicates that there are two type-5 hexes; one type-6; and one type-7.  Putting these in order, the type-5 hexes go in the 1st and the 2nd positions — far left and bottom right.  The type-6 goes in the 3rd position, top right.  The remaining hexes are all type-7.
+The image indicates that there are two [[Type-5 Hex|type-5]] hexes; one [[Type-6 Hex|type-6]]; and one [[Type-7 Hex|type-7]].  Putting these in order, the type-5 hexes go in the 1st and the 2nd positions — far left and bottom right.  The type-6 goes in the 3rd position, top right.  The remaining hexes are all type-7.
 [[File:Hex Group.png|left|525px|thumb|Hex Group generation for the left-hand hex.]][[File:7-2b.jpg|right|60px|thumb]]
@@ Line 82: / Line 82: @@
 === Places ===
-The results of this generation produce two type-4 hexes, four type-5 and one type-7.  Hex types between 1 and 4 are awarded a minor population centre, so the two type-4 hexes are each given a village-sized place.  An existing centre is taken from GoogleEarth, in the approximate place which the type-4 hex covers.
+The results of this generation produce two [[Type-4 Hex|type-4]] hexes, four type-5 and one type-7.  Hex types between 1 and 4 are awarded a minor population centre, so the two type-4 hexes are each given a village-sized place.  An existing centre is taken from GoogleEarth, in the approximate place which the type-4 hex covers.
 There are typically three to five places that can be chosen; zooming out on GoogleEarth reveals the most important, but in fact any of them might have existed in the 17th century.  Most, or all, won't have, so which choice is made doesn't matter much.  Again, this isn't about accuracy.  Usually, a name that's easiest for the players to say can be chosen, but even this isn't always possible.

← Older revision		Revision as of 18:50, 14 December 2022
Line 129:		Line 129:
	== Colour ==		== Colour ==
	The very last step is to add in the border between Kiyev and Vassia, and to colour the hexes. Each hex type has it's own colour, so the general "feel" of the hex map can be understood at a glance. Brighter colours mean people; dull green means backcountry farmlands.		The very last step is to add in the border between Kiyev and Vassia, and to colour the hexes. Each hex type has it's own colour, so the general "feel" of the hex map can be understood at a glance. Brighter colours mean people; dull green means backcountry farmlands.
		+
		+	[[File:Finished Section.png\|right\|700px\|thumb]]
		+	Showing, then, is the finished product, without the background visible. The process seems excessively complicated, but in actual fact much of this is the need for unfamiliar technical terms to describe what's going on. Once two or three hundred sections are completed (I've done more than 700), the procedure becomes quite familiar so that it's easy to continue with section after section.
		+
		+	For those who may be interested in more content about mapmaking, since Alexis' blog, [https://tao-mapmaking.blogspot.com/ Tao's Mapmaking].

← Older revision		Revision as of 18:24, 14 December 2022
Line 125:		Line 125:
	</gallery>		</gallery>

−	The dead ends are intentional.	+	The dead ends are intentional. They lead to [[Hamlets\|hamlets]], not shown on the map, and also allow further progress for travellers along foot paths, utterly impractical for carts. These are also not shown on the map, as they're everywhere people are.
		+
		+	== Colour ==
		+	The very last step is to add in the border between Kiyev and Vassia, and to colour the hexes. Each hex type has it's own colour, so the general "feel" of the hex map can be understood at a glance. Brighter colours mean people; dull green means backcountry farmlands.

← Older revision		Revision as of 18:21, 14 December 2022
Line 124:		Line 124:
	File:Roads 8.png\|		File:Roads 8.png\|
	</gallery>		</gallery>
		+
		+	The dead ends are intentional.

← Older revision		Revision as of 18:20, 14 December 2022
Line 111:		Line 111:

	This leaves five cart tracks. Starting with Uman, we link up a cart track from there to the dirt road nearby (5). We connect a cart track to the hexes at the top, both left and right (6), using the right hand road to set up a crossroads for the dirt road connecting the other type-5 hex. We connect that road, finished up the hex (7). That leaves one more cart track, which we connect between the dirt road (adjusting it) in the infrastructure 27 hex to Skaleva (8).		This leaves five cart tracks. Starting with Uman, we link up a cart track from there to the dirt road nearby (5). We connect a cart track to the hexes at the top, both left and right (6), using the right hand road to set up a crossroads for the dirt road connecting the other type-5 hex. We connect that road, finished up the hex (7). That leaves one more cart track, which we connect between the dirt road (adjusting it) in the infrastructure 27 hex to Skaleva (8).
		+
		+	These eight changes are arranged as a slide show; click on the first image and use the arrows to go forward and back.

	<gallery mode=slideshow=175px style="text-align:left">		<gallery mode=slideshow=175px style="text-align:left">

@@ Line 116: / Line 116: @@
 File:Roads 2.png|
 File:Roads 3.png|
 </gallery>