[Imports] EEA:Nationally designated areas import

[Jan Kučera]

Hello again,

2012/7/29 Frederik Ramm <frederik at remote.org>:
> 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!

I understand core of this point. These are "artificial" boundaries
(with a physical "sign" placed sometimes in the field - varies greatly
country by country I can imagine, but is nothing useful for mapping)
but as Mikel says currently such areas are present in OSM and there
are no "official" restrictions for mapping these known to me so far...
Surely these areas will not change a lot in the future, so the
advantage of having them in OSM is just using one single
platform/database with single API as for other OSM-objects... like
this we could surely delete all national borders etc... would not make
a lot of sence either.

I understand the possibility od having a standalone data just for
rendering though... is there a common practice how to include these
into main osm-mapnik layer (= without having these in main database)?

>
> 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).

See http://www.eea.europa.eu/legal/copyright - they want attribution
(EEA or local sources).

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?).

Tagging will be subject to further review as I said. Some "eea:" tags
seem useful to me though - like SITECODE or PARENTISO - these are
their identifiers which could help update data in the fugure from
their source again I think...

>
> Bye
> Frederik
>
> _______________________________________________
> Imports mailing list
> Imports at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/imports