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

Add support for geo coordinates and geopoints to website #41

Open
amoeba opened this issue May 22, 2018 · 4 comments
Open

Add support for geo coordinates and geopoints to website #41

amoeba opened this issue May 22, 2018 · 4 comments
Assignees
Milestone

Comments

@amoeba
Copy link
Collaborator

amoeba commented May 22, 2018

No description provided.

@amoeba
Copy link
Collaborator Author

amoeba commented May 24, 2018

The task here is to expand jsonld_to_mustache with more functions like this:

https://github.com/ropenscilabs/dataspice/blob/341ae3b259cd9292f4a8c51e280cf3059078f174/R/jsonld_to_mustache.R#L23-L28

@amoeba
Copy link
Collaborator Author

amoeba commented May 24, 2018

Plus: What other spatial stuff should we easily support? wkt?

@khondula
Copy link
Contributor

geojson?
kml/kmz?
Named locations?

For support here, do you mean for creating json and map display, or for extracting from data with prep functions to get the coverage info in the first place? Would be nice to be able to "prep_spatialcoverage" from a geotiff, sf, or spatial*dataframes object...

@amoeba amoeba changed the title Add support for geo coordinates and geopoints Add support for geo coordinates and geopoints in website May 24, 2018
@amoeba amoeba changed the title Add support for geo coordinates and geopoints in website Add support for geo coordinates and geopoints to website May 24, 2018
@amoeba
Copy link
Collaborator Author

amoeba commented May 24, 2018

Good question -- I wasn't clear! The specific part of this Issue is what we support display for, which is dependent on what's serialized from write_spice(). I renamed the Issue to reflect the much more narrow scope. At this point I was just thinking of supporting points and polygons.

I think your idea about helping the user import spatial coverage information from geojson/kml/etc makes a ton of sense. If we don't already have that penciled out we should.

@amoeba amoeba added this to the v1.1 milestone Jul 21, 2020
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

2 participants