USGS Data Fetching - Revision history

DaveSanderman at 16:35, 29 May 2025

2025-05-29T16:35:39Z

DaveSanderman at 16:21, 29 May 2025

2025-05-29T16:21:21Z

DaveSanderman at 16:19, 29 May 2025

2025-05-29T16:19:47Z

DaveSanderman at 16:05, 29 May 2025

2025-05-29T16:05:05Z

DaveSanderman: Created page with "== USGS Data Fetching == We use URLs of the following format to fetch USGS data:

 https://waterservices.usgs.gov/nwis/iv/?format=json&indent=on¶meterCd=00060,00065&..."

2025-05-29T15:42:17Z

Created page with "== USGS Data Fetching == We use URLs of the following format to fetch USGS data: <pre> https://waterservices.usgs.gov/nwis/iv/?format=json&indent=on&parameterCd=00060,00065&..."

New page

== USGS Data Fetching ==

We use URLs of the following format to fetch USGS data:

<pre>
https://waterservices.usgs.gov/nwis/iv/?format=json&indent=on&parameterCd=00060,00065&siteStatus=all&sites=12141300&period=PT22M29.5308163S
</pre>

The important pieces of the URL:
* parameterCd=00060,00065 -- This indicates that we want parameters 00060 and 00065, which are water height and discharge
* sites=12141300 -- This is which gauge we want to look at
* period=PT22M29.5308163S -- This is the time range we want to fetch data for; basically it will be an encoded version of "since the last time we asked".

@@ Line 24: / Line 24: @@
 * all the metadata gunk in the response is going away, yay
 * will want to get an API Key to avoid rate-limiting (although 100 requests/hour is probably more than we need)
 ** keys will allow 1000 per hour which is definitely plenty

@@ Line 21: / Line 21: @@
 * URL Base is changing
 * parameter names are changing but the encoding appears to be the same
- * e.g. "period" parameter will still be encoded in "P1D" format
+** e.g. "period" parameter will still be encoded in "P1D" format
 * all the metadata gunk in the response is going away, yay
 * will want to get an API Key to avoid rate-limiting (although 100 requests/hour is probably more than we need)
- * keys will allow 1000 per hour which is definitely plenty
+** keys will allow 1000 per hour which is definitely plenty

← Older revision		Revision as of 16:19, 29 May 2025
Line 13:		Line 13:
	* sites=12141300 -- This is which gauge we want to look at		* sites=12141300 -- This is which gauge we want to look at
	* period=PT22M29.5308163S -- This is the time range we want to fetch data for; basically it will be an encoded version of "since the last time we asked".		* period=PT22M29.5308163S -- This is the time range we want to fetch data for; basically it will be an encoded version of "since the last time we asked".
		+
		+	=== Notes about changes ===
		+
		+	The USGS is updating their systems, and we'll have to make changes to support the updated format. This is a series of
		+	notes about the changes we'll have to make.
		+
		+	* URL Base is changing
		+	* parameter names are changing but the encoding appears to be the same
		+	* e.g. "period" parameter will still be encoded in "P1D" format
		+	* all the metadata gunk in the response is going away, yay
		+	* will want to get an API Key to avoid rate-limiting (although 100 requests/hour is probably more than we need)
		+	* keys will allow 1000 per hour which is definitely plenty

@@ Line 6: / Line 6: @@
 https://waterservices.usgs.gov/nwis/iv/?format=json&indent=on&parameterCd=00060,00065&siteStatus=all&sites=12141300&period=PT22M29.5308163S
 </pre>
 The important pieces of the URL: