[OSM-talk] Osm2go: mobile mapping with Nokia n800/n810

[Till Harbaum / Lists]

Hi,

Am Montag 17 November 2008 schrieb Andrew Chadwick (email lists):
> There's quite a lot of stylus dragging in osm2go right now, both for
> panning and for moving objects. It's not always that reliable on my
You can already pan using the directop pad (or perhaps this isn't in the
version already published. So at least the next release will allow you 
to pan by the keys).

> the way Maemo-Mapper does it, with a single tap *or* tap+drag. Not sure
> how well that'd work in places with a lot of areas though.
That's the problem. I have plenty of examples where there's always an
area whereever you go ...

> osm2go should have a mode for following the GPS marker when it wanders
> off-screen :) Maybe turned off temporarily while you have something
I am afraid i don't understand what you want.

> At very high zoom levels, POIs can hide very short ways causing them to
> be uneditable. Is it possible to implement a maximum pixel size for POIs
> and Way widths? I can supply an example if you need one.
Hmm, that's difficult as the canvas always handles the items at their given
size. So the road widths and poi diameters just scales with the zoom.

I was already thinking about some global things to change the size of
all objects. The opposite also happens if you are in a very dense populated 
area and everything is just a bunch of thin lines.

> If you're zoomed out beyond the extent of the current project, it's
> impossible to pan the map so that part of it is hidden beyond the canvas
> edge. This might hinder new users because it creates an artificial
??? I don't understand that. There's the area you downloaded. You can 
see only that and work only on that. You can never leave the active area
by panning/scrolling and you can't place anything there.

> distinction between the behaviour when zoomed in (can pan without
> "hitting a wall") and when zoomed out (cannot pan in some or all
> directions). I'd suggest drawing a shaded border of about 64px width
> around the current project, perhaps looking like JOSM's new "display
> boundaries of downloaded data" hatching, and using that as an outer,
> visible handle. So it'd be possible to pan to
That's not how the goocanvas works. You cannot easily make display
data outside the given working area.

> The screen real estate usage is generally very well thought out and
> makes sense to me. It'd be really cool if the dependency on Hildon,
> osso, and various other Maemo-specific parts could be relaxed for users
> of devices like Eee PCs, but I guess that's less of an immediate
> requirement :)
There's no hildon requirement at all. In fact i do 99% of all coding and
testing on the gtk linux desktop. This should run out of the box on
any gtk based machine.

> I wonder if, like gosmore, it would make sense for osm2go to do some
> sort of level-of-detail hiding for lower zoom levels, in order to speed
> up the drawing process. It might make sense to restrict editability only
> to higher zooms too, like potlatch does (IIRC).
Also that's not how the goocanvas works and it's hard to circumvent those
things.

Till