Skip to main content

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

London Borough of Lewisham

Article 4 direction area

There is a problem

  • 78 issue of type invalid category value

Worsley Bridge Road LSIS

reference
Wor1
name
Worsley Bridge Road LSIS
article-4-direction
permitted-development-rights

undefined

Class e
uprns
address-texts
geometry
MULTIPOLYGON (((-0.031928 51.424841,-0.031953 51.424962,-0.031982 51.425085,-0.032011 51.425226,-0.032032 51.425234,-0.032051 51.425323,-0.032058 51.425328,-0.032100 51.425522,-0.032111 51.425582,-0.032162 51.425831,-0.032190 51.425979,-0.032248 51.426264,-0.032276 51.426393,-0.032302 51.426538,-0.032321 51.426631,-0.032337 51.426734,-0.032439 51.426714,-0.032603 51.426734,-0.032737 51.426735,-0.032881 51.426098,-0.032854 51.426095,-0.032903 51.425883,-0.032902 51.425881,-0.032905 51.425871,-0.032907 51.425844,-0.032907 51.425818,-0.032912 51.425801,-0.032993 51.425658,-0.032999 51.425632,-0.033000 51.425585,-0.033065 51.425306,-0.033134 51.424988,-0.033152 51.424921,-0.033079 51.424932,-0.033058 51.424831,-0.032913 51.424815,-0.032855 51.424746,-0.032601 51.424753,-0.032603 51.424780,-0.032155 51.424809,-0.032150 51.424764,-0.032076 51.424765,-0.032046 51.424767,-0.032019 51.424775,-0.031985 51.424790,-0.031974 51.424797,-0.031967 51.424804,-0.031963 51.424813,-0.031958 51.424836,-0.031928 51.424841)))
point
POINT (-0.032543 51.42559)
notes
entry-date
2026-02-25
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 London Borough of Lewisham’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