geoinfo.db

[Andreas Putzo-3]

Hello,

i tried to install gpsdrive 2.10pre7 from source and stumbled about
the missing geoinfo.db. I figured out that it is either available in the
minimal-icons.tgz from sourceforge or in Joergs openstreetmap-map-icons
package.
How is this file generated? Is there a script available to generate
the file from an existing icon directory?
Reading the database schema i guess the file is used to display OSM
waypoints with gpsdrive (mapnik). Is this correct? Does that file have
any other purpose within gpsdrive?

Regards,
Andreas

_______________________________________________
GPSdrive mailing list
GPSdrive@...
http://lists.gpsdrivers.org/mailman/listinfo/gpsdrive

[Guenther Meyer]

Am Samstag 27 Juni 2009 schrieb Andreas Putzo:
> Hello,
>
> i tried to install gpsdrive 2.10pre7 from source and stumbled about
> the missing geoinfo.db. I figured out that it is either available in the
> minimal-icons.tgz from sourceforge or in Joergs openstreetmap-map-icons
> package.
right, it has been moved into those packages.

> How is this file generated? Is there a script available to generate
> the file from an existing icon directory?
the file is generated with create_geoinfo-db.pl
you can find it in the openstreetmap svn in applications/share/map-
icons/tools/

> Reading the database schema i guess the file is used to display OSM
> waypoints with gpsdrive (mapnik). Is this correct? Does that file have
> any other purpose within gpsdrive?
>
it holds all the poi-type data used for displaying all the points and icons in
gpsdrive. there is also a table, that matches the osm-types with the gpsdrive-
types when importing poi-data from an osm xml-file.
it has nothing to do with mapnik.




_______________________________________________
GPSdrive mailing list
GPSdrive@...
http://lists.gpsdrivers.org/mailman/listinfo/gpsdrive

[Andreas Putzo-3]

On Jun 28  19:31, Guenther Meyer wrote:

> Am Samstag 27 Juni 2009 schrieb Andreas Putzo:
> > i tried to install gpsdrive 2.10pre7 from source and stumbled about
> > the missing geoinfo.db. I figured out that it is either available in the
> > minimal-icons.tgz from sourceforge or in Joergs openstreetmap-map-icons
> > package.
> right, it has been moved into those packages.
>
> > How is this file generated? Is there a script available to generate
> > the file from an existing icon directory?
> the file is generated with create_geoinfo-db.pl
> you can find it in the openstreetmap svn in applications/share/map-
> icons/tools/
>
> > Reading the database schema i guess the file is used to display OSM
> > waypoints with gpsdrive (mapnik). Is this correct? Does that file have
> > any other purpose within gpsdrive?
> >
> it holds all the poi-type data used for displaying all the points and icons in
> gpsdrive. there is also a table, that matches the osm-types with the gpsdrive-
> types when importing poi-data from an osm xml-file.
> it has nothing to do with mapnik.

Thanks for the explanation. That made things clear :)

May i suggest putting the script into the gpsdrive repository? Judging
from the comments in the script, geoinfo.db is solely used by gpsdrive
and thus, in my opinion, should be kept there.
That way, cmake could add the map-icons as a "build-dependency" and
create the geoinfo.db at build time.
I think that would be a much cleaner solution and, by theory, you are
not bound to a particular icon set, but people are allowed to provide
their own.
Another advantage might be, that gpsdrive wouldn't complain about the
missing geoinfo.db after installation but show a meaningful error
message at build time that a dependency is missing.
If you don't oppose my idea i would try to prepare a patch to implement
this.


Andreas



_______________________________________________
GPSdrive mailing list
GPSdrive@...
http://lists.gpsdrivers.org/mailman/listinfo/gpsdrive

[Guenther Meyer]

Am Sonntag 28 Juni 2009 schrieb Andreas Putzo:
> May i suggest putting the script into the gpsdrive repository? Judging
> from the comments in the script, geoinfo.db is solely used by gpsdrive
> and thus, in my opinion, should be kept there.
it was in the gpsdrive repository some time ago.
the geoinfo stuff was developed for gpsdrive, but we thought, it would be a
good idea to put it (together with the icons) into the osm repository, in the
hope, that other applications might use it, too.

as this may be a good idea for achieving this, I never liked Joerg's decision
to move the geoinfo.db (which is an essential part of gpsdrive) oout to a
separate package...

> That way, cmake could add the map-icons as a "build-dependency" and
> create the geoinfo.db at build time.
this would be a good idea, but the geoinfo db doesn't change that much, that
we need to rebuild it every time...
it also needs the icons.xml file as source; but that one also belongs to the
icons...

we had a svn link to the osm repository some time ago; I don't know if this is
still present...

> I think that would be a much cleaner solution and, by theory, you are
> not bound to a particular icon set, but people are allowed to provide
> their own.
people aren't bound to some specific icon sets; although there are some
requirements, they have to meet...

> Another advantage might be, that gpsdrive wouldn't complain about the
> missing geoinfo.db after installation but show a meaningful error
> message at build time that a dependency is missing.
> If you don't oppose my idea i would try to prepare a patch to implement
> this.
>
hmm...
IMO the best would be, to create a package from the minimal-icons.tgz, and use
it as a required dependency to gpsdrive. this package could also be built
together with gpsdrive...



_______________________________________________
GPSdrive mailing list
GPSdrive@...
http://lists.gpsdrivers.org/mailman/listinfo/gpsdrive

[Joerg Ostertag (Tettnang)]

On Monday 29 June 2009 01:19:54 Guenther Meyer wrote:

> Am Sonntag 28 Juni 2009 schrieb Andreas Putzo:
> > May i suggest putting the script into the gpsdrive repository? Judging
> > from the comments in the script, geoinfo.db is solely used by gpsdrive
> > and thus, in my opinion, should be kept there.
>
> it was in the gpsdrive repository some time ago.
> the geoinfo stuff was developed for gpsdrive, but we thought, it would be a
> good idea to put it (together with the icons) into the osm repository, in
> the hope, that other applications might use it, too.
>
> as this may be a good idea for achieving this, I never liked Joerg's
> decision to move the geoinfo.db (which is an essential part of gpsdrive)
> oout to a separate package...

The reason here is consistency. Since geoinfo.db is directly depending on the
existance or non existence of icons, i decided to move it to where the icons
are located. Only this way i can be sure that after installing a
map-icons-package Version xy i also have the corresponding geoinfo.db version
xy file laying near it. und thus being installed at the same time.

> > Another advantage might be, that gpsdrive wouldn't complain about the
> > missing geoinfo.db after installation but show a meaningful error
> > message at build time that a dependency is missing.
> > If you don't oppose my idea i would try to prepare a patch to implement
> > this.
> >
> hmm...
> IMO the best would be, to create a package from the minimal-icons.tgz, and
> use  
> it as a required dependency to gpsdrive. this package could also be built
> together with gpsdrive...

As Günther already entioned, I could think of one way arround it. We might
want to add a small dummy geoinfo.db with only the 10 top-level entries
included. But then we still have the problem that this is inconsistent as
soon as one new top-level icon-tree is added or removed.

-
Joerg

_______________________________________________
GPSdrive mailing list
GPSdrive@...
http://lists.gpsdrivers.org/mailman/listinfo/gpsdrive

[Andreas Putzo-3]

On Jun 30  22:05, Joerg Ostertag wrote:
> On Monday 29 June 2009 01:19:54 Guenther Meyer wrote:
> > Am Sonntag 28 Juni 2009 schrieb Andreas Putzo:
> > > May i suggest putting the script into the gpsdrive repository? Judging
> > > from the comments in the script, geoinfo.db is solely used by gpsdrive
> > > and thus, in my opinion, should be kept there.
> >
> > it was in the gpsdrive repository some time ago.

Somehow skipped that part in your first mail.

> > the geoinfo stuff was developed for gpsdrive, but we thought, it would be a
> > good idea to put it (together with the icons) into the osm repository, in
> > the hope, that other applications might use it, too.
> >
> > as this may be a good idea for achieving this, I never liked Joerg's
> > decision to move the geoinfo.db (which is an essential part of gpsdrive)
> > oout to a separate package...

If this file is useful for other applications it might be ok. You don't
add all libraries gpsdrive depends on into the gpsdrive source just
because gpsdrive won't run without it. Though the build system should
catch it, if it can't find the geoinfo.db.
>
> The reason here is consistency. Since geoinfo.db is directly depending on the
> existance or non existence of icons, i decided to move it to where the icons
> are located. Only this way i can be sure that after installing a
> map-icons-package Version xy i also have the corresponding geoinfo.db version
> xy file laying near it. und thus being installed at the same time.

What happens if the geoinfo.db contains a poi_type but the installed
icon set does not contain that particular icon? There are more than 500
poi_types already which is many for a minimal icon set for embedded devices.
Also, you would need something like a map-icons-common package since you
can't just add the geoinfo.db to every map-icons package without adding
conflicts. I don't really like the idea to add a package for only two
files (icons.xml and geoinfo.db), but well..


Andreas
_______________________________________________
GPSdrive mailing list
GPSdrive@...
http://lists.gpsdrivers.org/mailman/listinfo/gpsdrive

[Guenther Meyer]

Am Donnerstag 02 Juli 2009 schrieb Andreas Putzo:

