Jurisdiction & register status
The Phase 4 reconciliation found the proclaimed-township polygon wholly within both the MDB 2026 and live COJ municipal boundaries, with a 100% Region F intersection. The live City locality services do not publish a release date.
Local orientation
The City's proclaimed-township layer identifies Glenanda as T0IR0274000. The Phase 4 register independently matched the core township geometry and cross-checked the City's hosted consolidated-suburb record and historical Census 2011 subplace.
The different source polygons are evidence about locality identity and jurisdiction, not proof that all properties share one land use or development control. Census evidence is historical and is not presented as a current profile of residents or housing.
For planning work, Glenanda is the locality guide; the registered erf, portion and any extension on the title deed and SG diagram are the property identifiers needed for the actual assessment.
Before an application or design
Practical property checks
Erf and extension
Confirm the full registered description. A postal suburb name is not enough to match zoning, amendments, title conditions or a building plan to the correct property.
Rights before design
Check primary and consent uses, density, minimum requirements, coverage, floor area, height, building lines and parking under the operative scheme and any amendment scheme.
Boundaries and buildings
Use an up-to-date SG diagram and title deed to check servitudes and restrictions. Measure existing and proposed structures before assuming that an addition fits behind a building line.
Plans and services
Confirm approved-plan history where available and assess water, sewer, electricity, access and drainage implications for the actual additional use or development.
No suburb-wide zoning, density, minimum stand size or building line is assumed. Read the canonical development-rights checklist and the official resource register for the actual erf, then use the application finder to organise the indicated procedure.
Planning considerations in Glenanda
Second dwellings and backyard rooms
The correct route depends on the erf's zone, density, title and proposal. A subsidiary dwelling, additional dwelling and informal rooms are not interchangeable labels; building-plan requirements remain separate.
Subdivision
Do not infer subdivision potential from erf dimensions alone. Test applicable density and minimum requirements, workable access, services, title and the survey and registration path.
Extensions and building lines
A garage, carport or room addition needs an accurate site plan and the applicable building-line and coverage controls. Neighbour input does not replace the correct municipal procedure.
Relevant services
Choose the closest starting point. We will confirm the procedure only after checking the property and proposal.
Second Dwellings & Backyard Units
Add a cottage, granny flat or rental unit lawfully.
Subdivision
Split one erf or holding into two or more portions with their own title.
Building Line Relaxation
Build closer to the boundary than the scheme allows.
Zoning Certificates
Confirm what your property is zoned for under the Johannesburg scheme.
Glenanda planning FAQs
Is Glenanda verified within Johannesburg?
Yes. Its proclaimed-township polygon was contained by both the MDB 2026 and live COJ municipal boundaries in the 13 November 2026 reconciliation, and its verified regional intersection is Region F.
Can I add a second dwelling in Glenanda?
It depends on the actual erf. Check its zone, dwelling and density controls, title, coverage, building lines, parking and services, then identify whether plans alone, written consent, consent use or rezoning is the lawful route.
Are Glenanda building lines or minimum stand sizes standard?
No single Glenanda-wide figure is stated here. Read the erf's use zone, amendment scheme and approval conditions; title and site constraints can add further limits.
Official municipal & source links
Locality and source review: 13 November 2026. Live GIS access dates are not presented as dataset release dates.