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

readData.geojson, readData.topojson #346

Open
aappling-usgs opened this issue Mar 14, 2018 · 0 comments
Open

readData.geojson, readData.topojson #346

aappling-usgs opened this issue Mar 14, 2018 · 0 comments

Comments

@aappling-usgs
Copy link
Member

These file types can be read in as json, but the resulting format isn't ideal. These proposed readData functions could read data in as sp or sf objects. Of course, we'll need to decide which of those formats we want, and whether it's worth it for vizlab to make that decision on behalf of all vizzies.

I have mixed feelings about readData generally, which the above decision point raises again: are we really saving ourselves time or complexity when we force/strongly encourage the user to adopt vizlab's decisions about how and when to read data? It's not a baaad approach, just saying there are pros and cons.

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

1 participant