[OSM-dev] Re: Data types; indexes etc.

[.]

> So if it's more efficient, we could create tables of lines as a  
> derivative from the nodes/segments/ways tables, which would be updated  
> only on edit of the source data. Then use these to render the maps. I  
> guess it depends which apps are causing the most load.

speaking of efficiency and load: i often experience delays on editing
maps with the applet, not only at loading tiles but also with gps tracks
and displaying nodes/segments, and somtimes it gets stuck at loading
trace - what kind of hardware is OSM thing running on and where are the
bottlenecks?

is there some kind of fund accepting donations for new hardware (i hope
you're not alredy on the cutting-edge) - i'd like to donate some,
paypal'd be the easiest transfer method

i read somewhere about the rendering prog being unthreaded, is there a
replacement in the works?

is there something ongoing about a new/reworked applet which supports
some new functions like:
- not having to select each segment for a way, where i could just click
start and ending node (i'd like to edit some highways, the longer the
way, the more painful it is)
- on-the-fly segment creation -> creating a node automatically creates a
segment with the last node (would useful for following gps tracks)
- preloading tiles, traces and nodes (allowing faster editig)
- for beginners it'd be good to have some checkboxes with choices for
nodes/segments like "pub","gasstation","post office" -> that'd reduce
the spreading of different-terms-same-meaning; something like the
dropdown menu "class"

maybe it'd be good having a checkbox for the "advanced" features for not
confusing beginners

andreas