Closed ischneider closed 11 years ago
Go ahead and merge the patch (and forward port to master please).
Regarding a better/cleaner way of doing this what is the goal here? To have the final layer name be human readable? Or to have the directory on disk human readable? Or both?
On 03/21/2013 12:18 PM, Justin Deoliveira wrote:
Go ahead and merge the patch (and forward port to master please).
Cool. Will do.
Regarding a better/cleaner way of doing this what is the goal here? To have the final layer name be human readable? Or to have the directory on disk human readable? Or both?
Primarily the layer name but both would be ideal (as tracking down an opaque name is annoying). I played with other ways to get this done but just wanted to move forward.
Regarding a better/cleaner way of doing this what is the goal here? To have the final layer name be human readable? Or to have the directory on disk human readable? Or both?
Primarily the layer name but both would be ideal (as tracking down an opaque name is annoying). I played with other ways to get this done but just wanted to move forward.
Cool. So if we don't care about the directory name then one way would just be to edit the layer name on the item being processed. Another thing would be to just simply allow the "file" property of the data object to be relative. And process it is relative to the upload root.
— Reply to this email directly or view it on GitHubhttps://github.com/opengeo/geoserver-exts/pull/10#issuecomment-15256539 .
Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial.
Hacky way to force a Directory/Mosaic name from the client. Without this, when uploading a zip of rasters, the name will end up being a temp file name.
Not sure if it makes sense to do this in a better way except considering the functionality in the refactor.