Re: [Talk-us] [Tagging] Extremely long Amtrak route relations / coastline v. water

2020-11-22 Thread Clay Smalley
On Sun, Nov 22, 2020 at 11:12 AM Dave F via Tagging < tagg...@openstreetmap.org> wrote: > On 22/11/2020 11:24, Richard Fairhurst wrote: > > > I sincerely hope "I'm in favor of fixing" translates as "I'm planning to > fix", though I fear I may be disappointed. > > More broadly, we need to nip this

Re: [Talk-us] [Tagging] Extremely long Amtrak route relations / coastline v. water

2020-11-22 Thread Mateusz Konieczny via Talk-us
Nov 22, 2020, 17:08 by tagg...@openstreetmap.org: > Likewise we need to stop software developers from expectingcontributors > to add data purely because they can't be bothered/notcompetent enough to > write a few lines of code. (OSM-carto demandingboundaries on ways) > [citation

[Talk-us] weeklyOSM #539 2020-11-10-2020-11-16

2020-11-22 Thread weeklyteam
The weekly round-up of OSM news, issue # 539, is now available online in English, giving as always a summary of a lot of things happening in the openstreetmap world: https://www.weeklyosm.eu/en/archives/13975/ Enjoy! Did you know that you can also submit messages for the weeklyOSM? Just log

Re: [Talk-us] Extremely long Amtrak route relations / coastline v. water

2020-11-22 Thread Richard Fairhurst
[cross-posted to talk-us@ and tagging@, please choose your follow-ups wisely] Brian M. Sperlongano wrote: > It seems that we are increasingly doing things to simplify the > model because certain tooling can't handle the real level of > complexity that exists in the real world.  I'm in favor of

Re: [Talk-us] Extremely long Amtrak route relations

2020-11-22 Thread Rory McCann
On Sat, 21 Nov 2020, at 18:06, Clay Smalley wrote: > Many long-distance Amtrak trains have route relations with 1000+ > members. If I split one way that happens to be a member of one of these > routes, I end up with a changeset with a gigantic bounding box, and > often get edit conflicts due to