Well Permit Action History URL Generator

This URL Generator generates the URL from selected model dataset fields.

Argument Key Description Operator/Value
Format for returned data. Default=json
Forces encoding of response using "gzip" or "deflate" encoding to cut down on network response size. Leave blank to let the response headers manage the encoding.
Used to format all date fields in the returned data. This formatting is done after filtering.











Which fields to return, if you only want specific fields. Leave blank to return all fields.
Action date
Operator:

Type of date :
Date:
Time:
Enter desired date/time modifiers. Negative sign means backward from time of request
Years:
Months:
Weeks:
Days:
Hours:
Minutes:
Seconds:

To choose a range of dates, select "After" above and enter a "Before" date below


Type of date :

End Date:
End Time:
Enter desired date/time modifiers. Negative sign means backward from time of request
Years:
Months:
Weeks:
Days:
Hours:
Minutes:
Seconds:
Action name
Operator:
Text:
County where the well is located
Operator:
Text:
Eight established geographic areas in Colorado's Eastern Plains where users rely primarily on groundwater for water supply
Operator:
Text:
DWR Water Division
Operator:
Number:

To create a range of numbers, select 'Greater Than' above and enter a "Less Than" value below:
Thirteen local districts, within the Designated Basins, with additional administrative authority
Operator:
Text:
Permit application receipt number
Operator:
Text:
DWR Water District
Operator:
Number:

To create a range of numbers, select 'Greater Than' above and enter a "Less Than" value below:
Location search by latitude/longitude
Can search a radius of up to 150 miles, but smaller values will be much more efficient		 Latitude :
Longitude :
Radius:
Units:
Maximum number of rows to return (or up to remaining user available rows for the day, whichever is less). Default page size = 50,000 Max page size = 500,000 Page size:
If a page size is included and page size is less than the number of rows the query would have returned, page index can be used to tell the server which rows to return. Default page index = 1. Page index:
The API key to allow more daily returned rows/requests than the default amounts. API key:

CAUTION: Large datasets will slow down or freeze your browser. You should:
  • Make your query as specific as possible
  • Match the 'modified' date to your capture frequency
  • Possibly limit your 'pageSize' (at least to preview data)

URL: