# Spatial features

**URL:** <https://talk.observablehq.com/t/spatial-features/7998>\
**Category:** Feedback\
**Created:** [June 2, 2023, 10:33am UTC](https://talk.observablehq.com/t/spatial-features/7998 "2023-06-02T10:33:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![neocarto](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/neocarto/32/6554_2.png) [@neocarto](https://talk.observablehq.com/u/neocarto)\
**Post date:** [June 2, 2023, 10:33am UTC](https://talk.observablehq.com/t/spatial-features/7998/1 "2023-06-02T10:33:51Z")

</div>

Just a general thought about the management of geographic objects in Observable. What about if data tables could directly handle geojson by displaying properties + a geometry column? And what about adding turf.js to the libraries directly integrated into Observable? And more generally, are there any developments underway to take better account of spatial features natively ?

---

<div class="post-metadata">

**Author:** ![tophtucker](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/tophtucker/32/4781_2.png) [@tophtucker](https://talk.observablehq.com/u/tophtucker)\
**Post date:** [June 13, 2023, 1:41am UTC](https://talk.observablehq.com/t/spatial-features/7998/2 "2023-06-13T01:41:19Z")

</div>

Thanks for this! It’s a good question. There was some investigation last year into providing a GeoJSON inspector that toggled between a map preview and the object tree inspector, but it was tricky. One thing that came out of that is offering Plot and Leaflet suggestions below cells with GeoJSON, which create new cells that renders the GeoJSON:

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/observablehq/original/2X/a/a88753c91cae6749ca0f8a1c9cb634ac9090185a.png)

> What about if data tables could directly handle geojson by displaying properties + a geometry column?

I took a stab at something like this — is this akin to what you had in mind…? (I know you were asking about data table cells, but maybe we can get closer today with Inputs.table.)

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/observablehq/original/2X/9/9b68885b419bb6375e362c7a8e909b18145e6af8.png)

> **[GeoJSON table](https://observablehq.com/@tophtucker/geojson-table)**
>
> In the forum, neocarto asks: Just a general thought about the management of geographic objects in Observable. What about if data tables could directly handle geojson by displaying properties + a geometry column? And what about adding turf.js to the...