Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KB article that shows how to import GeoJSON with a deeply nested object array. #2926

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

linhgiang24
Copy link
Contributor

Summary

This KB article walks through an example of importing GeoJSON with a deeply nested object array.

Copy link
Member

@SpencerTorres SpencerTorres left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for writing this, glad to see more content related to Geo data. I've added a couple notes

How do I import GeoJSON with a nested object array?

### Answer
For this tutorial, we will use open data publicly available [here](https://opendata.esri.es/datasets/ComunidadSIG::municipios-ign/explore?location=39.536006%2C-0.303882%2C6.57).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this link expire or change? It looks very specific, perhaps we could recommend they go to a specific website rather than this exact location URL.

│ MultiPolygon │
└──────────────────────┘
```

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In addition to the count() query, it may be good to demo something complex to show the analytical power of geo data in ClickHouse. Perhaps something that filters on one of the many columns? We also have some functions for measuring distance, but I don't think they can be easily applied to the polygon data

@linhgiang24
Copy link
Contributor Author

@SpencerTorres One of the questions we have is whether this KB is still relevant since we have the JSON data type now. @allegrinisante is the author of the KB and is looking to review and possibly adapt it to the new capabilities. But was just wondering what your thoughts are.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants