On Aug 10, 2009, at 7:45 AM, Nop wrote:
>
> Hi!
>
> Apollinaris Schoell schrieb:
>>> To prevent accidential damage, there could be a warning when you are
>>> using it in a dangerous or most likely harmful way. E.g. more than
>>> 10
>>> ways are selected or using it on ways that already have les
2009/8/10 Nop :
>
> Hi!
>
> Apollinaris Schoell schrieb:
>>> To prevent accidential damage, there could be a warning when you are
>>> using it in a dangerous or most likely harmful way. E.g. more than 10
>>> ways are selected or using it on ways that already have less than 10
>>> nodes.
IMHO let n
Hi!
Apollinaris Schoell schrieb:
>> To prevent accidential damage, there could be a warning when you are
>> using it in a dangerous or most likely harmful way. E.g. more than 10
>> ways are selected or using it on ways that already have less than 10
>> nodes.
>>
> use the plugin and if you miss
>
> To prevent accidential damage, there could be a warning when you are
> using it in a dangerous or most likely harmful way. E.g. more than 10
> ways are selected or using it on ways that already have less than 10
> nodes.
>
use the plugin and if you miss features file a trac ticket.
but you
Hi!
Andre Hinrichs schrieb:
> Problem for the JOSM plugin is that this option is not automatically
> added to the preferences and hidden in the description in the WIKI and
> you have to actively search for this option.
+1
As long as you don't have any idea that such an option exists you don't
Hi!
Martin Koppenhoefer schrieb:
> 2009/8/9 Liz :
>> I concur
>> I found about 350 -400 km of highway uploaded (twice) with points at one per
>> second at 100kmh travel speed
>> Once uploaded and made into a way, and then the way deleted without removing
>> the points, then uploaded again
>> and
Am Samstag, den 08.08.2009, 14:42 +0200 schrieb Martin Koppenhoefer:
> An example from the result of the current tidy-points-function here:
> http://trac.openstreetmap.org/attachment/ticket/2148/090808_potlatch_tidy-points_.png
The exsample shows a problem which I also had once until I found that
On Aug 9, 2009, at 2:23 PM, Liz wrote:
> On Mon, 10 Aug 2009, Nop wrote:
>> Some people mentioned that the default settings of these tools are
>> very
>> agressive - this is true and a more lenient approach might produce
>> much
>> better results. But then, I have not seen any options to chan
2009/8/9 Liz :
> I concur
> I found about 350 -400 km of highway uploaded (twice) with points at one per
> second at 100kmh travel speed
> Once uploaded and made into a way, and then the way deleted without removing
> the points, then uploaded again
> and while we have editors that allow that sort
2009/8/9 John Smith :
> --- On Sun, 9/8/09, Stefan de Konink wrote:
>> Already saw an OSM editor supporting realigning Yahoo
>> Imagery based on
>> existing points?
>
> Not automatically, but JOSM can shift the yahoo image to align it to known
> points then you just move nodes/ways as needed.
AF
> Some people mentioned that the default settings of these tools are very
> agressive - this is true and a more lenient approach might produce much
> better results. But then, I have not seen any options to change this (in
> JOSM).
I think you can change the presets in Einstein-mode.
cheers,
Mart
Hi!
Martin Koppenhoefer schrieb:
> I want to point attention to the potlatch-funtion tidy-points (similar
> to JOSM simplify way). I encourage everybody not to use these
> functions (at least not on data someone else entered) as it harms
> severly the data.
First of all, I agree with you that th
--- On Sun, 9/8/09, Stefan de Konink wrote:
> Already saw an OSM editor supporting realigning Yahoo
> Imagery based on
> existing points?
Not automatically, but JOSM can shift the yahoo image to align it to known
points then you just move nodes/ways as needed.
___
On Sun, 9 Aug 2009, John Smith wrote:
> You get 4 or more points on the ground by GPS and you align to that, I
> meant suburb level, not an entire city or states or countries.
Already saw an OSM editor supporting realigning Yahoo Imagery based on
existing points?
Stefan
__
2009/8/9 John Smith :
> Assuming that yahoo is wrong, at least it will be consistently wrong and it's
> trivially to mass move ways when you do get reference points to re-align the
> data to.
no, unfortunately according to my gps-traces and knowledge of the
actual situation in my city, it is som
2009/8/9 Richard Fairhurst :
> As I've said several times to Martin, once I have a spare minute I'll
> add some sort of confirmation dialogue if you try to straighten a
> street with more than n metres divergence. But for now, I'm off on
> holiday.
Actually those confirmation dialogues are a bit
--- On Sun, 9/8/09, Stefan de Konink wrote:
> Moving stuff in GIS is never trivial. You don't know why it
> is wrong, and
> even if it looks 'locally' shifted it could be even
> misrectified causing
> it to be shifted and streched possibly rotated.
You get 4 or more points on the ground by GPS
Am Samstag 08 August 2009 14:42:43 schrieb Martin Koppenhoefer:
> An example from the result of the current tidy-points-function here:
> http://trac.openstreetmap.org/attachment/ticket/2148/090808_potlatch_tidy-p
>oints_.png
>
In this case it looks more like an error of the tidy-function, or at le
On Sun, 9 Aug 2009, Shaun McDonald wrote:
> How does your town compare to Yahoo?
It seems to have an offset in both X and Y. But I can only see that
locally. I don't know if there is a more global problem.
> I have only heard of trival shifts in the rectification being a problem.
I think it cou
On 9 Aug 2009, at 12:10, Stefan de Konink wrote:
> On Sun, 9 Aug 2009, John Smith wrote:
>
>> Assuming that yahoo is wrong, at least it will be consistently wrong
>> and it's trivially to mass move ways when you do get reference
>> points to
>> re-align the data to.
>
> Moving stuff in GIS is n
On Sun, 9 Aug 2009, John Smith wrote:
> Assuming that yahoo is wrong, at least it will be consistently wrong
> and it's trivially to mass move ways when you do get reference points to
> re-align the data to.
Moving stuff in GIS is never trivial. You don't know why it is wrong, and
even if it look
--- On Sun, 9/8/09, Stefan de Konink wrote:
> Most likely this is true because the TIGER dataset was
> actually traced
> from/for a much lower precision map, hence wavy because you
> are plotting
> it on a far higher resolution then it was created for. With
> respect to
> TIGER you might say: TIG
On Sun, Aug 9, 2009 at 11:12 AM, Stefan de Konink wrote:
> On Sun, 9 Aug 2009, Richard Fairhurst wrote:
>
>> Stefan de Konink wrote:
>>
>> > And then you realise that the alignment of Yahoo Imagery is wrong
>> > on most
>> > places, and you have killed good vector material. Great job :)
>>
>> "Good
Tobias Knerr wrote:
> But maybe "in those parts of the world where streets are not perfectly
> straight, it is of no use and even dangerous in the hands of newbies"
> should be extrapolated to "it should not be included by default but
> provided by a plugin/option"?
Hm. I can think of plenty of t
On Sun, 9 Aug 2009, Richard Fairhurst wrote:
> Stefan de Konink wrote:
>
> > And then you realise that the alignment of Yahoo Imagery is wrong
> > on most
> > places, and you have killed good vector material. Great job :)
>
> "Good vector material"? Tell me, have you ever _seen_ TIGER?
Yes, and I
Richard Fairhurst wrote:
> _That_ is why this function is here: to simplify the work of one of the most
> tedious parts of TIGER fixup. As always, "it's of no use for my mapping"
> should not be extrapolated to "it's of no use and should be banned".
But maybe "in those parts of the world where str
Stefan de Konink wrote:
> And then you realise that the alignment of Yahoo Imagery is wrong
> on most
> places, and you have killed good vector material. Great job :)
"Good vector material"? Tell me, have you ever _seen_ TIGER?
Seriously, you're kidding me. Yahoo may be out-of-alignment here a
On Sun, 9 Aug 2009, Richard Fairhurst wrote:
> Turn on the Yahoo imagery, align the start and end points of the way, and
> select the 'Tidy' function. Hey presto, the street is now correctly aligned
> to the grid. You could have done this manually, but it would have taken 10
> times as long and wo
Martin and I have had this conversation on private e-mail too, but one point
bears repeating:
> I know that some people like this tidy-points-function to
> work on TIGER-Data, but I tell you: if the TIGER-Data is
> not good/precise, it won't get better using this function ;-)
That is evidently
>
> I know that some people like this tidy-points-function to work on
> TIGER-Data, but I tell you: if the TIGER-Data is not good/precise, it
> won't get better using this function ;-)
bad data doesn't get worse either. for a lot of tiger data it can compact
without any loss. And tiger is not a c
On Sat, 8 Aug 2009 14:42:43 +0200, Martin Koppenhoefer
wrote:
> Hi all,
>
> I want to point attention to the potlatch-funtion tidy-points (similar
> to JOSM simplify way). I encourage everybody not to use these
> functions (at least not on data someone else entered) as it harms
> severly the data
On Sat, Aug 8, 2009 at 10:42 PM, Martin
Koppenhoefer wrote:
> I'd like to start a discussion about which automated functionalities
> we want to allow
As long as the "automated functionalities" are initiated and
controlled by human judgment, there is no need to limit them.
Hi all,
I want to point attention to the potlatch-funtion tidy-points (similar
to JOSM simplify way). I encourage everybody not to use these
functions (at least not on data someone else entered) as it harms
severly the data. IMHO OSM is a project about drawing a collaborative
map, not about comput
33 matches
Mail list logo
