[ gpsdrive ] External program interfacing with gpsdrive

[Guenther Meyer]

Am Montag 25 August 2008 schrieb stan:
> I found out the hard way that the osm2pgsql app wont tolerate any
> interfering with it's tables. So far I'm using a separate set of tables in
> the same database for the routing and osm2pgsql is happy with that. The
> trouble at the mo is the different data formats, it's tricky to join
> something from the mapnik tables with something from the routing tables but
> I'm slowly getting these kind of issues ironed out. It's almost certain the
> osm data will be duplicated in the 2 sets of tables, changing the layout
> too much would break the functions of one or the other, but duplication can
> be kept to a minimum once the tables are speaking the same language and
> adding a text search index will be fairly simple after that.
> The question of adding extra columns for different transport types or using
> the same data with different functions makes a big difference, I'm going
> with extra columns for now as the extra functions would make it very slow
> for older systems and almost unusable on embedded systems.
we should keep duplication as small as possible (my mapnik database containing 
europe uses almost 2GB...), but performance is also an issue, right.
I don't know postgis very well, but maybe we can gain some with good indexing?

how flexible is this system in using one or the other method?
because I think most people won't need all possible transport types, 
especially if they have limited resources on their devices.

> What are the 
> plans for gpsdrive with floating point operations and similar at the
> moment? cheers
>
floating point operations? plans?



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.gpsdrivers.org/pipermail/gpsdrive/attachments/20080825/d2b308ba/attachment.bin>