From be5b7f2f8cb2a01c29b69be2b0d71ffd4f332abc Mon Sep 17 00:00:00 2001 From: Vladimir Byko-Ianko Date: Tue, 16 Oct 2018 12:18:22 +0300 Subject: [PATCH] Review fixes. --- generator/translator_planet.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/generator/translator_planet.cpp b/generator/translator_planet.cpp index 88c6526616..be639fb861 100644 --- a/generator/translator_planet.cpp +++ b/generator/translator_planet.cpp @@ -212,7 +212,7 @@ void TranslatorPlanet::EmitArea(FeatureBuilder1 & ft, FeatureParams params, return; // @TODO(bykoianko) Now if a feature (a relation in most cases and a way in a rare case) has tag - // place with a value city, town or village (IsCityTownOrVillage() returns true) city boundary + // place with a value city, town, village or hamlet (IsCityTownOrVillage() returns true) city boundary // will be emitted. It's correct according to osm documentation but very often city boundaries // are mapped in another way. City boundary may be mapped with a relation of a few lines and // one point (town of city name). And only this point has tag place with an appropriate value.