Re: [mkgmap-dev] default style improvements
Hi Ticker I think I found the posts for polygons, lines and points. I will have a look into it on the weekend. Regards, Michael -Ursprüngliche Nachricht- Von: mkgmap-dev Im Auftrag von Ticker Berkin Gesendet: Montag, 11. Februar 2019 20:43 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] default style improvements Hi Michael The changes to the default style haven't been applied and released yet. There were in 3 posts on 21-Jan around 06:30. Regards Ticker On Sat, 2019-02-09 at 07:49 +0100, Michael Poesdorf wrote: > Hi Ticker, > > I'm not sure if I've seen changes from 21st of Jan. > I tested r 4262 and it is working very well for me. > Just adopted some resolutions of lines according to my personal > flavour. > > Regards, Michael > > -Ursprüngliche Nachricht- > Von: mkgmap-dev Im Auftrag > von Gerd Petermann > Gesendet: Dienstag, 5. Februar 2019 09:26 > An: Ticker Berkin ; Development list for > mkgmap > Betreff: Re: [mkgmap-dev] default style improvements > > Hi Ticker, > > I'd prefer to get some positive feedback. I did not even try to > understand the reasons for all these changes because I hoped for some > feedback from the other typ file experts. > > Gerd > > > Von: mkgmap-dev im Auftrag > von Ticker Berkin > Gesendet: Dienstag, 5. Februar 2019 09:12 > An: Development list for mkgmap > Betreff: Re: [mkgmap-dev] default style improvements > > Hi Gerd > > Given the lack of comments and objections, can you apply my 3 patches > to default style points/lines/polygons from 21-Jan > > Thanks > 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 ___ 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] Option handling with polish input (*.mp)?
It is a good idea to take the settings from the MP file. All those who will convert the MP file for the first time with Mkgmap will expect exactly this behavior. I remember, I was very surprised when I first converted the MP file and got an IMG file with a name different from the ID identifier from the [IMG ID] section... -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] Option handling with polish input (*.mp)?
Hi, with OSM data we provide options like family id, mapname etc. as program arguments. In *.mp files many of these options can be specified in the so called "IMG ID" section. In the past the polish reader in mkgmap didn't evaluate most of these parameters, there was no intention to replace the functionality of cGPSmapper. Now I learned about tools that create *.mp files as output and that mkgmap might be the better choice to process those files. So far so good. Problem: What is expected when the mkgmap options conflict with those in the *.mp file? My current understanding is this: 1) *.mp overwrites mkgmap builtin defaults 2) mkgmap options overwrite *.mp information Would that work? Gerd ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Commit r4271: improve reader for polish (*.mp) format
popej wrote > - I can't control parameters defining house number after street name or > zip code before city name. I guess mkgmap takes them form some config > file, which is not used for mp sources. Data is now taken from *.mp source See http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=4275 popej wrote > - Value of mapid is taken form file name instead of mp source. > I guess I should evaluate this line instead? > ID=9940015 I hope the labels work besser now, I did not test it very much. Gerd -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] Commit r4275: improve reader for polish (*.mp) format:
Version mkgmap-r4275 was committed by gerd on Tue, 12 Feb 2019 improve reader for polish (*.mp) format: - handle ~[0x1d] in country name and translate labels in Numbers with decoder - evaluate and use POIZipFirst, POINumberFirst, and Transparent keywords in IMG ID section to set TRE header. Maybe transparent needs more work - evaluate CountryName and RegionName keywords in IMG ID (not yet used) http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=4275 ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] Commit r4274: revert changes from r4273, not the right place to do this
Version mkgmap-r4274 was committed by gerd on Tue, 12 Feb 2019 revert changes from r4273, not the right place to do this http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=4274 ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] documentation improvement patch
Hi Gerd, I think it's quite similar to my idea. Just I was thinking to have one option to summarise the option file, you were suggesting. As option file is more easy to implement, I think its better to go your way first. The only advantage of my approach is that we later on can change the options if best practice is changed and user don't need to update any option file Henning On 11 Feb 2019, 17:50, at 17:50, Gerd Petermann wrote: >I think we can create a file in examples called maybe good-options.cfg >which contains options like >route >index >housenumbers >gmapi >gmapsupp >nsis >... (to be defined) > >Do we really need more? > > > > > > >Von: mkgmap-dev im Auftrag von >Henning Scholland >Gesendet: Montag, 11. Februar 2019 10:10 >An: Development list for mkgmap >Betreff: Re: [mkgmap-dev] documentation improvement patch > >Hi, >Maybe it is a good idea to introduce some switch like 'just create a >simple map'='for Garmin device and BaseCamp' , where mkgmap is always >doing, what is currently best practice and new people get easily a map >eg. for copying to their Garmin device or Basecamp or MapSource. >So he don't need to worry an index is missing... > >All the existing users still can keep their scripts with their specific >settings. > >Henning >On 11 Feb 2019, at 02:12, Mike Baggaley >mailto:m...@tvage.co.uk>> wrote: > >Hi Gerd, I have attached a patch to improve the documentation of the >command >line. I did it some time ago and had forgotten about it, but the >discussion >on whether to change default options prompted me to come back to it. >The >change is purely to the documentation, no code changes. > >Please review and if it meets with your approval, commit. > >Thanks, >Mike > > > >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
