Re: [Tagging] Feature Proposal - RFC - Mapping disputed boundaries (Version 1.3)

2018-12-09 Thread Johnparis
Thank you for this thoughtful analysis, Fredrik. I will be incorporating many of these ideas in version 1.4. For one of them, the minimal boundary, I realized that it wasn't necessary, because it duplicates a zone of control. I came to this conclusion after your wrote your email but before I read

Re: [Tagging] Feature Proposal - RFC - Mapping disputed boundaries (Version 1.3)

2018-12-08 Thread Frederik Ramm
Hi, so I've read the proposals that are on the table for the first time now. I wasn't sure at first whether your proposal would break existing tools that only look at boundary=administrative but I see from the discussion page that you understand it is important to keep things working. It would be

Re: [Tagging] Feature Proposal - RFC - Mapping disputed boundaries (Version 1.3)

2018-12-08 Thread Johnparis
Thanks, Andy. I replied to some of your comments (which I also copied to the proposal's discussion page). So far as I know you're the first to publicly question the use of land boundaries, but as I fully believe in Keep It Simple, I'm happy to do that. It's not a major change, though I will probab

Re: [Tagging] Feature Proposal - RFC - Mapping disputed boundaries (Version 1.3)

2018-12-08 Thread Andy Townsend
On 05/12/2018 18:52, Johnparis wrote: I have just posted another revised version of my proposal on mapping disputed boundaries. It greatly simplifies the tagging and relation structure. One thing that would be really helpful would be to summarise those changes somewhere.  There's a whole pag

[Tagging] Feature Proposal - RFC - Mapping disputed boundaries (Version 1.3)

2018-12-05 Thread Johnparis
I have just posted another revised version of my proposal on mapping disputed boundaries. It greatly simplifies the tagging and relation structure. Thanks to everyone who gave public and private feedback. I've archived some of the comments that are no longer applicable. The proposal is here: htt