Skip to main content

This is a new service – your feedback will help us to improve it.

Fareham Borough Council

Article 4 direction area

There is a problem

  • 19 issue of type invalid category value

Swanwick Shore

reference
010 - Schedule 3
name
Swanwick Shore
article-4-direction
permitted-development-rights

undefined

Permitted development right codes withdrawn by the article 4 - TBD
uprns
address-texts
geometry
MULTIPOLYGON (((-1.296054 50.879922,-1.295832 50.879975,-1.295889 50.880098,-1.295882 50.880107,-1.295971 50.880303,-1.296015 50.880288,-1.296099 50.880275,-1.296387 50.880266,-1.296433 50.880247,-1.296460 50.880210,-1.296473 50.880207,-1.296425 50.880139,-1.296274 50.879870,-1.296054 50.879922)),((-1.296387 50.879976,-1.296514 50.880196,-1.296653 50.880148,-1.296655 50.880139,-1.296563 50.880029,-1.296517 50.879961,-1.296450 50.879970,-1.296395 50.879843,-1.296341 50.879857,-1.296387 50.879976)),((-1.296801 50.881429,-1.297102 50.881345,-1.297246 50.881279,-1.297262 50.881244,-1.297260 50.881230,-1.297180 50.881099,-1.296984 50.881141,-1.296991 50.881152,-1.296980 50.881145,-1.296958 50.881150,-1.296963 50.881158,-1.296922 50.881168,-1.296915 50.881157,-1.296845 50.881173,-1.296852 50.881185,-1.296809 50.881188,-1.296812 50.881194,-1.296721 50.881216,-1.296709 50.881195,-1.296665 50.881205,-1.296801 50.881429)))
point
POINT (-1.29647 50.880486)
notes
entry-date
2026-05-19
start-date
end-date

How to fix this issue

Your data is missing a permitted-development-rights.

The Article 4 direction area guidance explains how to fix the issue:

permitted-development-rights

A list of the permitted development rights withdrawn by the article 4 direction.

Separate the rights in the list using semicolons.

Only use rights from our permitted development right dataset. If the area withdraws a permitted development right that is not in our dataset, email digitalland@communities.gov.uk.

Example: 3D;3M;11B

How to improve Fareham Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL