WikiProject Uganda/Conventions-Categories

    

WikiProject Uganda

Browse map of Uganda

 

^{0°30′00.00″ N, 32°34′48.00″ E}

 

Edit map with iD

Ugandan OSM community

Forum (talk-ug)

---

Users in Uganda

OSMF members in Uganda

OSM Guidelines & Training Workgroup

---

@joinchat/yHa8dzeh645hYmFk

Invite to UG-OSM Guides & Training

OSM Africa

---

@osmafrica

@OSMAfrica

HOT Uganda

---

@hot_uganda

 @hotosm

MapUganda

---

@mapuganda

 @mapuganda

OpenStreetMap Uganda

Conventions / Guidelines

Workgroup: By-laws,Memorandum

---

Members

MoM-Discussion & Activities

Info, Overview, Editing (discussion)

---

Guidelines Categories

Data Sources

 

Categories for UG Guidelines

Category Sub-Category Workgroup Priority	Current practice in UG Issues with current mapping Activities UG Guidelines Workgroup
Offsets Calibration of layers & images Workgroup Priority Low Medium High	Imagery needs to be aligned with existing mapped items before mapping starts. Offsets details No common strategy how to define offsets and calibration points. / OSM philosophy of "Ground Truth" not consistently applied. / OSM Imagery Offset Database] not used. / Training materials are spread across different sources. / no QA strategy 1. What do we have, general State of the Map UG, is the data consistent ? --26-03-2021--Bert Araali (on osm)
Offsets Field survey support Tagging schemes to record and support maintenance and input of field survey. Workgroup Priority Low Medium High	source=*, fixme=* and note=* to flag issues or additional not taggable information. Tags for quality and maintenance are currently missing. Possible candidates are: check_date=*, survey:date=*, operational_status=* 1. What do we have, general State of the Map UG, is the data consistent ? --18/05/2021--Bert Araali (on osm)
Map changes Procedures for map changes and maintenance Workgroup Priority Low Medium High	Do less deletions, use life-cycle tagging instead. No common strategy how to change existing map features and tagging, too many deletions take place / life-cycle tagging is unknown. 1. What do we have, general State of the Map UG, is the data consistent ? --18-05-2021--Bert Araali (on osm)
Highways Roads, tracks and paths  High   Medium   Low	Draw as ways. Add classification highway=* and a name name=* & reference ref=*. Junction and roundabouts as single nodes junction=*. Classification scheme applied in UG is Highway Tag Africa Mapping and tagging details according Highways. Roundabouts as , traffic lights on junctions highway=traffic_signals, individual lanes lanes=* according Lanes, sidewalks highway=path & sidewalk=*, bridges bridge=yes & tunnels tunnel=yes, crossings crossing=*, barriers barrier=* and turn Relation:restriction & access restrictions access=*. Common features in relations Relation:route route=road. Add detail highway features like streetlamps man_made=street_lamp, sign- and guideposts information=guidepost, median strips barrier=* natural=*, embankments embankment=* & cuttings cutting=*, drainage and culverts waterway=drain + tunnel=culvert. Details for maxspeed=*, maxheight=*, maxwidth=* and maxweight=*. Map as areas area|highway and group furniture and infrastructure in highway=junction & Relation:street. Details: #Highways. Confusion + inconsistency between local and global classification / no managerial classification / values change on single roads / different interpretation of classification. 1. What do we have, general State of the Map UG, is the data consistent ? --26-03-2021--Bert Araali (on osm)
Highways Traffic signs Traffic signs along roads  High   Medium   Low	Draw as on highways and tag with traffic_sign=UG:ID. Draw as along highways at physical location. Details like appearance (support=*,height=*,size=*,colour=*) and material material=*. Details: #Traffic signs Missing mapping strategy images, training & QA sections. Proposal team: Bert Araali (on osm) Convention proposal page: Road signs in Uganda (Traffic Signs) (redirect from Traffic Signs). 8. Discuss and integrate inputs to improve the proposal. --02-04-2021--Bert Araali (on osm)
Highways Barriers Hedges, walls, bollards, speed bumps etc...  High   Medium   Low	Drawn as on or along highways, or across highways sharing a with the highway=* and tag with barrier=*. Add details like appearance (height=*,size=*,colour=*) and material material=*. Details: #Barriers Strategy when to use node,linear or area / destroyed bridges and other (temporary) route interruptions / missing local images Proposal team: Bert Araali (on osm) Convention proposal page: Barriers 1. What do we have, general State of the Map UG, is the data consistent ? --02-04-2021--Bert Araali (on osm)
Buildings All man_made buildings  High   Medium   Low	Draw as .building=yes is mandatory. Specific (architectural) type with building=*. Use of a building with amenity=* and leisure=* added as or containing the building(s) (see also POIs, ROIs & VOIs). Entries and exits with entrance=*. Important facilities: water tanks building=storage_tank man_made=storage_tank content=water and toilets amenity=toilets. Details like material material=*. Consider indoor and 3D mapping. Details: #Buildings. Mixing of type and use / Indoor and 3D mapping largely unknown. / incomplete and contradicting wiki for Indoor & 3D mapping 1. What do we have, general State of the Map UG, is the data consistent ? --02-04-2021--Bert Araali (on osm)
Buildings Addresses Addresses for buildings and building parts.  High   Medium   Low	Addresses belong to buildings or building parts, not the POI. in the middle of the building or plot with addr: prefix like addr:housenumber=*, addr:street=*, addr:postcode=* etc... Details for building internals or parts (with indoor mapping) and addr:unit=* and/or addr:housename=*. Details: #Addresses. no consistency in UG / addresses added to the POI or ROI / postbox addresses need to be tagged on the business. 1. What do we have, general State of the Map UG, is the data consistent ? --09-04-2021--Bert Araali (on osm)
Buildings 3D 3-dimensional buildings  High   Medium   Low	For major public spaces and buildings. Simple 3D buildings according to the Simple 3D buildings and Roof lines tagging schemes . Details like materials material=* and appearance colour=*. Minor details like handrails (barrier=fence, columns building:part=*, chimneys building:part=*, doors and windows building:part=* entrance=* etc... Details: #3D. Deletions and overwriting of 3D mapping because largely unknown / inconsistent (global) wiki pages. 1. What do we have, general State of the Map UG, is the data consistent ? --02-04-2021--Bert Araali (on osm)
Buildings Indoor Indoor building maps  High   Medium   Low	For major public buildings. Add tagging for rooms, corridors, areas and levels according to Simple Indoor Tagging. Indoor ways for routing highway=*. Details like materials material=* and appearance colour=*. Handrails (barrier=fence, columns indoor=column, doors and windows indoor=door barrier=wall etc.. Details: #Indoor. Deletions and overwriting of 3D mapping because largely unknown / inconsistent (global) wiki pages. 1. What do we have, general State of the Map UG, is the data consistent ? --02-04-2021--Bert Araali (on osm)
Points, Regions & Volumes of Interest (POIs, ROIs & VOIs) All specific point or region we useful or interesting.  High   Medium   Low	A point of interest (POI) is a specific point (node or waypoint) location that someone may find useful or interesting. It includes region of interest (ROI) and a volume of interest (VOI). In OSM most POI's, ROI's and VOI's all belong to the top level tags man_made, amenity and leisure. Draw as nodes. ROI's are drawn as areas or polygons. VOI's are less common and tagged as relations. A single entity shall be tagged with only 1 map feature. Tag as man_made=*, amenity=* or leisure=*. Applying a name=* is common and mandatory. Additional tags to provide detailed information are specified. Position on the map might be improved by tagging separate entrances. Postbox addresses can be added. Add additional tagging (called annotation) for opening hours [[Key:|]]=*, website or web page website=*, website, contacts phone=* fax=* mobile=*, email=*... contact:=* prefix. Operator, owner and brand information with tags operator=*, owner=*, brand=*. More are mapped separately. Example: a bar stand, swimming pool, DJ stand etc... Details: #Points, Regions & Volumes of Interest. large scope implies many tagging schemes are unknown / clear sub-categorisation missing / a lot of undocumented custom keys / Values with inconsistent. 1. What do we have, general State of the Map UG, is the data consistent ? --02-04-2021--Bert Araali (on osm)
POIs, ROIs & VOIs Catering and Tourism Hotels, resorts, restaurants, bars ...  High   Medium   Low	or on the building or area and name=* is mandatory for: accommodation: hotels, motels, guest houses, lodges, apartments for short stay, chalets, hostels (incuding those for students), mountain and wilderness huts, caravan sites, camping sites and pitches. Tag with tourism=*. animal accommodation. Accomodation of animals like quarantaine facilties, animal hotels, animal shelters. Does not include zoos, reserves and national parks. Tag with amnity=animal_boarding. Tag the plot or land as landuse=commercial. Details like materials material=* and appearance colour=* and specific sector tags like : Details: #Catering and Tourism. No clear list what is included, gaps remain undefined. 1. What do we have, general State of the Map UG, is the data consistent ? --02-04-2021--Bert Araali (on osm)
POIs, ROIs & VOIs Cultural facilties Movie theatre, theatres ...  High   Medium   Low	or on the building or area and name=* is mandatory for: Details like materials material=* and appearance colour=* and specific sector tags like : Details: #Cultural facilties. No clear list what is included, gaps remain undefined.
POIs, ROIs & VOIs Religious facilties Buildings for worshipping, burial grounds, sites with religious meaning or worshipping practices...  High   Medium   Low	or on the building or area and name=* is mandatory for: Details like materials material=* and appearance colour=* and specific sector tags like : Details: #Religious facilties. No clear list what is included, gaps remain undefined.
POIs, ROIs & VOIs Public and government facilities & services Government & public service offices, ministeries, police ...  High   Medium   Low	or on the building or area and name=* is mandatory for: Details like materials material=* and appearance colour=* and specific sector tags like : Details: #Public and government facilities & services. No clear list what is included, gaps remain undefined.
POIs, ROIs & VOIs Educational institutions Nurseries, schools, colleges, universities, vocational institutions.  High   Medium   Low	or on the building or area and name=* is mandatory for: Details like materials material=* and appearance colour=* and specific sector tags like : Details: #Educational institutions. No clear list what is included, gaps remain undefined.
POIs, ROIs & VOIs Health facilities Doctors, nurses, pharmacies, clinics, hospitals, quarantaine facilties, health research.  High   Medium   Low	or on the building or area and name=* is mandatory for: Details like materials material=* and appearance colour=* and specific sector tags like : Details: #Health facilties.
POIs, ROIs & VOIs Leisure and entertainment industry Beaches with bars, swimming pools, zoos, disco/dancehall.  High   Medium   Low	or on the building or area and name=* is mandatory for: Details like materials material=* and appearance colour=* and specific sector tags like : Details: #Leisure and entertainment industry. No clear list what is included, gaps remain undefined.
POIs, ROIs & VOIs Social facilities Playgrounds, village gathering.  High   Medium   Low	or on the building or area and name=* is mandatory for: Details like materials material=* and appearance colour=* and specific sector tags like : Details: #Social facilties.
POIs, ROIs & VOIs Sports facilities Pitches, golf courses, race tracks, gyms, tennis courts, horse riding.  High   Medium   Low	or on the building or area and name=* is mandatory for: Details like materials material=* and appearance colour=* and specific sector tags like : Details: #Sports facilties.
POIs, ROIs & VOIs Commercial and retail facilities Markets, shops.  High   Medium   Low	or on the building or area and name=* is mandatory for: Details like materials material=* and appearance colour=* and specific sector tags like : Details: #Commercial and retail facilities.
POIs, ROIs & VOIs Financial institutions and services Banks, currency exchange, mobile money agents, ATM's, SACCO's, mortgage and lending agents, insurance companies.  High   Medium   Low	or on the building or area and name=* is mandatory for: Details like materials material=* and appearance colour=* and specific sector tags like : Details: #Financial institutions and services.
POIs, ROIs & VOIs Small, medium and large manufacturing enterprises Craftsmen, factories, warehouses, wholesale.  High   Medium   Low	or on the building or area and name=* is mandatory for: Details like materials material=* and appearance colour=* and specific sector tags like : Details: #Small, medium and large manufacturing enterprises.
Water Features which are rivers, streams, lakes, ponds and reservoirs, canals, ditches and drains.  High   Medium   Low	LInear features, like rivers, streams, canals, drains, ditches are mapped as and tagged as waterway=* with corresponding value. The direction of the waterway points downstream. Water bodies like lakes, ponds and reservoirs as with natural=water and water=*. Add at least a name=* if known. Bridges need to be tagged with bridge=yes and layer=1 on the highway=* containing the bridge. Waterways passing under a highway=* as separate section with tunnel=yes or tunnel=culvert and layer=-1. Best practice for waterways in sections or branched is to put the common tags, mostly water=* / name=* in a type=waterway. Large barriers and features in the waterway are mapped as , part of the waterway or as crossing the waterway or and sharing a . Tag with waterway=dam, waterway=weir, waterway=waterfall or waterway=rapids. Wide waterways are drawn along the banks. The banks being located as visual or as median of the maximum water levels of all months of the year. Most common tag is waterway=riverbank with alternative natural=water and water=* gaining popularity. Temporary dry waterways are most commonly tagged as intermittent=yes. Add facilties as waterway=dock and waterway=boatyard. Add smaller size barriers. Map the riverbeds and islands with natural=* (don't overlap !). Add additional optional tags as usage=irrigation. Details: #Water Features. Decide waterway=riverbank vs natural=water and water=river / inconsistent mapping and tagging of large bodies and water levels / resolve inconsistencies in irrigation systems and reservoirs 1. What do we have, general State of the Map UG, is the data consistent ? --04-05-2021--Bert Araali (on osm)
Water features which are mainly rivers, streams, lakes, ponds and reservoirs. Lake Victoria / lakes with varying levels High	Lakes are mapped as areas. Flood areas can be mapped as hazardous zones. Tag with natural=water and water=lake. Editing, and in case of damage, of Lake Victoria has become more and more difficult. The relation is too big and often editing conflicts arise due to it's large geographical extend. Suggestion is made to divide the lake in bays, island groups and a common middle area and use parent and child relations. It is a rather technical discussion and solution. Flood zones are hardly or not mapped in Uganda but, due to the recent significant changes in the level of many lakes, become more and more significant due to the humanitarian impact the resulting floods have. We see often changes in the polygons representing the lakes to reflect current short term water levels by adjusting shores. A change in mapping phylosophy is emminent, to map avaergae water levels (like on a 10 year span) instead of mapping actual ones and keep on changing them when new imagery comes available. Mapping flood zones (hazards) can be easily achieved reflecting the 10 year high and low water levels. Lakes sofar identified where this is a major issue: Lake Victoria, Lake ALbert, Lake Wamala.
Land Use which is mainly residential, commercial, industrial and agriculture.  High   Medium   Low	Draw as closed ways (also called areas). For general mapping enclosing large areas, like a complete village, a large area of land mainly used for agriculture etc... Tag with a specific value for landuse=*. should not overlap with other tagged as landuse=*. Keep a small gap from highway=*. Add the areas on a more detailed, lower scale, like on plot size. Details: #Land Use. Some areas (villages) are mapped very inaccurately on macor scale / Some areas are mapped as residential where other tagging or boundary would be more appriate (refugee camps) 1. What do we have, general State of the Map UG, is the data consistent ? --29-04-2021--Bert Araali (on osm)
Land Use Land ownership and conflicts Mapping of areas with ownership information and retaining neutral practices in regard to land conflicts.  High   Medium   Low	We don't map land ownership as it is not verifiable on the ground. Mapping of landuse is preferred on a micro scale to reflect the linear and unmanaged expansion of landuse. Actual landuse, as is on the ground may overlap with natural=* (or landcover=*. The land ownership is only used for land gazetted and officially owned by the government with owner=government, all other land is to be considered by default as "private", we don't use owner=private. Applying strict and private ownership tags incites conflicts and should be forbidden and deleted by the community. boundary used for administrative areas and protected areas like the common forest reserves and national parks, for natural=wetland and landuse=forest are the cases where owner=government might be used. Some areas contain private information / strategy to manage land conflicts through OSM data is missing / ownership, especially when it concerns government land, is not mapped / confllct zones are not mapped to actual ground truth but desired situation to avoid conflicts. 1. What do we have, general State of the Map UG, is the data consistent ? --06-05-2021--Bert Araali (on osm)
Natural features & Landcover Natural features that cover land like forest/wood and trees, scrub, heath, grass ... . Mountain features like peaks, cliffs, ridges, valleys etc...  High   Medium   Low	Draw an around the area covered with a single type of vegetation. Tag with natural=*. Tree rows as with natural=treerow. Hedges as tag with barrier=hedge. Draw mountain peaks as nodes and tag with natural=peak, it's elevation (in m) with ele=* is manadatory. Other mountain features as and tag with one of the natural=* values from the Landforms. Draw forests and wetlands as closed ways (also called areas). Mountain peaks must have the tag natural=peak, additionally if known add the name=* and it's elevation with ele=*. Forests must be tagged with natural=wood or natural=forest. Wetlands must be tagged with natural=wetland. Remark: implement these large forests and wetlands with relation boundaries so they can be easily detailed later on.
Administrative Boundaries & Places Boundaries for the different administrative areas in Uganda and place names  High   Medium   Low	Map as and/or . Tag with their type key:place and key:name. The relations are tagged with boundary=*, boundary=administrative, see also Key:boundary#Boundary_types and Boundaries. Add administrative level with admin_level=* according Tag:boundary=administrative. The country, regions and districts are mapped as . Lower levels like counties, sub-counties and parishes (mnicipalities), villages (zones and wards), suburbs etc... are not mapped as boundaries but mostly as nodes. Other large features like nature parks boundary=national_park and boundary=protected_area protect_class=1a or protect_class=2, wildlife reserves boundary=protected_area protect_class=1b, forest reserves boundary=protected_area protect_class=6 are identified with relations. See also Tag:boundary=protected_area. Map counties, sub-counties, parishes, villages as boundaries. Additional data is added like population and household numbers. Details: #Administrative Boundaries & Places. Not all admin levels have separate level in UG / Boundary mapping with relations largely unknown / no qualification for place types like villages as urban - rural - trading center / is_in:country remains from old imports, other is_in not used consistently, addr:=* and note=* is used instead but inconsistently / no links to wikidata or wikipedia / insufficient data sources for current situation, missing boundaries up to district level / IUCN levels not defined in UG (speifically problem with protect_class=* 1a / 2) / Large areas incorrectly mapped as multipolygons (forst reserves) / Admin boundaries for other purposes missing 1. What do we have, general State of the Map UG, is the data consistent ? --29-04-2021--Bert Araali (on osm)

Stepped approach for developing UG Guidelines

1. What do we have, general State of the Map UG, is the data consistent ?

• General statistics are given on the Conventions-Categories page.
• Detailed statistics are given on the Guideline Proposal page.

2. Assign proposal writer team.
3. Which Global Guidelines do we have, what are their caveats, can we use them in UG ?

• Described in the "Rationale" section of the Guideline Proposal page.

4. Identify the gaps, both for general, detailed as micro-mapping.

• General gap description are given on the Conventions-Categories page.
• Detailed gap description is given in the "Rationale" section of the Guideline Proposal" page.

5. Prepare training and info materials for a workshop on the category, concerning existing tagging and standard OSM tagging.

• Prepared as a presentation supported with video materials.
• The workshop is recorded for later reference and future workshops.

6. Identify local data sources and their reliability - where do we get more data to support our mappers.

7. Make a proposal for a local UG guideline.
8. Discuss and integrate inputs to improve the proposal.
9. Vote on the proposal.
10. Make an accepted UG guideline and extend with lots of examples and training material.
11. Make a roadmap for validation and QA.
12. Publish, promote and support implementation by the different mapping groups in UG.
13. If we do a good job, be very ambitious and bring our work for global proposals & approval, we can do it !

Additional category information

Offsets

Offsets
Calibration of layers & images
 High   Medium   Low  

Current mapping guideline

Layers and imagery needs to be aligned with existing mapped items before mapping starts. Offsets for specific imagery and calibration points are stored in OSM Imagery Offset Database for editing with JOSM. In iD manual alignment is required with on the ground elements like highways (roads).

Issues with current mapping guideline

• There is no common strategy how to define offsets and calibration points. HOT has a strategy based on "Armchair mapping" and Bing as "Golden Standard". This does not comply with the OSM philosophy of "Ground Truth" = GPS tracks and field mapping and does not describe alternative sources like Mapillary, KartaView/OpenStreetCam and Strava.
• Use of OSM Imagery Offset Database with JOSM or as JSON datasource is unknown & inconsistent. Only a small part of UG is covered.
• Training materials are spread across different sources and to general.
• UG has no QA strategy to deal and solve with misaligned new or changed data. Mostly beginners do not comply and cause major damage to the map.

Ongoing activities

1. What do we have, general State of the Map UG, is the data consistent ? --26-03-2021--Bert Araali (on osm)

Statistics

Statistics OSM Imagery Offset Database:

71 mostly Kampala / Wakiso / Entebbe & Jinja / Mount Elgon

Estimated required:

• 80 000 (=# villages)
• 1364 < x < 12276 (15 km < x < 5 km radius polygons)

(as per 01-04-2021)

#top

Highways

Highways
Roads, tracks and paths
 High   Medium   Low  

Current mapping guideline

Draw as ways. Add classification highway=* and a name name=*. Classification scheme applied in UG is Highway Tag Africa, a variant and customised version of Highways#Classification.

• Names and references are typically added from open public data resources (UNRA, Uganda National Roads Authorithy)
• Junctions and roundabouts are typically mapped as single nodes junction=roundabout.
  

Mapping and tagging details according Highways.

• Names name=* & references ref=* are verified, added & completed from signposts, thus requires street level imagery or field mapping.
• Large roundabouts as instead of and add traffic lights on junctions highway=traffic_signals.
• Individual lanes lanes=* according Lanes, sidewalks highway=path & sidewalk=*.
• Bridges bridge=yes & tunnels tunnel=yes, crossings crossing=* and barriers barrier=* are added.
• Turn Relation:restriction & access restrictions access=* for detailed router support.
• Common features of road sections are added through relations Relation:route route=road.

Add detail highway features like:

• streetlamps man_made=street_lamp;
• signposts, traffic signs and destinations with guideposts;
• median strips with details like barrier=fence, kerbs kerb=* and vegetation natural=*;
• embankments embankment=* & cuttings cutting=*,
• drainage and culverts waterway=drain + tunnel=culvert
• detailed information regarding restrictions in maxspeed=*, maxheight=*, maxwidth=* and maxweight=*.
• Map as areas area|highway and group furniture and infrastructure in highway=junction & Relation:street.

Issues with current mapping guideline

• Confusion exist with East-Africa Tagging Guidelines which was an attempt to link UNRA classification to Highway Tag Africa.
• Highway Tag Africa is created by HOTOSM. Although it states that it was achieved with community census and thre are some links to the Hot Talk list, there has never been a formal proposal process with voting from the community. It was developed based on a project in Mali and later promoted to be used all over Africa, for HOT projects and OSM at large. Local variations do however exist as it has some issues: Trunk roads are not listed (see discussion on Talk:Highway Tag Africa in Feb 2021, updates to the global tagging guidelines are not reflected or updated, unclassified is unclear and leads to the major part of the road system to be "unclassified". Improvements should be made or better detailed descriptions to what is to be considered as a "place", adoption f the unregulated development of "linear" urbanisation, for roads to be more often classified as residential and tertiary.
• There is no clear definition to link highway=* (global as well as local) to different classification systems: socio-economic vs. throughput/physical vs. management.
• Used inconsistently across Uganda. highway=* values change on single roads (task bounding box crossings in HOT), inconsistency due to participation of world wide contributors in HOT projects.
• Definition, even on global scale is unclear and causes inconsistencies especially between highway=trunk vs. highway=primary, when to apply highway=unclassified, highway=track vs. highway=path.
• Distinction of Expressways as top-level tag in UG vs.highway=primary and highway=motorway. Due to recent and ongoing infrastructure expansions in UG.

Ongoing activities

1. What do we have, general State of the Map UG, is the data consistent ? --26-03-2021--Bert Araali (on osm)

Statistics

Highway stats:

2147

476484

7

0

TOTAL: 478638

(as per 01-04-2021)

To retrieve statistics we use various overpass turbo (overpass-turbo.eu) queries.

---

Help and training material on the usage of overpass turbo can be found on its wiki page: overpass turbo -wiki page-

---

overpass turbo query for general statistics (link: Highway counts in Uganda Counts only):

 // output in JSON format, increase timeout for large query
 [out:json][timeout:250];
   {{geocodeArea:"Uganda"}}->.uganda;
 // gather results
 (
 // query part for: “highway=*”
   node["highway"](area.uganda);
   way["highway"](area.uganda);
   relation["highway"](area.uganda);
 );
 // print results
 out count;

overpass turbo query for individual class statistics(link: Highway counts in Uganda counts, data and map):

 /*
 This query looks for nodes, ways and relations 
 with the given key.
 */
 [out:json][timeout:250];
 {{geocodeArea:"Uganda"}}->.uganda;
 // gather results
 (
  // query part for: “highway=*”
  node["highway"="trunk"](area.uganda);
  way["highway"="trunk"](area.uganda);
  relation["highway"="trunk"](area.uganda);
 );
 // print results
 (._;>;);
 out count;
 (._;>;);
 out body;
 >;
 (._;>;);
 out skel qt;

#top

Highway subs (categories & guidelines)

Traffic signs

Highways
Traffic signs
Traffic signs along roads
 High   Medium   Low  

Current mapping guideline

Draw as on highways and tag with traffic_sign=UG:ID. In some cases specific tagging may be added on highway=* sections.

Categorized and listed as per The Highway Code pdf.

Draw as along highways at physical location. Add details like appearance (support=*,height=*,size=*,colour=*) and material material=*.

Issues with current mapping guideline

• Add mapping strategy icons, training & QA sections.
• Add additional image files (vector .svg preferred).
• Add image files to Wikimedia Commons so they can be used in Uganda specific routers and rendering.

Ongoing activities

Proposal team: Bert Araali (on osm)
Convention proposal page: Road signs in Uganda (Traffic Signs) (redirect from Traffic Signs).
8. Discuss and integrate inputs to improve the proposal. --02-04-2021--Bert Araali (on osm)

Statistics

Traffic_sign stats:

219

(as per 01-04-2021)

To retrieve statistics we use various overpass turbo (overpass-turbo.eu) queries.

---

Help and training material on the usage of overpass turbo can be found on its wiki page: overpass turbo -wiki page-

---

overpass turbo query for general statistics (link: Traffic sign counts in Uganda Counts only):

/*
This query looks for nodes, ways and relations 
with the given key.
Choose your region and hit the Run button above!
*/
[out:json][timeout:250];
{{geocodeArea:"Uganda"}}->.uganda;
// gather results

(

  // query part for: “traffic_sign=*”
  node["traffic_sign"](area.uganda);
  way["traffic_sign"](area.uganda);
  relation["traffic_sign"](area.uganda);
);

// print results
out count;
/*
>;
out skel qt;
*/

#top

Barriers

Highways
Barriers
Hedges, walls, bollards, speed bumps etc...
 High   Medium   Low  

Current mapping guideline

Drawn as on highways, or across highways sharing a with the highway=* and tag with barrier=*.

Same as general mapping strategy but now also along highway=* and landuse=*.

Add details like appearance (height=*,size=*,colour=*) and material material=*.

Issues with current mapping guideline

• Add mapping strategy when to use node,linear or area.
• Add mapping and tagging for destroyed bridges and other (temporary) route interruptions.
• Add image files to Wikimedia Commons so they can be used in Uganda specific routers and rendering.

Ongoing activities

Proposal team: Bert Araali (on osm)
Convention proposal page: Barriers
1. What do we have, general State of the Map UG, is the data consistent ? --02-04-2021--Bert Araali (on osm)

Statistics

Barrier stats:

6195

34824

1

0

TOTAL: 41020

(as per 02-04-2021)

#top

Buildings

Buildings
All man_made buildings
 High   Medium   Low  

Current mapping guideline

Draw as closed ways (also called areas). General tag building=yes is mandatory.

Specific (architectural) type with building=*.

Auxiliary buildings and utilities have their own values, mark them with separate tags like water tanks :building=storage_tank man_made=storage_tank content=water and toilets amenity=toilets with separate or on the building .

Entries and exits with entrance=*.

Important notice: Use of a building does not belong in this category. Tag with amenity=* and leisure=* added as or containing or as part of the building(s) (see also POIs, ROIs & VOIs).

Add more specific tagging like material material=*. Buildings of higher importance consider indoor and 3D mapping (separate sub-categories).

Issues with current mapping guideline

• Type and Use of a building are often mixed or considered as under one tag. This is not always the case and used inconsistently across Uganda.
• Due to some recent incidents with deletions and overwriting of indoor and 3D mapping these features seem to be largely unknown. We should create awareness about them and create UG guidelines how they are applied locally. Extend training materials, even for the global pages as the descriptions are incomplete and contradicting. Indoor, 3D mapping is especially interesting for major public spaces and buildings like educational institutions, ministries, shopping malls, town halls and town squares. Headquarters or centres in refugee camps.

Ongoing activities=

1. What do we have, general State of the Map UG, is the data consistent ? --02-04-2021--Bert Araali (on osm)

Statistics

Building stats:

Type	Northern Region	Eastern Region	Central Region	Western Region	Country total
	686	4625	454	61	5826
	1 917 113	890 884	1 107 675	2 450 906	6 366 578
	248	162	493	615	1518
TOTAL	1 918 047	895 671	1 108 622	2 451 582	6 373 922
Population 2014	0	0	0	0	34 634 650
Population building %	0 %	0 %	0 %	0 %	18.40 %
Households 2014	0	0	0	0	0
Households building %	0 %	0 %	0 %	0 %	0 %

Because of the large numbers, the overpass turbo query will run out of memory showing the error message:

To avoid this the query is split according to the regions. Replace the geocodeArea:"Uganda" as follows:

• geocodeArea="Northern Region, Uganda"
• geocodeArea="Eastern Region, Uganda"
• geocodeArea="Central Region, Uganda"
• geocodeArea="Western Region, Uganda"

Further reduce the load by running the queries (by commenting them out) one by one for "node", "way" and "relation". Avoid running these queries subsequently in a short timespan as you will run out of quota. You find the status of your quota with this link api/status

There is no census data of the number of buildings in Uganda. An indication of the state of the map (completeness) can be indicated by comparing, or better calculating the percentage of buildings in regard to the numbers which we have available, being population and households. The base level (in %) is the total country number from the 2014 census (National Households and Population Census 2014). The region percentages are calculated in the same way and then referenced as a percentage to the country percentage, thus we have a more comprehensible percentage on a 0 to 100% scale for the state of the map (completeness).

---

Help and training material on the usage of overpass turbo can be found on its wiki page: overpass turbo -wiki page-

---

overpass turbo query for with building=* (link: Building node counts in Uganda Counts only):

 /*
This query looks for nodes, ways and relations 
with the given key.
Choose your region and hit the Run button above!
*/
[out:json][timeout:250];
{{geocodeArea:"Uganda"}}->.uganda;
// gather results

(

  // query part for: “building=*”
  node["building"](area.uganda);
/*  way["building"](area.uganda);*/
/*  relation["building"](area.uganda);*/
);

// print results
out count;
/*
>;
out skel qt;
*/

#top

Building subs (categories & guidelines)

Addresses

Buildings
Addresses
Addresses for buildings and building parts.
 High   Medium   Low  

Current mapping guideline

Addresses belong to buildings or building parts (like shops in a mall), not the activity mapped inside the building (where they are often added).

Mapped as in the middle of the building or plot. Add address tagging with addr: prefix like addr:housenumber=*, addr:street=*, :addr:postcode=* etc...

Add more specific tagging for building internals or parts (with indoor mapping) of buildings. Tag with specific details like addr:unit=* and :addr:housename=*.

Issues with current mapping guideline

• Due to the variety and complexity in different addressing systems worldwide there is no consistency in Uganda.
• In many cases addresses for the building are added to the POI or ROI, which is incorrect and causes duplicate and inconsistent data.
• Specifically postbox addresses need to be tagged on the business or activity node instead of the building.

Ongoing activities=

1. What do we have, general State of the Map UG, is the data consistent ? --09-04-2021--Bert Araali (on osm)

Statistics

Address stats (on addr:housenumber=*):

8319

734 (building=*)

8

0

TOTAL: 9061

Concentration around Kampala / Wakiso and Manafwa district. Sparsely across the country except Karamoja.

#top

3D

Buildings
3D
3-dimensional buildings
 High   Medium   Low  

Current mapping guideline

3D mapping is especially interesting for major public spaces and buildings like educational institutions, ministries, shopping malls, town halls and town squares. Headquarters or centres in refugee camps.

Add more specific tagging for simple 3D buildings according to the Simple 3D buildings and Roof lines tagging schemes . Add more specific tagging like materials material=* and appearance colour=*.

Add more specific tagging like materials material=* and appearance colour=*. Consider more minor details like handrails (barrier=fence, columns :building:part=*, chimneys building:part=*, doors and windows building:part=* entrance=* etc...

Issues with current mapping guideline

• Due to some recent incidents with deletions and overwriting of 3D mapping these features seem to be largely unknown. We should create awareness about them and create UG guidelines how they are applied locally.
• Extend training materials, even for the global pages as the descriptions are incomplete and contradicting.

Ongoing activities=

1. What do we have, general State of the Map UG, is the data consistent ? --02-04-2021--Bert Araali (on osm)

Statistics

3D Building stats:

0

1365

4

0

TOTAL: 1369

#top

Indoor

Buildings
Indoor
Indoor building maps
 High   Medium   Low  

Current mapping guideline

Indoor mapping of buildings is especially interesting for major public buildings like educational institutions, ministries, shopping malls and town halls. Headquarters or centres in refugee camps.

Add more specific tagging for indoor mapping of buildings with rooms, corridors, areas and levels according to the Simple Indoor Tagging scheme. Create indoor ways for routing highway=*.

Add more specific tagging like materials material=* and appearance colour=*. Consider more minor details like handrails (barrier=fence, columns :indoor=column, doors and windows indoor=door barrier=wall etc..

Issues with current mapping guideline

• Due to some recent incidents with deletions and overwriting of 3D mapping these features seem to be largely unknown. We should create awareness about them and create UG guidelines how they are applied locally.
• Extend training materials, even for the global pages as the descriptions are incomplete and contradicting.

Ongoing activities=

1. What do we have, general State of the Map UG, is the data consistent ? --02-04-2021--Bert Araali (on osm)

Statistics

3D Building stats:

28

45

4

0

TOTAL: 73

#top

Points, Regions & Volumes of Interest

Points, Regions & Volumes of Interest
(POIs, ROIs & VOIs)
All specific point or region we useful or interesting.
 High   Medium   Low  

Current mapping guideline

A point of interest (POI) is a specific point (node or waypoint) location that someone may find useful or interesting. The scope is very broad and therefore divided into different subcategories.
It includes region of interest (ROI) and a volume of interest (VOI), denoting a region (area or polygon) or a volume (which may contain various individual POI's.

Points of Interest comprises a very broad scope of: catering and tourism industry, cultural facilities, religious faculties, public and government facilities and services, educational institutions, health facilities, leisure and entertainment industry, social facilities, commercial and retail facilities (markets, shops), small, medium and large manufacturing enterprises (craftsmen, factories, warehouses) ( .

In OSM most POI's, ROI's and VOI's all belong to the top level tags man_made, amenity and leisure.

Some are categorised into their own main categories because of their distinct features. Examples: water bodies, natural features, utility infrastructure (power facilties, water and sewage plants, etc...) and ROI's mapped with distinctive borders or boundaries (national parks, forestry areas etc...).

POI's are drawn as nodes. ROI's are drawn as areas or polygons. VOI's are less common and tagged as relations.

A single entity shall be tagged with only 1 map feature. Never put a within an tagged as the same kind of facility.
Tag as man_made=*, amenity=* or leisure=*. Applying a name=* is common and mandatory. For those for which have no name or the name is unknown the noname=* and fixme=* (or a note) shall be applied. Consistency in the values of the different keys is preferred.

Additional tags to provide specific information are specified. The position on the map might be improved by f.i. adding the tags at separate entrances of buildings.

Postbox addresses can be added. Building addresses are not added to the POI or ROI, they are mapped and tagged on separate nodes belonging to the building or plot, see Building Addresses.

Add additional tagging (called annotation) for opening hours [[Key:|]]=*, website or web page website=*, website, contacts phone=* fax=* mobile=*, email=*... contact:=* prefix.

Operator, owner and brand information with tags operator=*, owner=*, brand=*.

Additional details are mapped separately. Example: a bar stand, swimming pool, DJ stand or food stand on a beach, fountains, playgrounds and separate shops within a mall etc...

Issues with current mapping guideline

• Due to the large scope many tagging schemes are unknown and hard to find in the OSM wiki. We need a more clear sub-categorisation that reflects the common interpretation and practices in Uganda.
• Over the years custom keys were developed but not documented in the wiki in several projects. Global tagging schemes have evolved but the map was never updated. Need for standardisation and defining consistent (global tagging guidelines) or new tagging schemes (new UG local tagging guidelines) is highly recommended.
• Values are often applied with inconsistent syntax. Needs standardisation and consistency.

Ongoing activities=

1. What do we have, general State of the Map UG, is the data consistent ? --02-04-2021--Bert Araali (on osm)

Statistics

See individual subcategories.

#top

Points, Regions & Volumes of Interest subs (categories and guidelines)

Catering and Tourism

POIs, ROIs & VOIs
Catering and Tourism
Hotels, resorts, restaurants, bars ...
 High   Medium   Low  

Current mapping guideline

• for accommodation.

in the centre and/or around the building or campus (=area).

name=* (small letters capitalised !) is mandatory. If there is no specific name add noname=* or fixme=*, add a note.

When adding addr:=* tags only apply those belonging to the business. addr:=* tags belonging to the building(s) should be tagged according to #Addresses.

For all accommodation containing buildings extend the building(s) with specific tagging like materials material=* and appearance colour=*. Consider more minor details like handrails barrier=fence and entrances entrance=* and/or Simple_Indoor_Tagging and/or 3D.

• apartments for short stay
• camping sites and pitches
• caravan sites
• chalets
• guest houses
• hostels (including those for students)
• hotels

tourism=hotel as ;

tourism=hotel in the centre and: around the building or campus (=area).

• the hotel as a campus with tagged as landuse=commercial. Inside building=hotel or different typology with other building=*, amenity=parking, leisure=swimming_pool;
• the hotel as a building with tagged as landuse=commercial. Inside building=hotel or different typology with other building=*;

according to Hotel additional tags for micro-mapping on the tourism=hotel.

• huts in mountains and the wilderness (bush)
• lodges
• motels

• animal accommodation. This only includes facilties for the temporary accomodation of animals like quarantaine facilties, animal hotels, animal shelters. Does not include zoos, reserves and national parks. Tag with amnity=animal_boarding.
  
• catering

• restaurants
• take-aways (Fast food)
• ice-cream
• outdoor seating with dining
• cafe
• pubs
• bars

Issues with current mapping guideline

• There is no consensus yet about what should be included in this sub-category. Main issue is bars, who might operate during most part of the day as restaurants / take-ways. So do we include all bars in this category or in "entertainment" ?
• How to tag mixed facilities like f.i. hotels also offering apartments, hostels located on or affialted with a school, college or university campus, restaurants in hotels open to the general public etc...
• There is no approved local or global guideline to map quality and service ratings (stars). See Proposed_features/Awards_and_ratings.

Ongoing activities

1. What do we have, general State of the Map UG, is the data consistent ? --02-04-2021--Bert Araali (on osm)

Water Features

Water Features
which are rivers, streams, lakes, ponds and reservoirs, canals, ditches and drains.
 High   Medium   Low  

Current mapping guideline

LInear features, like rivers, streams, canals, drains, ditches are mapped as and tagged as waterway=* with corresponding value. The direction of the waterway points downstream. Water bodies like lakes, ponds and reservoirs as with natural=water and water=*. Add at least a name=* if known.

Bridges need to be tagged with bridge=yes and layer=1 on the highway=* containing the bridge. Waterways passing under a highway=* as separate section with tunnel=yes or tunnel=culvert and layer=-1.

Best practice for waterways in sections or branched is to put the common tags, mostly water=* / name=* in a type=waterway.

Large barriers and features in the waterway are mapped as , part of the waterway or as crossing the waterway or and sharing a . Tag with waterway=dam, waterway=weir, waterway=waterfall or waterway=rapids.

Wide waterways are drawn along the banks. The banks being located as visual or as median of the maximum water levels of all months of the year. Most common tag is waterway=riverbank with alternative natural=water and water=* gaining popularity.
Temporary dry waterways are most commonly tagged as intermittent=yes.

Add facilties as waterway=dock and waterway=boatyard.

Add smaller size barriers. Map the riverbeds and islands with natural=* (don't overlap !). Add additional optional tags as usage=irrigation.

Issues with current mapping guideline

• Decide on the tagging scheme to map extend of rivers: waterway=riverbank vs natural=water and water=river
• Inconsistent mapping and tagging of large bodies. Especially natural=water water=reservoir and water levels. For water varying water levels and flooding hazards see #Water bodies with varying levels / resolve inconsistencies in irrigation systems and reservoirs

Ongoing activities

1. What do we have, general State of the Map UG, is the data consistent ? --04-05-2021--Bert Araali (on osm)

Statistics

#top

Administrative Boundaries & Places

Administrative Boundaries & Places
Boundaries for the different administrative areas in Uganda and place names
 High   Medium   Low  

Current mapping guideline

Map as and/or . Tag with their type place=* and name=*. The relations are tagged with boundary=*, boundary=administrative, see also Key:boundary#Boundary_types and Boundaries. Add administrative level with admin_level=* according Tag:boundary=administrative.

The country, regions and districts are mapped as . Lower levels like counties, sub-counties and parishes (municipalities), villages (zones and wards), suburbs etc... are not mapped as boundaries but mostly as nodes. Other large features like nature parks boundary=national_park and boundary=protected_area protect_class=1a or :protect_class=2, wildlife reserves boundary=protected_area protect_class=1b, forest reserves boundary=protected_area protect_class=6 are identified with relations. See also Tag:boundary=protected_area.

Map counties, sub-counties, parishes, villages as boundaries.

Additional data is added like population and household numbers.

Issues with current mapping guideline

• Not all admin levels have separate level in UG.
• Boundary mapping with relations largely unknown. Training needed.
• No qualification for place types like villages as urban - rural - trading center.
• is_in:country remains from old imports, other is_in not used consistently, addr:=* and note=* is used instead but inconsistently
• No links to wikidata or wikipedia. The links are there but incomplete and even the list of districts on Wikipedia is not complete and hardly maintained.
• Insufficient data sources for current situation, missing boundaries up to district level.
• IUCN levels not defined in UG (specifically problem with protect_class=* 1a / 2).
• Large areas incorrectly mapped as multipolygons (forst reserves)
• Global page Tag:boundary=administrative does not describe all administrative boundary types in Uganda. There is no level assigned for Divisions in Kampala (assumed = sub-county = 8), city council is on district level (4) where wikipedia [1] aligns it to county level (6). Municipalities are mapped as level (9), parishes, where wikipedia puts them on level 6 as counties. Sub-regions are not mapped or listed (UBOS 12/05/2020 on UNHCR).
• Constituencies which are not counties have no separate level.
• Other areas often distinguished in the country census, like Peace and Recovery Development Plan (PRDP) districts and Hard-to-reach areas are not mapped. ([2])
• Admin boundaries for other purposes like, cultural (kingdoms), health boundary=health, religious (diocese) are not mapped and no global tagging schemes exist.

Ongoing activities

1. What do we have, general State of the Map UG, is the data consistent ? --29-04-2021--Bert Araali (on osm)

Statistics

Date	Country (2)	Region (3)	District City Council (4)	County Constituencies (6)	Sub-county Division (8)	Parish Municipality[9)	Village Ward Zone(10)
2011 Official UBOS 2011 on Human Rights Focus	na	na	113	47	960	4675	43999
01/08/2014 Official 2014 Census	1	3	116	200	1378	6495
24/07/2019 Official UBOS Admin Units in UG	1	4	122	296	1460	7467
01/01/2021 Official Electoral commission Electoral commission statistics	1	4	146	353	2184	10595	70626
30/04/2021 OSM count	1	3	110	11	62	50	place=*14312 304

To retrieve statistics we use various overpass turbo (overpass-turbo.eu) queries.

---

Help and training material on the usage of overpass turbo can be found on its wiki page: overpass turbo -wiki page-

---

overpass turbo query for general statistics (link: Administrative boundary counts in Uganda Counts only). change the admin_level to the level you want to count: 2=country, 3=region, 4=district, 6=county, 8=sub-county, 9=parish (municipality), 10=village (ward or zone):

 /*
 This query looks for administrative boundary relations.
 */
 [out:json][timeout:250];
 {{geocodeArea:"Uganda"}}->.uganda;
 // gather results
 (
  // query part for: “highway=*”
  relation["boundary"="administrative"] ["admin_level"="2"](area.uganda);
 );
 // print results
 (._;>;);
 out count;

overpass turbo query for individual nodes defined as place=*(link: Place counts in Uganda counts, data and map):

 /*
 This query looks for all nodes defined as places in Uganda.
 */
 [out:json][timeout:250];
 {{geocodeArea:"Uganda"}}->.uganda;
 // gather results
 (
  // query part for: “highway=*”
  node["place"](area.uganda);
 );
 // print results
 (._;>;);
 out count;
 /*
 (._;>;);
 out body;
 >;
 (._;>;);
 out skel qt;
 */

#top