[Imports] EEA:Nationally designated areas import
Mikel Maron
mikel_maron at yahoo.com
Sun Jul 29 16:26:23 UTC 2012
Hi
>Only if these areas are verifiable and editable by mappers should they
> be in OSM!
That's overly restrictive and not reflective of actual OSM practice. That guideline would preclude the inclusion of most any administrative boundary in OSM.
The objects in this EEA database are protected areas ... parks, wilderness and wildlife protection areas, etc. These are already collected in OSM, and very frequently are the result of imports of some kind.
That's not to say that this import shouldn't be scrutinized closely, like all imports. But it should not be rejected because it refers to administrative boundaries that aren't visible on the ground.
-Mikel
* Mikel Maron * +14152835207 @mikel s:mikelmaron
>________________________________
> From: Frederik Ramm <frederik at remote.org>
>To: imports at openstreetmap.org
>Sent: Sunday, July 29, 2012 5:55 AM
>Subject: Re: [Imports] EEA:Nationally designated areas import
>
>Hi,
>
>On Sun, 29 Jul 2012 11:30:05 +0200
>Jan Kučera <kozuch82 at gmail.com> wrote:
>> I would like to discuss this import - see wiki at
>> http://wiki.openstreetmap.org/wiki/EEA:Nationally_designated_areas
>
>My main concern would be:
>
>Are these areas somehow visible on the ground - with fences, or signs,
>or other markers?
>
>Because if they are not, then our mappers have practically zero chance
>to actually edit (correct, improve) this data; and it would not make
>sense to have in OSM at all. It could simply be kept in a separate
>shape file and added by those who wish to render it, at the rendering
>stage.
>
>Only if these areas are verifiable and editable by mappers should they
>be in OSM!
>
>Additionally, I think that we need a more precise license (you write on
>the wiki page that the data is reusable commercially but a pointer to
>*their* licensing page would be good). The tagging you suggest will
>surely be commented upon by others, but I'm wary of the eea:* tags you
>suggest - they are unlikely to be of any use, once the data is modified
>in OSM (e.g. if a mapper combines two nearby areas or splits one, what
>eea:cdda:objectid should he use?).
>
>Bye
>Frederik
>
>_______________________________________________
>Imports mailing list
>Imports at openstreetmap.org
>http://lists.openstreetmap.org/listinfo/imports
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20120729/7aa5ee46/attachment.html>
More information about the Imports
mailing list