I've started doing some work in Massachusetts and noticed that the boundaries around the coastline are aesthetically ugly, as well as inconsistent. The problem seems to be two sets of data (county and state) that don't agree. For example, see the area around Logan Airport in Boston, MA or up the coast a bit at Nahant, MA. Neither boundary follows the coastline very closely -- sometime they cut across the land, sometimes they are a ways out. Obviously they were generated to a larger, less accurate scale. What is the best way to: 1) Reconcile the two boundaries so they match, preferably with the current (or adjusted) coastline. 2) Keep the boundaries from displaying along the coastline -- I can see why the boundaries should be there (people may want to extract the shape of the state), but I think the map would look rather strange with a dotted line winding its way all around the coast. Maps such as Google's simply extend the state boundary out to sea when it reaches the coast. EDIT: OK, I see that other places do indeed have the boundary winding all the way around the coast, so I guess there's no need for 2). asked 07 Oct '10, 19:14 OceanVortex |
Note that administrative boundaries are likely to be in a relation, i.e. you will have multiple ways that together form the boundary. To solve your problem, for the first boundary:
For the second boundary, do the same but of course the coastline will already be split at the right position. answered 08 Oct '10, 21:18 Frederik Ramm ♦ Your Quote: "Do not tag the coastline as "boundary=administrative"; being in the relation is enough. Depending on the renderer in use, this will also suppress the coastline being rendered as a boundary." is this generally regarded as 'the thing to do'?. In Italy, municipality boundaries stop at the coast (not at inland lakes, though) Should the boundaries, that follow the coast really not labelled administrative, but only be in relation to the inland borders?
(09 Oct '10, 17:51)
Alexander Ro...
1
Alexander - I guess you can do whatever you want; tagging the coastline as an admin boundary is not necessary (as the information is already in the relation) but it isn't wrong either. It will, however, cause many renderers to draw a boundary depiction along the coast.
(28 Nov '10, 23:37)
Frederik Ramm ♦
|