-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Comments
+1 here for me. |
Punting to 2.5? |
Also, let's make sure to avoid any duplication with https://github.com/GeoNode/geonode/wiki/GNIP-47--Predefined-Download-Service |
-1 for vector 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. |
You can already do this without even logging in. Even on private data. See #2896 😮 |
Allow people to download the file that was uploaded with NO modifications.
Potential Problems
What to do about layers that are modified after creation.
The text was updated successfully, but these errors were encountered: