I agree that relations are the way to for borders. <div><br></div><div>Here is an example of 3 border ways meeting at a point, but sharing National, State, Provence, and County boundary relations. It's where the New York/Vermont border meets the US/Canada/Quebec border:<br>
<div><font class="Apple-style-span" color="#021324"><span class="Apple-style-span" style="border-collapse: collapse; white-space: pre-wrap; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px;"><a href="http://www.openstreetmap.org/?lat=45.01193&lon=-73.34281&zoom=15&layers=B000FTF">http://www.openstreetmap.org/?lat=45.01193&lon=-73.34281&zoom=15&layers=B000FTF</a><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); white-space: normal; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; "></span></span></font></div>
<div><font class="Apple-style-span" color="#021324"><span class="Apple-style-span" style="border-collapse: collapse; white-space: pre-wrap; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px;"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); white-space: normal; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; ">Here's another example where the Ontario/Quebec border meets the Canada/US/New York border:</span></span></font></div>
<div><a href="http://www.openstreetmap.org/?lat=45.00428&lon=-74.66812&zoom=15&layers=B000FTF">http://www.openstreetmap.org/?lat=45.00428&lon=-74.66812&zoom=15&layers=B000FTF</a></div><div><br></div>
<div>In the Vermont area I have manually removed all but one way at each border and made that way a member of the appropriate relations. Bit of a pain, but it's mostly done now. For the US/Canada border I've found the Canadian Geobase data to be more accurate than the TIGER data.</div>
<div><br></div><div>Zeke Farwell</div><div>Burlington, VT</div><div><br></div><div><br><div class="gmail_quote">On Tue, Mar 31, 2009 at 12:22 PM, Richard Weait <span dir="ltr"><<a href="mailto:richard@weait.com">richard@weait.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">On Tue, 2009-03-31 at 10:00 -0600, James Ewen wrote:<br>
> The end result, is that I would concur that the GeoBase borders are<br>
> much closer to the real world location than the manually input border,<br>
> or the USGS imports.<br>
><br>
> So, now we need to clean up the erroneous data.<br>
><br>
> The county outlines in the US are circular ways, the GeoBase ways are<br>
> not.Will it affect rendering by cutting up the US county circular<br>
> ways, and making them part of a combined way? Can I cut the GeoBase<br>
> ways at the Alberta, BC and US confluence, and then add in a bunch<br>
> more tags to the common borders? Can we tag the same way as a<br>
> border_type: state, and also border_type:international, then do<br>
> state:left, province:right, county:left, county:right, etc?<br>
<br>
I think relations are the way to go.<br>
Tag the way with the source, uuid and attribution.<br>
Split the way at each prov/state/county/regional municipality junction.<br>
Add tags only at highest level relation for say, name, place,<br>
population, ...<br>
Include the way in Canada relation - boundary=admin, admin_level=2<br>
Include the way in USA relation - boundary=admin, admin_level=2<br>
Include the way in state/prov/muni/county relations as appropriate.<br>
<div><div></div><div class="h5"><br>
<br>
<br>
_______________________________________________<br>
Talk-us mailing list<br>
<a href="mailto:Talk-us@openstreetmap.org">Talk-us@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk-us" target="_blank">http://lists.openstreetmap.org/listinfo/talk-us</a><br>
</div></div></blockquote></div><br></div></div>