Re: [mkgmap-dev] osmc:symbol
Hi Is there a way using mkgmap to directly show the osmc:symbol in basecamp & on the garmin. I am able to show the contents of the osmc:symbol in basecamp and on the garmin but I want to generate the osmc:symbol itself and have it disploay without having to create a complete set of custom icons in the typ file.. Any thoughts? Thanks. Bill
Garmin's img format (unfortunately) only caters for highway shields. You would therefore be asking mkgmap to generate a TYP file for any osmc symbols it encounters. In theory, this should not be a problem but you would still have to merge it with your own TYP file and deal with any conflict of type numbers - again, this could be possible. I've had to create a style file which caters for most eventualities , both in POIs and Lines. You could reduce the number of pois by using a layering system with pois plotted on top of each other using transparency. Interestingly, Waymarked Trail Hiking <http://hiking.waymarkedtrails.org/help/rendering/osmc> has had to make some compromises when generating its symbols. -- View this message in context: http://gis.19327.n5.nabble.com/Re-osmc-symbol-tp5875693p5875717.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Thanks for the feedback. I was not sure if it was even possible or if I was just missing something. I have not learned about the layering system yet. Any suggestions as to where I might do some reading? Thanks Bill. On 6/17/2016 2:26 AM, nwillink wrote:
Garmin's img format (unfortunately) only caters for highway shields.
You would therefore be asking mkgmap to generate a TYP file for any osmc symbols it encounters.
In theory, this should not be a problem but you would still have to merge it with your own TYP file and deal with any conflict of type numbers - again, this could be possible.
I've had to create a style file which caters for most eventualities , both in POIs and Lines.
You could reduce the number of pois by using a layering system with pois plotted on top of each other using transparency.
Interestingly, Waymarked Trail Hiking <http://hiking.waymarkedtrails.org/help/rendering/osmc> has had to make some compromises when generating its symbols.
-- View this message in context: http://gis.19327.n5.nabble.com/Re-osmc-symbol-tp5875693p5875717.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I'm not aware of any documentation about layering POIs but perhaps consider these points a) TYP files can not define a POIs draworder, unlike polygons. b) There is no guaranteed way of ensuring POI1 always has a higher order than POI2 - this depends on your Garmin device However, there is still room for experimentation: osmc symbols define a foreground and background, ie background: blue foreground: yellow diamond For the level approach to work the background can't be solid but only a frame with a transparent centre and all foreground symbols need to fit inside the frame and have the same dimensions as a background poi # catch all osmc:symbols and split them into background and foregrounds #plot backgrounds first background=blue {0 x 1200a resolution 24 continue) # must use continue #plot foregrounds last foreground= yellow_diamond [0 x 1201a resolution 24) etc The level approach is probably best suited for spurious symbols like arches,wheels or hikers -- View this message in context: http://gis.19327.n5.nabble.com/Re-osmc-symbol-tp5875693p5875742.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Thanks. Interesting approach. I will experiment and see what happens. On 6/17/2016 11:38 AM, nwillink wrote:
I'm not aware of any documentation about layering POIs but perhaps consider these points
a) TYP files can not define a POIs draworder, unlike polygons.
b) There is no guaranteed way of ensuring POI1 always has a higher order than POI2 - this depends on your Garmin device
However, there is still room for experimentation:
osmc symbols define a foreground and background, ie
background: blue
foreground: yellow diamond
For the level approach to work the background can't be solid but only a frame with a transparent centre and
all foreground symbols need to fit inside the frame and have the same dimensions as a background poi
# catch all osmc:symbols and split them into background and foregrounds
#plot backgrounds first
background=blue {0 x 1200a resolution 24 continue) # must use continue
#plot foregrounds last
foreground= yellow_diamond [0 x 1201a resolution 24)
etc
The level approach is probably best suited for spurious symbols like arches,wheels or hikers
-- View this message in context: http://gis.19327.n5.nabble.com/Re-osmc-symbol-tp5875693p5875742.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (2)
-
987654321＠use.startmail.com -
nwillink