Specifications include, but are not limited to: Project Goals and Objectives The goal of this project is to have a contractor create a freshwater water quality data portal that accesses new freshwater water quality data and assists communities in their efforts to address pond water quality concerns. The contractor will deliver a fully tested, debugged, and functioning web-based portal connected to our hosted data. The Application will be hosted in Azure. The data could come from one or two sources and could be accessed by one or two APIs or spreadsheets. The Contractor will work with the Commission to determine best practices and efficiencies for the application to function optimally. Project objectives include: Development of a new freshwater water quality portal highlighting and displaying water quality data across Cape Cod. The ability for the user to pick the geography of the monitoring sites to be displayed/queried. The ability for the user to visually examine the monitoring locations on a map. The ability for the user to see graphics and/or charts to visualize and ascertain the water quality data and associated analyses of the chosen geography. The application must utilize open-source libraries. The application must access all identified sources of freshwater data. The Commission must be able to maintain the tool. 1. Identify recommended development libraries. The contractor will familiarize themselves with the data, APIs, existing R (analysis) coding, and with GIS REST services, as provided by the Commission. The contractor will develop a list of recommended and alternative libraries for each (or all) of the following application elements: map interface with station display, data and trend analysis view, data filtering and trend computation. Deliverable: List of recommended and alternative development libraries. Timeline: within 1 month of signed contract 2. Recommend, for Commission staff approval, data access path forward. The contractor will familiarize themselves with the two data sources and the best way to access them. Each source has a different data format. The contractor must select and help implement the aggregating of data to one source if keeping the data in one format is more beneficial. For instance, WISKI data could be imported in WQP(X) and accessed solely through the Federal WQP API. Conversely, one or both data sources could also be exported to .csvs, housed in Azure, and be queried by two different statements to synthesize the data for the portal. Deliverable: Final recommendation on best practice for live data access, and implementation of access to data, once path is approved by Commission staff. Timeline: within 1.5 months of signed contract 3. Develop application storyboard. The contractor will review application mock-ups developed and provided by Commission staff. The contractor will develop a final application storyboard for Commission review that includes functionality and needs detailed in Commission mock-ups. Where the contractor identifies needs and/or deviations from proposed mock-ups, the contractor will review and discuss those with Commission staff prior to finalizing the storyboard. The contractor will edit storyboard as needed based on feedback. Deliverable: Application storyboard. Timeline: within 3 months of signed contract
