Skip to main content

Your data has issues

There is a problem

  • geometry column must have valid geometry
Reference Name Tree preservation order Uprn Address text Point Geometry Notes Organisation Felled date Entry date Start date End date
301 K61 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
302 K61 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
303 K61 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
304 K61 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
305 K61 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
306 K61 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
307 K61 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
308 K60 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
309 K60 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
310 K60 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
311 K60 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
312 May-85 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
313 Aug-85 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
314 Aug-85 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
315 Aug-85 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
316 Aug-85 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
317 26/89 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
318 9/00 CAMBRIDGE GARDENS

Unexpected geom type

2025-01-03
319 K45 CAMBRIDGE PLACE

Unexpected geom type

2025-01-03
320 Oct-72 CAMBRIDGE PLACE

Unexpected geom type

2025-01-03
321 K45 CAMBRIDGE PLACE

Unexpected geom type

2025-01-03
322 Aug-72 CAMPDEN GROVE

Unexpected geom type

2025-01-03
323 Aug-72 CAMPDEN GROVE

Unexpected geom type

2025-01-03
324 Aug-72 CAMPDEN GROVE

Unexpected geom type

2025-01-03
325 Aug-72 CAMPDEN GROVE

Unexpected geom type

2025-01-03
326 Aug-72 CAMPDEN GROVE

Unexpected geom type

2025-01-03
327 K57 CAMPDEN HILL

Unexpected geom type

2025-01-03
328 K1 CAMPDEN HILL

Unexpected geom type

2025-01-03
329 16/75 CAMPDEN HILL GARDENS

Unexpected geom type

2025-01-03
330 K57 CAMPDEN HILL PLACE

Unexpected geom type

2025-01-03
331 Apr-73 CAMPDEN HILL PLACE

Unexpected geom type

2025-01-03
332 Feb-72 CAMPDEN HILL ROAD

Unexpected geom type

2025-01-03
333 Jul-72 CAMPDEN HILL ROAD

Unexpected geom type

2025-01-03
334 K56 CAMPDEN HILL ROAD

Unexpected geom type

2025-01-03
335 Jul-72 CAMPDEN HILL ROAD

Unexpected geom type

2025-01-03
336 Jul-72 CAMPDEN HILL ROAD

Unexpected geom type

2025-01-03
337 K56 CAMPDEN HILL ROAD

Unexpected geom type

2025-01-03
338 K58 CAMPDEN HILL ROAD

Unexpected geom type

2025-01-03
339 K58 CAMPDEN HILL ROAD

Unexpected geom type

2025-01-03
340 K58 CAMPDEN HILL ROAD

Unexpected geom type

2025-01-03
341 K58 CAMPDEN HILL ROAD

Unexpected geom type

2025-01-03
342 May-90 CAMPDEN HILL ROAD

Unexpected geom type

2025-01-03
343 Jan-93 CAMPDEN HILL ROAD

Unexpected geom type

2025-01-03
344 May-97 CAMPDEN HILL ROAD

Unexpected geom type

2025-01-03
345 Apr-73 CAMPDEN HILL SQUARE

Unexpected geom type

2025-01-03
346 Apr-73 CAMPDEN HILL SQUARE

Unexpected geom type

2025-01-03
347 K57 CAMPDEN HILL SQUARE

Unexpected geom type

2025-01-03
348 See Aubrey Road CAMPDEN HILL SQUARE

Unexpected geom type

2025-01-03
349 K57 CAMPDEN HILL SQUARE

Unexpected geom type

2025-01-03
350 25/87 CAMPDEN HILL SQUARE

Unexpected geom type

2025-01-03

Showing rows 301 to 350 of 1000

How to fix this issue

Your dataset is missing the geometry column.

The Tree guidance explains how to fix the issue:

geometry

The boundary of the tree as a single polygon or multipolygon value. All points in the polygon must be in the WGS84 coordinate reference system.

If you’re providing geometry in a CSV, geometry should be in well-known text (WKT).

You must provide a point or geometry for each tree. You may provide both.

Example: MULTIPOLYGON (((1.188829 51.23478,1.188376 51.234909,1.188381 51.234917,1.187912 51.235022...

If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associated geometry format.

How to improve Royal Borough of Kensington and Chelsea’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