[OSM-talk] Corine Land Cover becomes a potential OSM data source...

[Martijn van Exel]

Interesting. We will be having the same kind of import versus existing
data issue once more (if and) when the Nationaal Wegenbestand
(National road database) is made available by the transport ministry.
I did not give it much thought yet - may be some of my Dutch
co-OSM-ers will have a more elaborate train of thought - but I was
thinking along similar lines: import the data but tag it so that it
won't show up in the map. Have a dedicated map layer on a local server
that can be used to check existing user data, may be even a Potlatch
layer if at all possible. I guess JOSM support would be easy enough
through the WMS plugin.

Other noteworthy fact is that we have had this issue before, in 2007
when importing the AND data. There was much discussion then on how to
approach, and as far as I can remember we had an opt-out system then:
if you don't want your current user data overwritten by AND data, you
could indicate such and this way some particularly well mapped areas
were untouched by the AND data. But back then, the Netherlands had
only isolated pockets of good OSM coverage.

martijn van exel -+- mvexel at gmail.com -+- http://www.schaaltreinen.nl/



On Thu, May 14, 2009 at 12:23, Christoph Boehme <christoph at b3e.net> wrote:
> Hi
>
> Pieren wrote:
>> But we are facing the problem of how to detect and resolve the
>> conflicts with existing landuse data in OSM which are usually (but not
>> always) more accurate (Yahoo imagery or french cadastre).
>> I know we are not the first country having this problem and we would
>> like to know how it was solved with other mass imports.
>
> We are currently importing public transport information for the UK
> (NaPTAN) and are having a similar problem with existing data in OSM. Our
> approach is to tag the imported data specially so that it can easily be
> found in the database but does not show up on the map (i.e. all imported
> bus stops are tagged with source=naptan_import but do not have
> highway=bus_stop tag). Mappers can then check the imported data and
> "activate" bus stops by adding a highway=bus_stop tag to it or copy the
> imported tags over to an existing OSM bus stop.
>
> To aid this task a web-based tool is being developed at the moment. The
> tool displays all bus stops from OSM and all newly imported stops on a
> map and can find pairs of similar bus stops in the existing and the new
> dataset (based on proximity and similar names). The user can then easily
> select pairs and merge them.
>
>        Christoph
>
>
>
>
>
> _______________________________________________
> talk mailing list
> talk at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk
>