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

Should GI.FeatureCollection subscribe to the Tables interface? #155

Open
asinghvi17 opened this issue Sep 19, 2024 · 2 comments
Open

Should GI.FeatureCollection subscribe to the Tables interface? #155

asinghvi17 opened this issue Sep 19, 2024 · 2 comments

Comments

@asinghvi17
Copy link
Member

That would make DataFrame(fc) work, which would be incredibly convenient. We currently don't have that so it's very difficult to tell beginner users how to use a GI feature collection.

@rafaqz
Copy link
Member

rafaqz commented Sep 19, 2024

Yes, but maybe Tables.jl should be an extension?

One problem is there is no need to supply all fields in all rows so you have to read the whole thing to get the columns.

We can maybe move my code for that from GeoJSON.jl to here.

@evetion
Copy link
Member

evetion commented Sep 19, 2024

+1 For extension, as soon as you load DataFrames that will trigger.

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

No branches or pull requests

3 participants