FYI Population specified on admin boundaries

Hi, The French osm community decided to remove the population tag from cities and towns and add them the municipality admin-border instead. Because of this tagging place=city can not be displayed at certain zoomlevels based on the population anymore. I added this to the relation file to have large cities nicely popup early on lower zoomelvels again type = boundary & boundary = administrative & population = * { apply role=admin_centre { set population = '${population}'; } } (or bettter: you assign it here to a new tag "population_from_boundaries" and check both in the points style to avoid accidential overwrites, which I actually did) Kind regards, Joris Bo jorisbo@hotmail.com<mailto:jorisbo@hotmail.com>

Hi Joris, doesn't that mean that the population of the whole country is used for the capital? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joris Bo <jorisbo@hotmail.com> Gesendet: Mittwoch, 17. Februar 2021 08:12 An: Development list for mkgmap Betreff: [mkgmap-dev] FYI Population specified on admin boundaries Hi, The French osm community decided to remove the population tag from cities and towns and add them the municipality admin-border instead. Because of this tagging place=city can not be displayed at certain zoomlevels based on the population anymore. I added this to the relation file to have large cities nicely popup early on lower zoomelvels again type = boundary & boundary = administrative & population = * { apply role=admin_centre { set population = '${population}'; } } (or bettter: you assign it here to a new tag “population_from_boundaries” and check both in the points style to avoid accidential overwrites, which I actually did) Kind regards, Joris Bo jorisbo@hotmail.com<mailto:jorisbo@hotmail.com>

That's one to check 😊 This evening.... Otherwise exclude if capital = 2 or something like that Or in my case I use population from place=city if specified and else from admin-boundary Met vriendelijke groeten, Joris Bo jorisbo@hotmail.com -----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens Gerd Petermann Verzonden: woensdag 17 februari 2021 08:58 Aan: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk> Onderwerp: Re: [mkgmap-dev] FYI Population specified on admin boundaries Hi Joris, doesn't that mean that the population of the whole country is used for the capital? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joris Bo <jorisbo@hotmail.com> Gesendet: Mittwoch, 17. Februar 2021 08:12 An: Development list for mkgmap Betreff: [mkgmap-dev] FYI Population specified on admin boundaries Hi, The French osm community decided to remove the population tag from cities and towns and add them the municipality admin-border instead. Because of this tagging place=city can not be displayed at certain zoomlevels based on the population anymore. I added this to the relation file to have large cities nicely popup early on lower zoomelvels again type = boundary & boundary = administrative & population = * { apply role=admin_centre { set population = '${population}'; } } (or bettter: you assign it here to a new tag “population_from_boundaries” and check both in the points style to avoid accidential overwrites, which I actually did) Kind regards, Joris Bo jorisbo@hotmail.com<mailto:jorisbo@hotmail.com> _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (2)
-
Gerd Petermann
-
Joris Bo