[PATCH] Distinguish stops with lit shelters by *
The attached patch replaces the + in the names of shelter-equipped bus/tram/train stops with * when lit=yes. When travelling by foot or bicycle during dark time of a day, it can be helpful to find the nearest lit shelter for a break. Best regards, Marko
Quoting Marko Mäkelä <marko.makela@iki.fi>:
The attached patch replaces the + in the names of shelter-equipped bus/tram/train stops with * when lit=yes. When travelling by foot or bicycle during dark time of a day, it can be helpful to find the nearest lit shelter for a break.
Best regards,
Marko
Marko (and list), A while back we discussed creating a style repository for mkgmap, where we can put our own individual style files (there must be a fair few between regular users now). Rather than apply your patches to the default style, perhaps we could kick-start the style repository? We could also add a TYP file repository. I've found it inordinately hard to find any sort of systematic directory of TYP files online (and what I have found, tends mostly to be on Czech web-pages, for some reason). -- Charlie
On Thu, Nov 26, 2009 at 11:05:01AM +0000, charlie@cferrero.net wrote:
Quoting Marko Mäkelä <marko.makela@iki.fi>:
The attached patch replaces the + in the names of shelter-equipped bus/tram/train stops with * when lit=yes. When travelling by foot or bicycle during dark time of a day, it can be helpful to find the nearest lit shelter for a break.
Best regards,
Marko
Marko (and list),
A while back we discussed creating a style repository for mkgmap, where we can put our own individual style files (there must be a fair few between regular users now). Rather than apply your patches to the default style, perhaps we could kick-start the style repository?
I think that the default style should still be maintained. There is some value in having sensible defaults. I do see value in other styles and hacks, such as distinguishing different types of paths by drawing multiple lines per way or repurposing taxi/delivery/emergency flags for custom bicycle routing, but I would keep the default style bare-bones. I must say that I have not played with other styles than the default. Is it possible to include the definitions of another style by reference and override them? That would allow improvements in the default style to be automatically applied to other styles. In that way, custom styles would be easier to maintain and understand, as they would not copy large amounts of definitions from other styles. A while back, when I emailed Steve directly to ask him to apply my shelter=yes/no to +/- patch, he asked if I would like to maintain the default style. I said yes, but I guess that Steve has been busy with other things.
We could also add a TYP file repository. I've found it inordinately hard to find any sort of systematic directory of TYP files online (and what I have found, tends mostly to be on Czech web-pages, for some reason).
Agreed. But I think that we should have the files in an editable format (a text file that is converted to binary TYP by a simple program) and the origin and the copyright information of every icon has to be clearly documented. Best regards, Marko
Marko Mäkelä <marko.makela@iki.fi> writes:
I think that the default style should still be maintained. There is some value in having sensible defaults. I do see value in other styles and hacks, such as distinguishing different types of paths by drawing multiple lines per way or repurposing taxi/delivery/emergency flags for custom bicycle routing, but I would keep the default style bare-bones.
Agreed. The default is close to that - what a 'normal' user would want.
I must say that I have not played with other styles than the default. Is it possible to include the definitions of another style by reference and override them? That would allow improvements in the default style to be automatically applied to other styles. In that way, custom styles would be easier to maintain and understand, as they would not copy large amounts of definitions from other styles.
At least mostly, maybe totally. See resources/styles/noname.
Agreed. But I think that we should have the files in an editable format (a text file that is converted to binary TYP by a simple program) and the origin and the copyright information of every icon has to be clearly documented.
There seems to be perl code to run as cgi that does text/typ, so it should be possible to turn this into something that can checked in and part of the build, or of mkgmap. Long term, it would be cool to have a design for a joint style file and TYP file that maps OSM objects to codepoints beyond what base garmin can do and then makes those codepoints show up sensibly with a TYP file. This is currently beyond what I grasp.
I have made custom styles and typ for my OSM Philippine maps and would be happy to share them and learn from others as well. Some shots: http://epsg4253.wordpress.com/2009/09/12/new-osm-ph-garmin-map-release-sept-... http://epsg4253.wordpress.com/2009/11/14/new-osm-ph-garmin-map-release-nov-2... All icons from my minimal.typ are public domain. On Fri, Nov 27, 2009 at 8:17 AM, Greg Troxel <gdt@ir.bbn.com> wrote:
Marko Mäkelä <marko.makela@iki.fi> writes:
I think that the default style should still be maintained. There is some value in having sensible defaults. I do see value in other styles and hacks, such as distinguishing different types of paths by drawing multiple lines per way or repurposing taxi/delivery/emergency flags for custom bicycle routing, but I would keep the default style bare-bones.
Agreed. The default is close to that - what a 'normal' user would want.
I must say that I have not played with other styles than the default. Is it possible to include the definitions of another style by reference and override them? That would allow improvements in the default style to be automatically applied to other styles. In that way, custom styles would be easier to maintain and understand, as they would not copy large amounts of definitions from other styles.
At least mostly, maybe totally. See resources/styles/noname.
Agreed. But I think that we should have the files in an editable format (a text file that is converted to binary TYP by a simple program) and the origin and the copyright information of every icon has to be clearly documented.
There seems to be perl code to run as cgi that does text/typ, so it should be possible to turn this into something that can checked in and part of the build, or of mkgmap.
Long term, it would be cool to have a design for a joint style file and TYP file that maps OSM objects to codepoints beyond what base garmin can do and then makes those codepoints show up sensibly with a TYP file. This is currently beyond what I grasp.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------
maning sambale wrote:
I have made custom styles and typ for my OSM Philippine maps and would be happy to share them and learn from others as well.
Some shots:
http://epsg4253.wordpress.com/2009/09/12/new-osm-ph-garmin-map-release-sept-... http://epsg4253.wordpress.com/2009/11/14/new-osm-ph-garmin-map-release-nov-2...
All icons from my minimal.typ are public domain.
Anyone who's interested can download my TYP file and custom style files from: http://www.cferrero.net/maps/map_downloads.html
participants (5)
-
Charlie Ferrero -
charlie＠cferrero.net
-
Greg Troxel -
maning sambale -
Marko Mäkelä