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

GNIP - Upload/Download directly from GeoNode #1421

Closed
ingenieroariel opened this issue Apr 14, 2014 · 5 comments
Closed

GNIP - Upload/Download directly from GeoNode #1421

ingenieroariel opened this issue Apr 14, 2014 · 5 comments
Labels
gnip A GeoNodeImprovementProcess Issue
Milestone

Comments

@ingenieroariel
Copy link
Member

Allow people to download the file that was uploaded with NO modifications.

Potential Problems

What to do about layers that are modified after creation.

@capooti
Copy link
Member

capooti commented Apr 16, 2014

+1 here for me.
But for our use case we should provide the latest version of the datasets, that could be different from the original dataset if for example dataset was edited.
I think we should provide a basic download service implementation, giving the data owner the possibility to define which formats/projections and eventually subdatasets to provide for download.
The datasets to be downloaded could be generated by an asynchronous process on the server with GDAL.

@jj0hns0n
Copy link
Contributor

Punting to 2.5?

@jj0hns0n jj0hns0n added this to the 2.5.x milestone Jan 13, 2015
@jj0hns0n jj0hns0n added feature A new feature to be added to the codebase and removed needs-triage labels Jan 13, 2015
@capooti
Copy link
Member

capooti commented Jan 17, 2015

Also, let's make sure to avoid any duplication with https://github.com/GeoNode/geonode/wiki/GNIP-47--Predefined-Download-Service

@JJediny
Copy link
Member

JJediny commented Jan 24, 2015

-1 for vector data
+1 for raster data

While geoserver takes a hit the reality is traffic/demand is rarely an issue, and if a production geonode is seeing heavy use, taking the normal steps to scale the site (via clustering / DB isolation) will meet the demand. Shouldn't break or complicate what already works, for raster I agree that automating a download service for original raster file is needed. Maybe just mod apache to access upload dir as a static file to download and register direct link to override current WCS link to geoserver. Lastly seems like version control is also baked into this ticket, feel like if that is an issue for a project they would consider integrating GeoGig (feature-based versioning) over a (file-based) versioning system within django.

@jj0hns0n jj0hns0n modified the milestones: 2.7, 2.5 Aug 21, 2016
@jondoig
Copy link
Contributor

jondoig commented Feb 9, 2017

You can already do this without even logging in. Even on private data. See #2896 😮

@afabiani afabiani removed the feature A new feature to be added to the codebase label Aug 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gnip A GeoNodeImprovementProcess Issue
Projects
None yet
Development

No branches or pull requests

6 participants