The upload workflow, as described in a meeting 5-18-09.
- If you are logged in, then you can upload (the upload UI element is visible, or not disabled, or something. See wireframe.)
- Select a file (shapefile or geotiff) to upload in some dialogue.
- What if it is not a shapefile?
- Click "Upload" button
- A REST API call is made to GeoServer to submit the shapefile or geotiff. It will check the cookie to figure out which user is active.
- GeoServer returns a resource from which you can get the layer to display it in the browser.
- Display the layer and begin the Styling story
- What's the base layer here?
- How different is this context from from "default" one where you view a map?
- The layer begins with a default style, set for all layers in GeoServer.
- Styling allows those options from Styler. (They need to be integrated in). The user can work from the default style to whatever style they can make.
- When the style is ready, as REST call is made to submit the SLD.
- That is now the style for that layer.
- Where does the user get directed to from there?
There are some related features that haven't been mentioned here. We need to ask about these (but since they haven't been listed in this story so far, I don't think we should estimate them immediately.)
- What happens if a user doesn't like the layer's style and wants to edit it?
- Can the user delete a layer they have uploaded? If so, how?
In the process of roadmapping and estimation we should figure out what other features are missing from here.
