[OSM-talk] Suggestion for JOSM
dieterdreist at gmail.com
Mon Nov 2 14:00:10 GMT 2009
2009/11/2 Ævar Arnfjörð Bjarmason <avarab at gmail.com>
> On Mon, Nov 2, 2009 at 8:12 AM, Richard Fairhurst <richard at systemed.net>
> > I would commend this forced simplification to the JOSM devs. Ways are
> > automatically split after an interval of n seconds.
> Unlike Potlatch JOSM is a powertool. It shouldn't force you to do anything.
wait for potlatch 2.0 ;-)
> Recently I traced a zigzag road in Greece from a GPX track in JOSM by...<http://www.openstreetmap.org/browse/way/40783985/history>
> I tried to simplify the track using the utilsplugin but that made the
> road way more inaccurate than my trace was. What was previously a
> smooth curve around a bend turned into a few crude points that would
> have looked bad on the map.
+1, the main issue is that no piece of software but just you know where
there was a curve, which line was straight and where it was really
ondulated. I personally care about those details, and while I would like to
represent a straight line with just 2 points (and not 3 or 4), I would also
like to have quite a lot of points in curves to represent them well.
> We would do well to remember that not everyone wants to spend an hour
> to perfectly trace some way in the middle of nowhere.
perfectly true for the middle of nowhere but horrible in densly builtup
> importing an almost raw GPX track is quick, good enough and perfectly
> We can always fix the data later.
true, but what I sometimes face is the opposite: traced for some time very
precisely some road/footway till someone thinks: hey, it would be enough to
have this represented by 8 nodes, and applies some algo-magic to it.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the talk