# How do I fix inconsistent boundaries?

 0 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 141●3●4●8 accept rate: 0%

 1 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: Identify the node in the boundary where the boundary should start to run along the coast. Split the way at that position, if that position is not already one where two separate ways meet. Identify the node where the boundary should branch inland, away from the coast. Split the way at that position (as above). If the whole boundary is one circular way, some editors may require that you mark these two nodes at once and then execute the split. Now delete the boundary way or ways that is/are supposed to coincide with the coastline. Similar to the above procedure, identify the nodes in the coastline where the boundary should join and leave the coastline, and split the way unless it is already two parts. Now drag the admin boundary node that is supposed to join the coastline onto the joining node in the coastline, and combine both nodes. (Alternatively extend the admin boundary way by one segment leading up to that coastline node.) Do the same for the other side, where the boundary leaves the coast. Finally, add all bits of coastline that now form part of your admin boundary to the boundary relation if there is one. The reason you have split the coastline before is that you can now add only the relevant bits of coastline. 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. 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 ♦ 77.0k●88●687●1191 accept rate: 24% 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 ♦
 toggle preview community wiki:

By Email:

Markdown Basics

• *italic* or _italic_
• **bold** or __bold__
• image?![alt text](/path/img.jpg "title")
• numbered list: 1. Foo 2. Bar
• to add a line break simply add two spaces to where you would like the new line to be.
• basic HTML tags are also supported

Question tags:

×120

question asked: 07 Oct '10, 19:14

question was seen: 4,564 times

last updated: 28 Nov '10, 23:37