The High/Low Water Consumption solution allows a utility to query and view customers with above and below average water usage. To maintain a current view of these customers, a Python script is scheduled to update the services, maps, and dashboard. Additionally, a record of above and below average consumption can be stored in your ArcGIS organization.


High/Low Water Consumption requires specific technical experience and software.

Requirement Description
  • Scheduling Windows tasks
  • Modifying JSON files
  • Publishing GIS services
  • Authoring maps
  • Administering groups and organizing content in an ArcGIS organization
Data Publishing
  • ArcMap (Standard or Advanced) 10.2.1, 10.3, 10.4
  • Python 2.7.x
  • Windows Task Scheduler
Map authoring
  • ArcMap (Standard or Advanced) 10.2.1, 10.3, 10.4
Map Service Hosting
  • ArcGIS Online
  • ArcGIS Enterprise (Standard or Advanced) 10.5
  • ArcGIS for Server (Standard or Advanced) 10.3, 10.4
    • Portal for ArcGIS
Application hosting
  • ArcGIS Enterprise 10.5
  • Portal for ArcGIS 10.4
  • ArcGIS Online
Applications Operations Dashboard for ArcGIS

What you get

When you download High/Low Water Consumption, you'll find the following in the zip file:

Directory Item Description
Application A set of Python 2.7 scripts to create and update the required services, maps, and apps in your organization. These scripts utilize the Automated Setup & Reporting tools.
Maps and GDBs Consumption.gdb The geodatabase contains the water consumption schema and sample data.
ConsumptionData The CSV file with water consumption schema and sample data.
HighWaterConsumption.mxd The ArcMap document with sample cartography used to publish the high water consumption service.
LowWaterConsumption.mxd The ArcMap document with sample cartography used to publish the low water consumption service.

What's new

Below are the release dates and notes for High/Low Water Consumption.

Date Description
February 2016
August 2015
  • Latest versions of the ArcREST tools
    • ArcREST version 3
  • Config file enhancements
May 2015
  • Latest versions of the ArcREST tools
    • ArcREST Helper is now included with ArcREST
  • Report modules moved to solutionreporttools python package
  • Config file schema changes
    • ReportingAreas and ReportingAreasIDField moved to ReportDetails section
    • PublishData added to PublishingDetails section to allow the user to quickly bypass this entire section
    • EnableEditTracking & Capabilities parameters in FeatureServices has been replaced with the Definition section
    • RunReport added to ReportDetails section to allow the user to quickly bypass this entire section
    • Data added to ReportDetails to centrally define the data layers
    • Data parameter in each report now uses a value from the RunReports Data section instead of path to data
    • CSVOutputLocation added to ReportDetails to allow a merged CSV file result from selected reports
    • ExportDataLocally added to ReportDetails to copy the data from the data section to a local GDB before running the reports
    • TempExportLocation added to ReportDetails. Specify the path to a File GDB when you set ExportDataLocally to True
    • SchemaGDB & ResultsGDB sections added to ReportDetails to remove the redundant list of database in each report
    • ReportResultSchema & ReportResult in each report section list the layer location in the database defined in SchemaGDB and ResultGDB
    • ReportMerge added to each report to append results after each run instead of overwriting output
December 2014
  • Latest versions of the ArcREST and ArcREST Helper tools
  • Config files schema changes
    • FeatureService section to FeatureServices
    • Login info only defined in the GlobalLoginInfo file
    • EnableEditTracking parameter added to FeatureServices section
    • UpdateItemContent changes to UpdateService in MapDetails
    • Portal in login section changed to Orgurl
    • ExistingService change to ExistingServices
    • ExistingServices ReportResult tag changes to FeatureClass
    • ReplaceTag added to section
    • ReplaceInfo Section now uses the following three parameters, SearchString, ReplaceString and ReplaceType
September 2014
  • First release of High/Low Water Consumption

Known issues

  • This solution uses the Intersect geoprocessing tool. If you have line features in the same layer that overlap (for example, in a 3d view the line would look like a "Z") and using a field other than Shape Length for reporting, the results will be incorrect.
  • If you are using a field other than Shape Length to calculate a report summary and your data is being split by your reporting district, the results will be incorrect as this field is not being adjusted by the percentage that record falls into the reporting zone.
  • The automated setup utilizes ArcREST, which does not support application and enterprise logins.
  • When publishing to Portal for ArcGIS, the Hosting Server must use an ArcGIS Data Store as a managed geodatabase.
  • When publishing to Portal for ArcGIS with an ArcGIS Data Store Hosting Server, field names will be auto converted to lowercase. The tools will update the maps created, but apps are not updated to handle this conversion.
  • The script is delivered using relative paths. To use this without changing to absolute paths, you need to have python.exe as the default file extension for .py files and the path to Python in your systems path variable.

Get started with High/Low Water Consumption.

Solution Report Tools preview release

The next release of the Solution Report tools solves the known issues relating to Intersect and the Shape Length field. A preview of this next release is available on GeoNet.