1. The first suggestion I have is to output the warning messages in html format so that when the url for a problem is logged, the file can be opened in a browser and just click on the link to problem. I played with this and it seems to work, maybe an extra option could be added to output this format so the default is how it is now? 2. This may be able to be done already but I could not see how, currently I use my own style files to create the output I desire but every time a new feature is added the the default ones I need to get that and add to all my style sets or reapply my changes to the default ones. It would be good to have the ability to create a set of overide style files that only contain things that are to be changed from the default style you are using and some type of marker so some default ones can be deleted. Are they worth me looking at?
Hello Peter & Suzie
1. The first suggestion I have is to output the warning messages in html format so that when the url for a problem is logged, the file can be opened in a browser and just click on the link to problem. I played with this and it seems to work, maybe an extra option could be added to output this format so the default is how it is now?
I don't know what system you are using but on Linux, all I have to to is display the log file in a terminal window (using less) and I can copy URLs straight from the text by putting the cursor over the URL and using the right mouse button to pop up a context menu. No need for a browser.
2. This may be able to be done already but I could not see how, currently I use my own style files to create the output I desire but every time a new feature is added the the default ones I need to get that and add to all my style sets or reapply my changes to the default ones. It would be good to have the ability to create a set of overide style files that only contain things that are to be changed from the default style you are using and some type of marker so some default ones can be deleted.
Are they worth me looking at?
Perhaps, but given that a lot of people use radically different style files from the default, it may not be taken up by the hard-core stylers? Don't know, just guessing. Cheers, Mark
Hi Mark, Windows users don't have the feature. I will see if I get any other feedback on the styles before I attempt it. Peter.. On Wed, Dec 9, 2009 at 8:25 AM, Mark Burton <markb@ordern.com> wrote:
Hello Peter & Suzie
1. The first suggestion I have is to output the warning messages in html format so that when the url for a problem is logged, the file can be opened in a browser and just click on the link to problem. I played with this and it seems to work, maybe an extra option could be added to output this format so the default is how it is now?
I don't know what system you are using but on Linux, all I have to to is display the log file in a terminal window (using less) and I can copy URLs straight from the text by putting the cursor over the URL and using the right mouse button to pop up a context menu. No need for a browser.
2. This may be able to be done already but I could not see how, currently I use my own style files to create the output I desire but every time a new feature is added the the default ones I need to get that and add to all my style sets or reapply my changes to the default ones. It would be good to have the ability to create a set of overide style files that only contain things that are to be changed from the default style you are using and some type of marker so some default ones can be deleted.
Are they worth me looking at?
Perhaps, but given that a lot of people use radically different style files from the default, it may not be taken up by the hard-core stylers? Don't know, just guessing.
Cheers,
Mark _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Mark, On Tue, Dec 08, 2009 at 09:25:17PM +0000, Mark Burton wrote:
Hello Peter & Suzie
2. This may be able to be done already but I could not see how, currently I use my own style files to create the output I desire but every time a new feature is added the the default ones I need to get that and add to all my style sets or reapply my changes to the default ones. It would be good to have the ability to create a set of overide style files that only contain things that are to be changed from the default style you are using and some type of marker so some default ones can be deleted.
Are they worth me looking at?
Perhaps, but given that a lot of people use radically different style files from the default, it may not be taken up by the hard-core stylers? Don't know, just guessing.
I have understood that there is some interest in having multiple styles in the mkgmap repository. See for example the feedback that I got a couple of days ago to my suggestion of translating traffic_calming=* in the default style. An "include file" feature for styles would help achieve having a family of styles. We could distribute a few styles in addition to the current default one, e.g., for pedestrians, pedestrians who want bus route overlays, on-road bicyclists, and motorheads who do not want to see cycleways or footways :-). All styles would be based on a bare-bones "core" default style that would only display major roads, excluding some stuff like traffic_calming=* or highway={bus_stop,service,cycleway,path,footway,steps}. There could be a repository of user-contributed styles that could import definitions from the default styles by reference. How would that sound like? Style files could even take parameters from the command line or args file. You could for example specify --unlit_is_unpaved=true to control a conditional feature like this: lit=no & unlit_is_unpaved=true { set mkgmap:paved=no } Best regards, Marko
Quoting Peter & Suzie <pslowater@gmail.com>:
2. This may be able to be done already but I could not see how, currently I use my own style files to create the output I desire but every time a new feature is added the the default ones I need to get that and add to all my style sets or reapply my changes to the default ones. It would be good to have the ability to create a set of overide style files that only contain things that are to be changed from the default style you are using and some type of marker so some default ones can be deleted.
It's been suggested before that the style files have some sort of #include directive. As an example. We have a style called 'pedestrian'. The style rules file ./pedestrian/points would have a line at the top that said: #include ../default/points This would mean that the file ./pedestrian/points would include all the default points style rules. Below the #include directive in the ./pedestrian/points file would be: a) additional style rules not present in ../default/points b) over-rides (i.e. style rules that match the same OSM objects as ../default/points, but do something different) This would mean you could keep your own styles fully up to date with changes to the default style, and save you re-writing lots of rules that you don't want to change from the default. -- Charlie
participants (4)
-
charlie＠cferrero.net -
Mark Burton -
Marko Mäkelä -
Peter & Suzie