<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Another popular view is that these are problems for the renderer/editor, not intrinsic issues with the data. <sarcasm>Tag as you see fit and the renderers/editors will catch up!</sarcasm> The fact that coastlines are difficult to maintain with the current toolset is not an argument to not have them in OSM.</p>
<p>Back on topic: how do you phrase an objective rule, or at least well-worded guidelines, which allow admin boundaries but disallow time zone boundaries? I wonder where the UK ceremonial counties, fire department areas, national parks etc will end up. My point is, gut feelings aside, that it is not reasonable to single out TZ boundaries for this deprecation.</p>
<p>On 2013-10-21 13:14, Pieren wrote:</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<pre>On Mon, Oct 21, 2013 at 11:19 AM, Colin Smale <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</pre>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px">The traditional consensus is that anyone can put anything in OSM</blockquote>
<pre>It was only a consensus in the group of contributors thinking that
(which is then easy to reach a consensus).
This remembers me similars discussions about:
- hi-res aerial imagery coverage by huge polygons (Yahoo!)
- underground facilities (sewer, parkings, phone cables)
- geologic stuff (mountain strings, stratifications)
All such features have the problem that they are often not verifiable
(underground) or creates high density maps with many different layers
where none of the OSM editors can handle easily and correctly
different layers making the map "unreadable" and "unworkable"
(parcels, sewer, air lines) or that polygons are so big that nobody is
able to maintain them correctly (coastlines) or too fuzzy to represent
something real with a sharp line (e.g. mountains strings, valleys). So
no, you cannot say that OSM can be a garbage collector for all data as
soon as you can draw them on a map.
talk mailing list