Hi;
I am experiencing challenges harvesting building
from a university with many campuses. The campuses are linked with a relation type=site
and tagged amenity=university
and the sites themselves are named uniquely while the operator=
is the same.
[out:json];
area[name="Western Cape"]->.b;
way(area.b)[operator='Cape Peninsula University of Technology'];
map_to_area -> .a;
out body;
>;
out skel qt;
Executes correctly and returns the sites but
[out:json];
area[name="Western Cape"]->.b;
way(area.b)[operator='Cape Peninsula University of Technology'];
map_to_area -> .a;
way["building"](area.a);
out body;
>;
out skel qt;
does not return isolated buildings.
Only buildings that are enclosed within University Grounds
are returned and buildings not on "traditional" grounds are excluded - this is even though isolated buildings are University Grounds
. How must the query change to accommodate isolated buildings not on "traditional" University Grounds
? Are the Tags
effective or should these change? Must University Grounds
be a separate area bigger than features - such as building
- it contains?
asked
25 Feb '21, 15:58
arkriger
155●13●14●21
accept rate:
0%
Please advise if I should open a separate question:
I believe the 'amenity=university' on each campus including the site relation is unnecessary. I should delete the 'amenity=university' on each campus and leave only the 'amenity=university' on the relation.
Is this correct?
No I would not do that site relations are relatively uncommon & therefore not often consumed (for instance I don't believe the main Carto-OSM render consumes them, in which case all labelling of Western Cape sites would cease).