ptey
Posts: 41
Joined: 9/25/2006 From: Copenhagen, Denmark Status: offline
|
quote:
ORIGINAL: Shannon V. OKeets quote:
ORIGINAL: ptey quote:
ORIGINAL: Shannon V. OKeets quote:
ORIGINAL: Froonp quote:
ORIGINAL: Shannon V. OKeets 1 - If you can modify the coastline between Legaspi and the hex SE of it, so it looks like naval units could move out of Legaspi SE without entering the Bismarck Sea (the all sea hex due east of Legaspi) that would help. This can be done by just trimming the coastline a bit. 2 - Let's move the city symbol for Auckland further inland (to the center of the hex?) and the port symbol to where the city symbol currently is located. Visually, that will reinforce the rule that naval units can move in and out of the Auckland port to both of the sea areas. Fair enough. I'll do that. Thanks. So that just leaves figuring out/writing code for Istanbul. Another possibility would be to move the minor port one hex south-east and rename it Sorsogon? Wikipedia doesnt seem to have much information of the history of the place, but today there apparently is something called Sorsogon City located in the bay at the west coast in the northen part of the hex south east of Legaspi. http://en.wikipedia.org/wiki/Sorsogon_City The city is the combination of two former towns it says, with a total population of 151.000 (2007). Compared with 179.000 in Legaspi (2000). Maybe the Legaspi port on the WIFFE maps is actually a depiction of the combination of these minor coastal towns at the southen tip of the peninsula? With Legaspi chosen as name because it was the biggest of the towns there. With the new scale, this might not be the best option anymore. Regardless. Instead of moving Legaspi to an incorrect location, and giving it the ability of a 2 sea area port, even though it doesnt look like one on the map. I think its better to move the port one hex to the south-east and rename it to the biggest (coastal)town in the hex. Hmmm. How about we leave the Legaspi hex as the port but move the port symbol to the 4 o'clock position, instead of the 3 o'clock position? That will put it very close to the hex SE of it, though not actually in the SE hex. [We should do this anyway.] Well, the solution i proposed achieves everything (clarity of map and same function is wiffe maps), except maintaining the Legaspi name. The other solutions proposed maintain the Legaspi name but at the cost of clarity of the map. I dont like that trade-off. If moving the Legaspi port symbol to an incorrect location within the hex, i dont see an argument for not moving it over the hex boundary to the south east as well, while keeping the Legaspi name for it, if people find this to be of importance.
|