Upload shape files

[sethlbrown]

Users can upload shapefiles provided to them and generate a report based on them. Users are sometimes provided shape by their advisors. This would be a feature where the user can upload the shapefile and get a cost report based on what was provided to them.

• Users can choose to upload shapefiles by clicking on the plant tree or plant prairies menu item
• Once a shapefile has been uploaded, the blank shape will appear on the map with the edit icon.
• Once the shapefile has finished uploading a modal will appear letting the user know that the upload is complete and that they have to click on the edit button to configure the trees or prairies. The below image illustrating this is a wireframe. Styles are defined in the style guide.
• When the user clicks on the edit icon, it will open the tree or prairie configuration modal.

[johnwildspring]

Proposed approach:

Bypass the draw tool by allowing users to upload shapefiles. Adds config-less shapes to the dataset. Users must add configurations before they can see the report.

Developer comment: This is actually a major feature we worked on at Teralytic. It's more complicated than one expects, because shapefiles come in all shapes and sizes (pun intended). It's a powerful feature worth doing though because it enables ease and scale. Users can upload a dozen shapes at once, that were already drawn using other software.

Dependencies:

• Will need to do some user research and actually get some sample shapefiles that users would upload, to understand their structure.
• If the structure is not consistent (e.g. there is user-specific nesting or structuring of the file), which I assume they won't be, we might need to design some kind of step-by-step upload wizard that lets users explore their shapefiles and pick the specific shapes they want to upload.
• The number of shapes could get out of hand really easily, especially if users upload shapefiles with many shapes in them. They would need a way to track all the shapes uploaded, and which ones they still need to configure. I suggest some kind of list or menu maybe where they can browse all their shapes in one place (it would actually be also useful if users have shapes that are far apart or if they have a large property). I think this need some additional design love.

Estimate hours (incl. dependencies): 160, or about between 2-3 sprints.

Honestly we might have to break this feature up into chunks (each dependency is its own feature).