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
351 74/95 CAMPDEN HILL SQUARE

Unexpected geom type

2025-01-03
352 04-Feb CAMPDEN HOUSE CLOSE

Unexpected geom type

2025-01-03
353 K58 CAMPDEN STREET

Unexpected geom type

2025-01-03
354 K44 CANNING PLACE

Unexpected geom type

2025-01-03
355 Oct-72 CANNING PLACE

Unexpected geom type

2025-01-03
356 K44 CANNING PLACE

Unexpected geom type

2025-01-03
357 K44 CANNING PLACE

Unexpected geom type

2025-01-03
358 C10 CARLYLE SQUARE

Unexpected geom type

2025-01-03
359 C10 CARLYLE SQUARE

Unexpected geom type

2025-01-03
360 C12 CARLYLE SQUARE

Unexpected geom type

2025-01-03
361 C12 CARLYLE SQUARE

Unexpected geom type

2025-01-03
362 C12 CARLYLE SQUARE

Unexpected geom type

2025-01-03
363 C12 CARLYLE SQUARE

Unexpected geom type

2025-01-03
364 14/96 CARLYLE SQUARE

Unexpected geom type

2025-01-03
365 C12 CARLYLE SQUARE

Unexpected geom type

2025-01-03
366 C12 CARLYLE SQUARE

Unexpected geom type

2025-01-03
367 C12 CARLYLE SQUARE

Unexpected geom type

2025-01-03
368 C12 CARLYLE SQUARE

Unexpected geom type

2025-01-03
369 C12 CARLYLE SQUARE

Unexpected geom type

2025-01-03
370 C12 CARLYLE SQUARE

Unexpected geom type

2025-01-03
371 C12 CARLYLE SQUARE

Unexpected geom type

2025-01-03
372 Mar-74 CARLYLE SQUARE

Unexpected geom type

2025-01-03
373 Mar-74 CARLYLE SQUARE

Unexpected geom type

2025-01-03
374 Mar-74 CARLYLE SQUARE

Unexpected geom type

2025-01-03
375 Mar-74 CARLYLE SQUARE

Unexpected geom type

2025-01-03
376 Mar-74 CARLYLE SQUARE

Unexpected geom type

2025-01-03
377 Mar-74 CARLYLE SQUARE

Unexpected geom type

2025-01-03
378 Mar-74 CARLYLE SQUARE

Unexpected geom type

2025-01-03
379 Oct-88 CARLYLE SQUARE

Unexpected geom type

2025-01-03
380 21/75 CATHCART ROAD

Unexpected geom type

2025-01-03
381 21/75 CATHCART ROAD

Unexpected geom type

2025-01-03
382 22/75 CATHCART ROAD

Unexpected geom type

2025-01-03
383 22/75 CATHCART ROAD

Unexpected geom type

2025-01-03
384 15/92 CATHCART ROAD

Unexpected geom type

2025-01-03
385 Apr-85 CAVERSHAM STREET

Unexpected geom type

2025-01-03
386 Dec-89 CHELSEA MANOR STREET

Unexpected geom type

2025-01-03
387 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
388 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
389 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
390 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
391 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
392 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
393 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
394 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
395 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
396 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
397 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
398 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
399 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03
400 22/74 CHELSEA PARK GARDENS

Unexpected geom type

2025-01-03

Showing rows 351 to 400 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