[OSM-talk] osmeditor2 and JOSM

[Wollschaf]

On Fri, 08 Sep 2006 12:24:39 +0100, Nick Whitelegg wrote:

> - direct communication with GPS, removing the need for GPSBabel.

As this especially targets newer users, direct conversion from trackpoints
to nodes without filtering should be restricted in some way. Otherwise a
good idea, but I would make it a low-priority addition.

> - remove the need for people to know about Map Features, with a
> drop-down selectable list as in osmeditor2.

Very good. Keeps users from entering non-standard tags for features that
already exist. Good for lazy people like me :D

> - an optional display style where ways are rendered in different colours
> according to type, as in the slippy renderer, osmarender, Freemap or
> osmeditor2.

A useful feature. Densely populated areas are currently a bit too
confusing for my taste.

> - show POIs as icons (as per the slippy renderer, osmarender, Freemap,
> osmeditor2)

POIs and city names. At least a different color for POI nodes and a popup
(with optional icon) in standard editing mode, perhaps mouse-over
triggered. I suggest using an icon only in the optional map rendering
mode, at least only display a very small icon in standard editing mode.
 
What if...

> Given the quite large number of users who want to use a 100% Open Source
> environment, it would also be of benefit to make it compatible with GNU
> Classpath or other open source Java VM.

nevermind, now you convinced me :)

That is important to some people, and - I think - the major advantage of
osmeditor2; With JOSM then being OS Java compatible, the question is just
one of preferred toolkit - and that can be put aside.

Although I like working with native (gtk/qt) applications under linux, I
also know that it is better to have one feature-complete editor than two
editors which work well in their certain areas, but lack features.

I can't object to any of the additions you would make in case you decide
to enhance JOSM. I'm really, really looking forward for the new JOSM
generation. :)

Other useful features I can think of at the moment:
- different coloring for segments, ways and nodes that contain useful tags
(not created_by)
- different default color for local GPX data.

happy coding,
Wollschaf