[OSM-talk] JOSM feature requests

[Joerg Ostertag (OSM Munich/Germany)]

On Saturday 05 August 2006 03:37, Andrew Loughhead wrote:
> Thanks for your thoughtful reply Joerg.
>
> Joerg Ostertag (OSM Munich/Germany) wrote:
> > On Thursday 03 August 2006 14:29, Andrew Loughhead wrote:
> >> I hope I am not missing a feature that already exists in JOSM. What
> >> I would really like to see is the ability to select, say by drawing
> >> a polygon, a sequence of trackpoints from a local gpx file, and a
> >> button to turn that set into a segment.
> >
> > I personally think that directly converting tracks into osm-segments
> > without filtering is a really bad idea.
>
> I think we are in violent agreement here :-). I was trying to say that
> making effective filtering easily available will let users be more
> consistent, and there are the other data quality benefits too. I was
> just suggesting a way of allowing selective use and filtering of tracks,
> and you have described an another way which exists right now.

Imi and I already started to combine the two programs(josm and osm-filter). 
The idea is to let josm talk to osm-filter with a pipe and let osm-filter do 
the work and josm display the tracks. 

> I have tried osm-filter.pl. I can't get osm.txt right now, so I can't

Well, the file is: ~/.gpsdrive/way.txt

> use --filter-all, as it fails on finding the osm.txt file.  But if I

I just added this passage to the osm-filter help:
 The file osm.txt is the segments file used by osm-pdf-atlas.
 It's containing all osm-segments from planet.osm in a rather simple way.
 The probably easiest way to create it is to go to the 
 directory
    svn.openstreetmap.org/utils/osm-pdf-atlas
 and once call "create.sh".

I thought about downloading and creating this automagically inside the 
osm-filer, but my question about a default place for planet.osm and osm.txt 
was not really answered, but more flamed. So I decided to drop that. It works 
here and I can work on this as soon as we have an conses on this.

The valid locations for osm.txt are(see source for now):
	./
	~/openstreetmap.org/svn.openstreetmap.org/utils/osm-pdf-atlas/Data/
	~/svn.openstreetmap.org/utils/osm-pdf-atlas/Data/
	~/.gpsdrive/MIRROR/osm/

> manually use --split-tracks --filter_duplicate_tracepoints
> --draw_filter_areas, it runs.  It cleans out some garbage from lost
> signal and initial lock very nicely.  

I like this; it's positive feedback ;-)

> It doesn't seem to be removing 
> nodes along straight tracks though.  

I limited the length of the resulting segments to .5 Km
Source:
    if ( $dist_0_2 > .5 ) { # max .5 km distanz
The Idea behind it is to have a decent length of segments. Maybe we can change 
this to 1 Km, but i wouldn't increase too much. 

> I have read through the script and 
> it looks like you are using 0.001 degrees to approximate 1 meter?  

For now the distance calculation held pretty pretty simple. This way it also 
get pretty inaccurate if you're going to the poles. This needs to be changed 
later. 

> I am 
> reasonably sure that some of my points would be within 1 meter of a
> straight line - I will try to check more carefully.

Maybe it's the angle of the track which differs more than 30 degrees?

> On the osm part of the filter: is osm.txt the same as planet.osm? Can I
> just use JOSM to save OSM data for my area of interest, and call that
> osm.txt?

Well almost. you have to filter it first with something like
    perl planet_osm2txt.pl "$planet_dir/$planet_file"
I think i'll add a filter similar to this into osm-filter some time.

> I will try to get gpsdrive up (good that the FC5 issues have just been
> sorted!), to try out the deny and allow area feature of osm-filter.

Just give me feedback on this as soon as you have some experience with it.


-- 
Jörg (Germany, Munich)

http://www.ostertag.name/
TeamSpeak2: ts2.ostertag.name, user: tweety, Channel: "GPS Drive"
irc://irc.oftc.net/#osm