p.org
> Subject: Re: [OSM-talk] Corine Land Cover becomes a potential OSM data
> source...
>
> On Thu, May 28, 2009 at 11:17 AM, Jaak Laineste (Nutiteq)
> wrote:
> > Hello,
> > are there separate general discussion lists or wiki regarding this
> > Corine land data i
On Thu, May 28, 2009 at 11:17 AM, Jaak Laineste (Nutiteq)
wrote:
> Hello,
> are there separate general discussion lists or wiki regarding this
> Corine land data import ? We just got hands on and permissions for our
> local (Estonian) data, and some practical questions and ideas have
> arisen.
>
>
> Cheers
>
> Andy
>
>>-Original Message-
>>From: talk-boun...@openstreetmap.org [mailto:talk-
>>boun...@openstreetmap.org] On Behalf Of Pieren
>>Sent: 13 May 2009 10:13 PM
>>To: OSM
>>Subject: [OSM-talk] Corine Land Cover becomes a potential OSM data
&
The French community has been working hard on getting tags converted
to OSM format.
A wiki has been created. We have also been analyzing a bit the data to
see if it was overlapping with existing polygons to facilitate import
of data.
It is nice to see that the other countries are following the rele
Andy Robinson (blackadder-lists) wrote:
> Pieren,
>
> A new OSMF Working Group is being formed to support groups and individuals
> with the import of new public and private data. I've copied SteveC who will
> be leading the group so that your email reaches the new groups radar.
>
>
I am happy to
Steve Singer sympatico.ca> writes:
>
> On Thu, 14 May 2009, Pieren wrote:
>
> For the Canadian GeoBase road import I've been using a plugin to JUMP called
> RoadMatcher[1] to that detects common roads between two datasets. I've then
> been excluding ones that aren't likely to not cause confli
On Fri, May 15, 2009 at 3:05 PM, Steve Singer wrote:
> On Thu, 14 May 2009, Pieren wrote:
>
> For the Canadian GeoBase road import I've been using a plugin to JUMP called
> RoadMatcher[1] to that detects common roads between two datasets. I've then
> been excluding ones that aren't likely to not c
On Thu, 14 May 2009, Pieren wrote:
For the Canadian GeoBase road import I've been using a plugin to JUMP called
RoadMatcher[1] to that detects common roads between two datasets. I've then
been excluding ones that aren't likely to not cause conflicts.
A few more details at:
http://wiki.openstree
On Thu, May 14, 2009 at 16:52, Lennard wrote:
> Martijn van Exel wrote:
>>
>> 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 no
Martijn van Exel wrote:
> 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
> c
On 14/05/09 11:23, Christoph Boehme wrote:
> 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 s
Thanks for your suggestions.
In our case, it is more about 80% of the import dataset that will
stay. And we speak about e.g. forests, tree plantations, agricultural
areas,etc which is a huge surface in France. Tha't why our preference
would go to some solution making the import as much as possible
Hi,
Martijn van Exel wrote:
> 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 Dutc
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 elabora
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 kn
On Thu, May 14, 2009 at 11:05 AM, Andy Robinson (blackadder-lists)
wrote:
> Pieren,
>
> A new OSMF Working Group is being formed to support groups and individuals
> with the import of new public and private data. I've copied SteveC who will
> be leading the group so that your email reaches the new
: talk-boun...@openstreetmap.org [mailto:talk-
>boun...@openstreetmap.org] On Behalf Of Pieren
>Sent: 13 May 2009 10:13 PM
>To: OSM
>Subject: [OSM-talk] Corine Land Cover becomes a potential OSM data
>source...
>
>at least in France.
>
>The Corine Land Cover (CLC) is refering t
at least in France.
The Corine Land Cover (CLC) is refering to a european programme
establishing a computerised inventory on land cover of the 27 EC
member states and other European countries, at an original scale of 1:
100 000, using 44 classes of the 3-level Corine nomenclature.
It is produced
18 matches
Mail list logo
