[Openstreetmap] major db refactoring and GPS data

[Thomas Walraet]

Someone (you ?) told a few day ago that it was not easy to show tracks 
(instead of just dots) on the applet with the current db diagram.

Maybe you could add a field to store the preceding GPS point uid in the 
database... (or the following one, but if you process GPS files from 
start to end it seem easier to remember and store the last inserted point)

Having lines between GPS dots would be a major improvement for people 
who cannot set their GPS to drop points every 2 seconds, 5 meters or so. 
(My Forerunner only drop trackpoint on curve)


SteveC a écrit :
> Hello,
> 
> I'm refactoring the database which will require some downtime perhaps
> tomorrow night again. This is in preperation for getting streets, areas
> and curved street segments done. As well as for a move to postgres at
> some point.
> 
> I'm removing all the dead tables, renaming tables and columns to
> sensible names and changing all the timestamp like fields from using
> unix time to SQL datetime fields.
> 
> This is quite a chunk of work, with changes all over the place in the
> codebase.
> 
> I've noticed in the gps data table we have fields for:
> 
> * horizontal dilution
> * vertical dilution
> * number of visible satellites
> * quality
> 
> And none of them are used. Indeed, it's hard to find retail GPS
> receivers that even give that data in their output through gpsbabel.
> Granted you can get these things out of a USB GPS etc.
> 
> So given we have 14 or 15 million rows with 4 unused columns and I don't
> recall anyone really wanting that data parsed and stored... should we
> keep it?
> 
> have fun,