/*
This has been generated by the overpass-turbo wizard.
The original search was:
“place=town and population=*”
*/
[out:json][timeout:250];
// gather results
(
// query part for: “place=town and population=*”
node["place"="city"]({{bbox}});
way["place"="city"]({{bbox}});
relation["place"="city"]({{bbox}});
node["place"="town"]({{bbox}});
way["place"="town"]({{bbox}});
relation["place"="town"]({{bbox}});
);
// print results
out body;
>;
out skel qt;
/*
This has been generated by the overpass-turbo wizard.
The original search was:
“place=town and population=*”
[out:json][timeout:250];
// gather results
(
// query part for: “place=town and population=*”
node["place"="city"]["population"](if:t["population"]<5000)({{bbox}});
way["place"="city"]["population"](if:t["population"]<5000)({{bbox}});
relation["place"="city"]["population"](if:t["population"]<5000)({{bbox}});
node["place"="town"]["population"](if:t["population"]<5000)({{bbox}});
way["place"="town"]["population"](if:t["population"]<5000)({{bbox}});
relation["place"="town"]["population"](if:t["population"]<5000)({{bbox}});
);
// print results
out body;
>;
out skel qt;
*/
kind_detailvalues (eg city, town, village) which we map tomin_zoom, and most havepopulationvalues. But there are sometimes hundreds when just a handful can end up being labeled. We can't select by population ranked via zoom because that would leave the more rural areas of the map looking empty. So instead we need to cull features based on a grid that roughly matches how many features we could actually label in a given tile.That same area via Overpass Turbo:
Helpful queries: