On Sat, Nov 7, 2015 at 10:47 PM, Richard Welty <rwe...@averillpark.net> wrote:
> On 11/7/15 6:02 PM, Martin Koppenhoefer wrote: > > > > sent from a phone > > > >> Am 07.11.2015 um 22:31 schrieb Richard Fairhurst <rich...@systemed.net > >: > >> > >> To do it properly and > >> lessen the chance of multiple relations being accidentally created for > the > >> same route (as continues to happen with NCN routes in the UK and > elsewhere), > >> it will need either a new API search method or a dependency on Overpass. > > > > Are multiple relations for (pieces of) the same route really a big > problem? We could have multiple relations until they meet and then merge > them. > > > > > for the very long Interstate and US highways, in the US we usually > create a super relation and then have per-state relations. otherwise > you get into relations that you can barely if at all load into an editor. > I thought the problem was a 2000 member limitation in the API, though the geographic grouping really helps manageability anyway even if the network doesn't change at the jurisdiction line (ie, I 44 is still I 44 when it runs into Missouri, as opposed to OK 325 which turns into NM 456 when it crosses the Dry Cimmaron River at the border).
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
