Priority Features for 1.4.0 / 1.5.0

[swainn]

In preparation for the upcoming Tethys Summit, I thought it would be good to start a discussion on what our priorities for development should be. I've reviewed most of the proposals that have been made on the forum in the last couple of months and I'll list them here, but I'd also like to see what development priorities we have coming from the recently awarded contracts. I will also point out that there are many items on the Tethys Project Road Map / Backlog that are fair game here too.

• MapView Gizmo 2.0 Features
• Add Image Pyramid plugin to GeoServer
• Add "coverageName" parameter to "create_coverage_resource" method of the GeoServer spatial dataset services API.
• Add additional libraries/dependencies to improve the Tethys app development environment (e.g.: gdal, numpy, netCDF4)
• Create a "make" command that can automate frequently performed tasks (like adding a new page to an app which involves creating a controller, template, and url map)
• Add a "visibility" attribute for all gizmos to define their initial visibility and JavaScript endpoints to toggle the visibility
• Implement ESRI integration
• Add a "Layouts" feature -  a layout would essentially be alternative base templates. Examples include: Map Layout, Plot Layout, Two Column Layout, Tile View Layout
• Installation of apps from admin portal / automated app installation /  sandbox portal setup
• Allow overriding the "Exit" button action and text: e.g. Back
• Generalize the JavaScript to allow the Map View  options to instantiate any openlayers object

Other development priorities that fall more in the maintenance category than in the feature category are:

• Python 3.0 support
• Implement testing framework for Tethys and Apps and build out tests
• Update dependencies (e.g.: ensure we are using a secure version of Django)

This by no means complete, please post additional features that you would like to be considered for priority development.

[alansnow21]

Hi Nathan,

All of this looks great!

Just wanted to let you know that this task is already done: "Allow overriding the "Exit" button action and text: e.g. Back"

See: https://github.com/erdc-cm/tethysapp-streamflow_prediction_tool/blob/master/tethysapp/streamflow_prediction_tool/templates/streamflow_prediction_tool/map.html

{% block exit_button_override %}

<div class="exit-button">

<a href="{% url 'streamflow_prediction_tool:home' %}">Back</a>

</div>

{% endblock %}