> From: Dan Charrois [mailto:d...@syz.com]
> Subject: Re: [Talk-ca] Internal CanVec conflicts
>
> Usually, in remote areas of the north that I've dealt with, there is
> often little else already there than the Landsat lakes. And usually, in
> a given tile, there is us
Usually, in remote areas of the north that I've dealt with, there is often
little else already there than the Landsat lakes. And usually, in a given
tile, there is usually just a handful of lakes.
In pretty much every case I've dealt with so far, I've replaced the Landsat
lakes with Canvec dat
=shpak_landsat_lakes and erase the selected objects.
Too risky?
Pierre
>
> De : Pierre Béland
>À : "talk-ca@openstreetmap.org"
>Envoyé le : Jeudi 15 novembre 2012 12h48
>Objet : Re: [Talk-ca] Internal CanVec conflicts
>
>
>Nort
"
>Envoyé le : Jeudi 15 novembre 2012 11h06
>Objet : Re: [Talk-ca] Internal CanVec conflicts
>
>A really simple answer that gets lost is this:
>
>Did you make the edits to the best of your ability, and your edits add value
>to the OSM project?
>
>If so, then
A really simple answer that gets lost is this:
Did you make the edits to the best of your ability, and your edits add value to
the OSM project?
If so, then it was the right thing to do.
We all bring different levels of ability, and may not do things perfectly
according to the "experts", but i
> From: Tom Taylor [mailto:tom.taylor.s...@gmail.com]
> Subject: Re: [Talk-ca] Internal CanVec conflicts
>
> I've just performed my first edits, in our neighbourhood. One thing I
> noticed was that some of the buildings are duplicates. I assume this is
> part of what you
Hi Tom:
welcome to OSM and congratulations on your first edits! Yes, it sounds
like you did the right thing. One thing to look out for: Bing images
are not always aligned 100% -- they can be offset by several meters.
Usually this is not a problem but if there are any GPS traces
available in your ar
I've just performed my first edits, in our neighbourhood. One thing I
noticed was that some of the buildings are duplicates. I assume this is
part of what you are talking about when you mention internal CanVec
conflicts. In the case of a local public school, I deleted one of the
copies and drag
On 14-11-2012 19:37, Pierre Béland wrote:
Pierre Lamoureux***:* Mardi 13 novembre 2012 23h54
**<
Je suis un nouveau participant au projet OSM, par contre je ne suis
pas un débutant en cartographie et je saisis assez bien les termes de
la discussion en cours
En passant, j’ai un peu d’expé
Pierre Lamoureux: Mardi 13 novembre 2012 23h54
<
Je suis un nouveau participant au projet OSM, par contre je ne suis pas un
débutant en cartographie et je saisis assez bien les termes de la discussion en
cours
En passant, j’ai un peu d’expérience dans l’utilisation de FME pour convertir
l
.
Pierre Lamoureux
Quebec, Qc
De : Pierre Béland [mailto:infosbelas-...@yahoo.fr]
Envoyé : 13 novembre 2012 16:22
À : Frank Steggink; talk-ca@openstreetmap.org
Objet : Re: [Talk-ca] Internal CanVec conflicts
Frank Steggink november 13 2012 15h37
answering Paul Norman
> However, t
> De : Frank Steggink
>À : talk-ca@openstreetmap.org
>Envoyé le : Mardi 13 novembre 2012 15h37
>Objet : Re: [Talk-ca] Internal CanVec conflicts
>
>Hi Paul,
>
>It probably won't come to you as a surprise if I would say it is acceptable,
>but to
Hi Paul,
It probably won't come to you as a surprise if I would say it is
acceptable, but to a certain degree. A map with no data is not a map. A
map with inconsistent data is still a map, but obviously something is
not right. A map with perfectly consistent data doesn't need to tell the
trut
On Monday, November 12, 2012 4:36 PM, Paul Norman wrote:
> > From: Brian Gamberg [bgamb...@nf.sympatico.ca]
> > Sent: Monday, November 12, 2012 11:01 AM
> > To: Talk-ca@openstreetmap.org
> > Subject: [Talk-ca] Internal CanVec conflicts
> >
> > The
I ran into many of the same issues when I started importing Canvec data for
the province of Newfoundland and Labrador. But, in my case, the arguments I
had were with myself.
When I started, most of the province was a blank slate with only the (PGS)
coastline in the OSM database. There wer
I've already said what I have to say about the issue at hand in
earlier discussion. A more lighthearted remark: whenever I feel
depressed about some Canvec-related issue I load up JOSM, pick a
random location in the US, and spend half an hour fixing TIGER data.
It's a very effective therapeutic...
ssage-
From: Dan Charrois [mailto:d...@syz.com]
Sent: November-11-12 02:47
To: Talk-CA OpenStreetMap
Subject: Re: [Talk-ca] Internal CanVec conflicts
> "Is it the communities view that it is okay to import CanVec without
> reconciling the internal differences between the layers?"
> "Is it the communities view that it is okay to import CanVec without
> reconciling the internal differences between the layers?"
>
> I believe it is. The great thing about OSM data is it is not written in
> stone. An import or edit can be changed in the future. The data is
> inserted for use
: talk-ca@openstreetmap.org
Subject: Re: [Talk-ca] Internal CanVec conflicts
> From: Bryan Crosby [mailto:azubr...@gmail.com]
> Sent: Saturday, November 10, 2012 8:33 AM
> To: talk-ca@openstreetmap.org
> Subject: Re: [Talk-ca] Internal CanVec conflicts
> This will be my fir
> From: Bryan Crosby [mailto:azubr...@gmail.com]
> Sent: Saturday, November 10, 2012 8:33 AM
> To: talk-ca@openstreetmap.org
> Subject: Re: [Talk-ca] Internal CanVec conflicts
> This will be my first and only response to this. If the Canadian OSM
> community feels we need to
at in doing so, 80% of the country will receive no data, and the
community will be down one mapper.
B
-Original Message-
From: Paul Norman [mailto:penor...@mac.com]
Sent: November-10-12 4:38 AM
To: talk-ca@openstreetmap.org
Subject: [Talk-ca] Internal CanVec conflicts
CanVec da
CanVec data comes from multiple sources and this can lead to internal
inconsistencies. A common case is a new development where there used to be
trees. The tree data in CanVec might be older and show an area as forested
while there is newer road data indicating that the area has been developed.
An
22 matches
Mail list logo
