Re: [mkgmap-dev] New branch for default typ file
Ticker Berkin writes: (I'm a long-term mkgamp user, sometimes contributor, mostly lurking lately.) > I don't think having: > > BRANCH: default-typ > > makes sense because I don't think there will ever be a single, ideal > file. So better to accept now that it will be a collection of files, > and, as nothing exists at the moment, they might as well go in 'trunk'. As I see it, branches are useful for protecting trunk from changes that are in-progress or controversial. Adding some typ sources doesn't seem to rise to that. But if so, then surely we'd have a branch until it's reviewed, and then merge it and delete the branch. I'm unclear on if that's the choice, or if there is some other suggestion that I don't understand. > I don't know what the best visual effect should be either, but, having > tried a complex example I found somewhere, the raw Garmin device > rendering (with just a _drawOrder section in the TYP file) looked much, > much better. Having a bunch of examples sounds good. I would like to head to a default typ file that is integrated with the default style, so that rendering is more or less aligned with mapnik, but perhaps a bit more detailed at high zoom. I used to use cferrero's style/typ and really liked it, but with mkgmap improvements over the years it was no longer usable without more clue than I had. The big thing over no-typ was showing traffic lights. Semi-related, I am carrying a diff to render "boundary=parcel"; I include state parcel boundary data with osm data in splitter. I have no idea how many others want this, but given that parcel data is not in OSM, merging while mapbuilding (or a separate transparent parcel map) seems pretty useful. What I'm doing is not really ok, but I'm just mentioning the concept. # 0x23 is depth countour - thin. Wacky but useful. 0x1c is too heavy boundary=parcel [0x23 resolution 20] ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] New branch for default typ file
Hi Gerd I don't think having: BRANCH: default-typ makes sense because I don't think there will ever be a single, ideal file. So better to accept now that it will be a collection of files, and, as nothing exists at the moment, they might as well go in 'trunk'. In trunk, they will be visible sooner to all mkgmap users. Then any in the dist/examples/typ-files directory could be selected to be used as -is or a starting point for modification. I don't know what the best visual effect should be either, but, having tried a complex example I found somewhere, the raw Garmin device rendering (with just a _drawOrder section in the TYP file) looked much, much better. I'm hoping others will submit examples, then we just need some reference in the documentation to point people to the examples, along with good comments in the files themselves. Ticker On Tue, 2018-11-27 at 10:59 +, Gerd Petermann wrote: > Hi Ticker, > > well, we have it because I wrote that I'd like to have a typ file for > the default style. My problem is that I cannot help with that because > I feel helpless when it comes to questions reg. "what looks better?" > or "what should be rendered and how?" > Do you think we need another branch or do you think that the exising > one makes no sense? > > Gerd > > > Von: Ticker Berkin > Gesendet: Dienstag, 27. November 2018 11:37 > An: Gerd Petermann; Development list for mkgmap > Betreff: Re: AW: [mkgmap-dev] New branch for default typ file > > Hi Gerd > > Is it worth having a branch for typ-files development? > > Ticker > > > On Tue, 2018-11-27 at 09:25 +, Gerd Petermann wrote: > > Hi Ticker, > > > > okay, see > > http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=425 > > 8 > > > > Gerd > > > > > > Von: mkgmap-dev im Auftrag > > von Ticker Berkin > > Gesendet: Dienstag, 27. November 2018 09:56 > > An: Development list for mkgmap > > Betreff: Re: [mkgmap-dev] New branch for default typ file > > > > Hi Gerd > > > > Happy with either, but slightly prefer typ-files. > > > > I don't think it's worth me doing another patch, it was really just > > a > > 1 > > line change to build.xml and inserting the attached file > > > > Ticker > > > > > > On Tue, 2018-11-27 at 06:27 +, Gerd Petermann wrote: > > > Hi Ticker, > > > > > > I don't like the directory name TYPs. One reason is that the > > > directory doesn't contain *.TYP files, the other is that one > > > might > > > want to write TYPes instead. > > > I'd prefer typ-files or maybe typ-sources. > > > > > > Gerd > > > > > > > > > Von: mkgmap-dev im > > > Auftrag > > > von Ticker Berkin > > > Gesendet: Montag, 19. November 2018 13:07 > > > An: Development list for mkgmap > > > Betreff: Re: [mkgmap-dev] New branch for default typ file > > > > > > Hi > > > > > > I suspect there will be a few TYP files for different usages. > > > > > > I propose that they should be handled like the styles, where they > > > are > > > gathered in a directory resources/TYPs and the build process > > > copies > > > then to dist/examples/TYPs > > > > > > I don't think a new branch is necessary, as there is nothing in > > > the > > > system at the moment. > > > > > > I'd like to submit my most basic TYPfile and attach the file and > > > patch. > > > This, along with option --order-by-decreasing-area, has been > > > adequate > > > for me for a few years (but I have problems with my new Etrex 30x > > > not > > > showing some line types) > > > > > > Ticker > > > ___ > > > mkgmap-dev mailing list > > > mkgmap-dev@lists.mkgmap.org.uk > > > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > ___ > > mkgmap-dev mailing list > > mkgmap-dev@lists.mkgmap.org.uk > > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] New branch for default typ file
Hi Ticker, well, we have it because I wrote that I'd like to have a typ file for the default style. My problem is that I cannot help with that because I feel helpless when it comes to questions reg. "what looks better?" or "what should be rendered and how?" Do you think we need another branch or do you think that the exising one makes no sense? Gerd Von: Ticker Berkin Gesendet: Dienstag, 27. November 2018 11:37 An: Gerd Petermann; Development list for mkgmap Betreff: Re: AW: [mkgmap-dev] New branch for default typ file Hi Gerd Is it worth having a branch for typ-files development? Ticker On Tue, 2018-11-27 at 09:25 +, Gerd Petermann wrote: > Hi Ticker, > > okay, see > http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4258 > > Gerd > > > Von: mkgmap-dev im Auftrag > von Ticker Berkin > Gesendet: Dienstag, 27. November 2018 09:56 > An: Development list for mkgmap > Betreff: Re: [mkgmap-dev] New branch for default typ file > > Hi Gerd > > Happy with either, but slightly prefer typ-files. > > I don't think it's worth me doing another patch, it was really just a > 1 > line change to build.xml and inserting the attached file > > Ticker > > > On Tue, 2018-11-27 at 06:27 +, Gerd Petermann wrote: > > Hi Ticker, > > > > I don't like the directory name TYPs. One reason is that the > > directory doesn't contain *.TYP files, the other is that one might > > want to write TYPes instead. > > I'd prefer typ-files or maybe typ-sources. > > > > Gerd > > > > > > Von: mkgmap-dev im Auftrag > > von Ticker Berkin > > Gesendet: Montag, 19. November 2018 13:07 > > An: Development list for mkgmap > > Betreff: Re: [mkgmap-dev] New branch for default typ file > > > > Hi > > > > I suspect there will be a few TYP files for different usages. > > > > I propose that they should be handled like the styles, where they > > are > > gathered in a directory resources/TYPs and the build process copies > > then to dist/examples/TYPs > > > > I don't think a new branch is necessary, as there is nothing in the > > system at the moment. > > > > I'd like to submit my most basic TYPfile and attach the file and > > patch. > > This, along with option --order-by-decreasing-area, has been > > adequate > > for me for a few years (but I have problems with my new Etrex 30x > > not > > showing some line types) > > > > Ticker > > ___ > > mkgmap-dev mailing list > > mkgmap-dev@lists.mkgmap.org.uk > > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > ___ > mkgmap-dev mailing list > mkgmap-dev@lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] New branch for default typ file
Hi Gerd Is it worth having a branch for typ-files development? Ticker On Tue, 2018-11-27 at 09:25 +, Gerd Petermann wrote: > Hi Ticker, > > okay, see > http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4258 > > Gerd > > > Von: mkgmap-dev im Auftrag > von Ticker Berkin > Gesendet: Dienstag, 27. November 2018 09:56 > An: Development list for mkgmap > Betreff: Re: [mkgmap-dev] New branch for default typ file > > Hi Gerd > > Happy with either, but slightly prefer typ-files. > > I don't think it's worth me doing another patch, it was really just a > 1 > line change to build.xml and inserting the attached file > > Ticker > > > On Tue, 2018-11-27 at 06:27 +, Gerd Petermann wrote: > > Hi Ticker, > > > > I don't like the directory name TYPs. One reason is that the > > directory doesn't contain *.TYP files, the other is that one might > > want to write TYPes instead. > > I'd prefer typ-files or maybe typ-sources. > > > > Gerd > > > > > > Von: mkgmap-dev im Auftrag > > von Ticker Berkin > > Gesendet: Montag, 19. November 2018 13:07 > > An: Development list for mkgmap > > Betreff: Re: [mkgmap-dev] New branch for default typ file > > > > Hi > > > > I suspect there will be a few TYP files for different usages. > > > > I propose that they should be handled like the styles, where they > > are > > gathered in a directory resources/TYPs and the build process copies > > then to dist/examples/TYPs > > > > I don't think a new branch is necessary, as there is nothing in the > > system at the moment. > > > > I'd like to submit my most basic TYPfile and attach the file and > > patch. > > This, along with option --order-by-decreasing-area, has been > > adequate > > for me for a few years (but I have problems with my new Etrex 30x > > not > > showing some line types) > > > > Ticker > > ___ > > mkgmap-dev mailing list > > mkgmap-dev@lists.mkgmap.org.uk > > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > ___ > mkgmap-dev mailing list > mkgmap-dev@lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] New branch for default typ file
Hi Ticker, okay, see http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4258 Gerd Von: mkgmap-dev im Auftrag von Ticker Berkin Gesendet: Dienstag, 27. November 2018 09:56 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] New branch for default typ file Hi Gerd Happy with either, but slightly prefer typ-files. I don't think it's worth me doing another patch, it was really just a 1 line change to build.xml and inserting the attached file Ticker On Tue, 2018-11-27 at 06:27 +, Gerd Petermann wrote: > Hi Ticker, > > I don't like the directory name TYPs. One reason is that the > directory doesn't contain *.TYP files, the other is that one might > want to write TYPes instead. > I'd prefer typ-files or maybe typ-sources. > > Gerd > > > Von: mkgmap-dev im Auftrag > von Ticker Berkin > Gesendet: Montag, 19. November 2018 13:07 > An: Development list for mkgmap > Betreff: Re: [mkgmap-dev] New branch for default typ file > > Hi > > I suspect there will be a few TYP files for different usages. > > I propose that they should be handled like the styles, where they are > gathered in a directory resources/TYPs and the build process copies > then to dist/examples/TYPs > > I don't think a new branch is necessary, as there is nothing in the > system at the moment. > > I'd like to submit my most basic TYPfile and attach the file and > patch. > This, along with option --order-by-decreasing-area, has been adequate > for me for a few years (but I have problems with my new Etrex 30x not > showing some line types) > > Ticker > ___ > mkgmap-dev mailing list > mkgmap-dev@lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] New branch for default typ file
Hi Gerd Happy with either, but slightly prefer typ-files. I don't think it's worth me doing another patch, it was really just a 1 line change to build.xml and inserting the attached file Ticker On Tue, 2018-11-27 at 06:27 +, Gerd Petermann wrote: > Hi Ticker, > > I don't like the directory name TYPs. One reason is that the > directory doesn't contain *.TYP files, the other is that one might > want to write TYPes instead. > I'd prefer typ-files or maybe typ-sources. > > Gerd > > > Von: mkgmap-dev im Auftrag > von Ticker Berkin > Gesendet: Montag, 19. November 2018 13:07 > An: Development list for mkgmap > Betreff: Re: [mkgmap-dev] New branch for default typ file > > Hi > > I suspect there will be a few TYP files for different usages. > > I propose that they should be handled like the styles, where they are > gathered in a directory resources/TYPs and the build process copies > then to dist/examples/TYPs > > I don't think a new branch is necessary, as there is nothing in the > system at the moment. > > I'd like to submit my most basic TYPfile and attach the file and > patch. > This, along with option --order-by-decreasing-area, has been adequate > for me for a few years (but I have problems with my new Etrex 30x not > showing some line types) > > Ticker > ___ > mkgmap-dev mailing list > mkgmap-dev@lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