> On Jun 30  22:05, Joerg Ostertag wrote:
> > On Monday 29 June 2009 01:19:54 Guenther Meyer wrote:
> > > Am Sonntag 28 Juni 2009 schrieb Andreas Putzo:
> > > > May i suggest putting the script into the gpsdrive repository?
> > > > Judging from the comments in the script, geoinfo.db is solely used by
> > > > gpsdrive and thus, in my opinion, should be kept there.
> > >
> > > it was in the gpsdrive repository some time ago.
>
> Somehow skipped that part in your first mail.
>
> > > the geoinfo stuff was developed for gpsdrive, but we thought, it would
> > > be a good idea to put it (together with the icons) into the osm
> > > repository, in the hope, that other applications might use it, too.
> > >
> > > as this may be a good idea for achieving this, I never liked Joerg's
> > > decision to move the geoinfo.db (which is an essential part of
> > > gpsdrive) oout to a separate package...
>
> If this file is useful for other applications it might be ok. You don't
> add all libraries gpsdrive depends on into the gpsdrive source just
> because gpsdrive won't run without it. Though the build system should
> catch it, if it can't find the geoinfo.db.
>
> > The reason here is consistency. Since geoinfo.db is directly depending on
> > the existance or non existence of icons, i decided to move it to where
> > the icons are located. Only this way i can be sure that after installing
> > a map-icons-package Version xy i also have the corresponding geoinfo.db
> > version xy file laying near it. und thus being installed at the same
> > time.
>
> What happens if the geoinfo.db contains a poi_type but the installed
> icon set does not contain that particular icon? There are more than 500
> poi_types already which is many for a minimal icon set for embedded
> devices.

this is one of the advantages of our tree-bases approach:

if an icon is missing, or there is a new poi_type which hasn't yet an icon,
the parent icon is used.

> Also, you would need something like a map-icons-common package
> since you can't just add the geoinfo.db to every map-icons package without
> adding conflicts. I don't really like the idea to add a package for only
> two files (icons.xml and geoinfo.db), but well..
>
that's why I recommend to create a package from my minimal-icons.tgz with no
other dependencies.
it should contain only the base icons and the geoinfo.db.
I don't know if it is possible for other (full) icons packages to depend on
that, because they would probably have to overwrite the provided base icons.





_______________________________________________
GPSdrive mailing list
GPSdrive@...
http://lists.gpsdrivers.org/mailman/listinfo/gpsdrive

[hamish_b]

for my 2c, I would vote for the base .tgz package to be self-complete.

i.e. a truly minimal symbol set of simple +,x,.,o,*,box,diamond rendered
as vector graphics, not raster. (eg WLAN symbol et al from 2.09's way.txt)
and a simple (empty?) geoinfo.db to match that.

it is not unexpected to ask users to install widely available libgtk2
and zlib, and have cmake complain if they are not there, but requiring a
second .tgz for geoinfo.db seems a bit of an unexpected imposition,
especially when those not using OSM will use none of those icons.
(probably gpsd is a better example of a distinct run-time dep)


I have no problem with small dependent .deb's, that is another matter.
(e.g. no one complains about friendsd.deb)  Just the omnibus.tgz.


also IHMO POI icons should be SVG not rasterized, but I would let the
OSM and Mapnik projects worry about that :)


regards,
Hamish



     

_______________________________________________
GPSdrive mailing list
GPSdrive@...
http://lists.gpsdrivers.org/mailman/listinfo/gpsdrive

[hamish_b]

Hamish wrote:
> for my 2c, I would vote for the base .tgz package to be self-complete.

ie if geoinfo.db is not found, disable POI and continue instead of exiting
with an error. and/or maybe a compile time flag to create a dummy file?

then you could have icons-minimal.deb and icons-full.deb packages conflict
with each other to avoid overlaps, and not conflict with the base package.


?

Hamish



     

_______________________________________________
GPSdrive mailing list
GPSdrive@...
http://lists.gpsdrivers.org/mailman/listinfo/gpsdrive

[Guenther Meyer]

Am Donnerstag 02 Juli 2009 schrieb Hamish:
> for my 2c, I would vote for the base .tgz package to be self-complete.
>
> i.e. a truly minimal symbol set of simple +,x,.,o,*,box,diamond rendered
> as vector graphics, not raster. (eg WLAN symbol et al from 2.09's way.txt)
> and a simple (empty?) geoinfo.db to match that.
>
having only a minimal set of icons is fine.
but I would always provide the full version of geoinfo.db, otherwise we will
have several different versions flying around which will just cause confusion.
as I already mentioned, it's no problem for gpsdrive if icons are referenced,
that are no there...

> it is not unexpected to ask users to install widely available libgtk2
> and zlib, and have cmake complain if they are not there, but requiring a
> second .tgz for geoinfo.db seems a bit of an unexpected imposition,
> especially when those not using OSM will use none of those icons.
> (probably gpsd is a better example of a distinct run-time dep)
>
Although we tried to match the types to osm to use osm poi-data inside
gpsdrive, it's not the only purpose.
gpsdrive always had POIs (or waypoints) displayed with icons, you can use them
without having any kind of osm data on your system.
geoinfo.db is a part of gpsdrive, it's no "osm import".

> I have no problem with small dependent .deb's, that is another matter.
> (e.g. no one complains about friendsd.deb)  Just the omnibus.tgz.
>
friendsd is not a dependency, gpsdrive runs fine without it.

> also IHMO POI icons should be SVG not rasterized, but I would let the
> OSM and Mapnik projects worry about that :)
>
afaik all the icons in gpsdrive have always been raster images. they were
easier to handle, too. but I agree, that svg icons would be better.
most of the icons have their origin in gpsdrive; we provided them to osm to
use them. and nice to see, that people do it...







_______________________________________________
GPSdrive mailing list
GPSdrive@...
http://lists.gpsdrivers.org/mailman/listinfo/gpsdrive