About the directory

How we map streets

Evidence behind every mapped section

Identity and scope

Source objects keep their source, layer, type and native identifiers. Logical streets are resolved from names and topological evidence; disconnected names remain separate unless supported by evidence.

Geometry and measurements

Outlines use the actual OpenStreetMap geometry. Distances use a suitable metric calculation, never untransformed degrees. Mapped geometry length describes the represented lines and is not a guarantee of the physical length of a street.

Connections and nearby streets

Connections require shared source nodes and compatible topological levels. Nearby streets use geometric distance to the mapped section, not walking distance or a route recommendation.

Administrative context

Navigation hubs describe documented coverage areas. A city label is not automatically a legal municipal boundary. A locality needs geographic evidence; a point label alone does not create a suburb polygon.

Postal evidence

Street delivery, PO Box and Private Bag are separate. An official assignment needs a verified postal authority and permitted source. Multisource verification needs independent, agreeing evidence for the same street scope and delivery type. Inferred values are not displayed as assignments; conflicting or insufficient evidence remains unknown. A code on a nearby address cannot establish a whole-street code.

Evidence states

Observed facts reproduce source objects. Calculated facts use recorded inputs and a stated method. Inferred values remain distinct and are not presented as verified assignments. Officially verified means an authorised independent source corroborates the exact claim; no municipal or postal claim currently has that status.

Identity review and related streets

Names are compared using Unicode case folding and whitespace normalisation, without expanding abbreviations or removing accents. Street components can join only with a shared source node at a compatible level and the same name and city. Disconnected names stay under review. Related names appear once, with separate section links; nearby and connected sections are shown in their respective blocks even when their names match.

Publication quality

Publication review checks identity, valid geometry, clear geographic scope, rights and the usefulness of locating and understanding the street. Short streets, a single source way and few nearby places do not lower eligibility. Missing optional postal or municipal evidence does not block otherwise useful pages. Sections with unresolved identity or misleading duplicates are not published until that review is complete.

Nearby places and transport

Named OpenStreetMap point objects are matched to the nearest part of the mapped street geometry using the appropriate South African UTM zone. Services use a 500 m buffer and transport points a 1 km buffer. Distances are straight-line gaps, rounded for display, not walking routes or journey times. Only named points are counted; unnamed features and places mapped only as areas or relations are outside this layer. A missing category is not evidence of no local service.

Counts and examples

Category totals count all named point records in the stated radius. Highlights prefer everyday service types and subtype variety, then proximity; these are not rankings. Sensitive retail tags are excluded from highlights but remain in the expandable full inventory and counts, identically for all readers. Gyms and sports facilities are separate from parks and green spaces. Transport highlights show passenger stop/platform/station records; vehicle stop positions remain in technical details. Source stop-area relations associate components when recorded, without treating opposite-side stops as one boarding point. These records do not establish unique operational stations or service frequency. Closed, proposed, disused and explicitly private records are excluded where identified in the source. Names and current operation are not independently verified.

Road characteristics

Road tags apply to individual mapped segments. Segment counts remain in technical details. Length coverage measures the source line length carrying a tag, not the proportion of a street certified to have that facility. Pavement absence, unknown data and separately mapped pavements are distinct. Left and right refer to the direction of each source way, not a single orientation for the whole street. Missing tags remain unknown. One-way direction follows the source geometry; mapped speed values are historical map records, not live traffic guidance. Numeric maxspeed tags use km/h according to the OSM convention.

Street descriptions

Summaries and questions are assembled from the same recorded facts shown in the modules. No quality-of-life score, safety assessment, property valuation, demographic profile or walking time is inferred from nearby amenities.

Author, data sources & methodology

Edited by Yoel Castaño Peón for Callejear South Africa. Methodology · Sources & licences.

Map and geographic data © OpenStreetMap contributors, available under the Open Database Licence (ODbL). Extracts provided by Geofabrik.