[OSM-talk] using JOSM in Los Angeles

[Blars Blarson]

After never getting osmeditor2 to do much other than segfault, I set
up a dedicated system to run JOSM.  (I don't run untrusted non-free
software on any of my real systems.)  (The osmeditor2 version was from
a few months ago, after ignoring the documentation and opening a gpx
file it showed some dots.  It segfaulted doing pretty much anything
else.)

JOSM is mostly working, if not quite the way I expected after reading
the documentation.  Unfortunatly, I uploaded some incorrect things
while experimenting and the delete feature doesn't work.


Some feature requests (or questions on how to do it) for JOSM:

	Deleting
	
	Making trackpoints bigger so they can be seen

	Making track lines a different color than trackpoints

	Getting information on trackpoints

	Removing obviously bogus tracklines.  GPS either lost fix or
was turned off.

	Some way to select a segment that can't be bound by a
rectangle that does not contain other segments without selecting the
other segments.

	Getting rid of sets of trackpoins without having to exit/reenter.




Comments/questions on editing conventions:

	I'm doing a single way for freeways, labling it
highway=motorway.  At this point, I think it's better to spend time
getting major features in rather than getting a few things perfect.

	Naming: I'm naming things like I5, CA2 etc.

	The wiki said not to use abbreviations, but almost all entered
data does.  I think the wiki should be fixed to match the data, and a
set of standard abbreviations set or addopted.

	What is primary, secondary etc.  Is it determined by width,
speed limit, traffic patterns, abbutters?

	How should dual signed freeways be handled?  (Example: I5 and
I10 merge together for a mile)

	How about alternate names: portions of CA2 is the "Glendale
Freeway".  Some names don't follow the numbers: "Hollywood Freeway" is
CA170 and portions of US101

	((far?) future) How should HOV (aka carpool) lanes be handled?
	



The editing applet kinda works, but is unusable due to slow responce.
(Do an action, wait a minute to see if the display starts updating,
wait 5-10 more to get the display completely updated.)

-- 
Blars Blarson			blarson at blars.org
				http://www.blars.org/blars.html
With Microsoft, failure is not an option.  It is a standard feature.