Data Request
Description
This operation returns CIMIS weather data in either JSON (default) or XML. This includes data from the CIMIS Weather Station Network (WSN) and/or the Spatial CIMIS System (SCS). Data requests may be made in the following ways:
- WSN data by station number(s)
- WSN or SCS data by zip code(s)
- SCS data by coordinate in decimal degrees
- SCS data by street address(es)
Considerations for Zip Code Requests
Zip code requests are unique because the WSN and SCS data providers may qualify to satisfy the request.
This differs from every other request type which always returns data from a specific provider (see Venn diagram).
So it's important to understand how the system determines which data provider is used for any given zip code.
The system examines each zip code in the targets parameter in turn and determines the following.
- is zip supported by WSN provider
- is zip supported by SCS provider
- is prioritizeSCS set to 'Y'
The following table shows which data provider is used based on the three criteria.
|
The WSN data provider supports all zip codes associated with any station within the weather station network. Use the Station List service to obtain a complete list of weather stations, this list also shows the zip codes associated with each station. Alternatively, you may use the Station Zip Code List service to obtain a distinct list of all zip codes supported by the WSN data provider. The SCS data provider supports all California zip codes identified during the 2010 census. The census data was used to obtain zip code polygons. The system uses these polygons to identify the area for each zip code. The system then averages ETo and Solar Radiation values for the zip code area using a 2/km grid. Use the Spatial Zip Code List to obtain a distinct list of all zip codes supported by the SCS data provider. |
In order for your query to successfully return data the zip codes in your request must be found to be supported by the WSN or SCS data providers, or both. If you attempt to query a zip code that is supported by neither provider you will receive a 404 error. The WSN data provider supports all zip codes that are associated with existing weather stations and the SCS data provider supports all zip codes covered by the 2010 census.
If a zip code request includes hourly data items the system will not return SCS data because the SCS data provider does not support hourly data.
Parameters
| appKey required |
Registered users are issued their own unique application key. The application key is required for each data request. Notice that authentication through a username and password is not required. The system simply identifies you through the application key. |
| targets required |
targets are geographies or weather stations of interest. targets answers the
question, "What area or station am I reporting on? The targets parameter may specify one-to-many
stations, zip codes, coordinates, or street addresses; however, you are not allowed to mix values from
different categories. This means the targets parameter must contain only stations, only
zip codes, only coordinates, or only street addresses. You will receive an error if you attempt to mix
different category types. The following is the category list:
ex: "2, 80, 127" weather station list (comma delimited) ex: "95823, 90017" zip code list (comma delimited) ex: "lat=34.99,lng=-118.34; lat=36.45,lng=-118.16" (semicolon delimited) ex: "addr-name=State Capitol,addr=1315 10th Street Sacramento, CA 95814;addr-name=Grauman's Chinese Theatre,addr=6925 Hollywood Boulevard, Los Angeles, CA 90028" (semicolon delimited) |
| startDate required |
Specifies the start date. The data format is "yyyy-mm-dd".
Example: 2012-01-01 |
| endDate required |
Specifies the end date. The data format is "yyyy-mm-dd".
Example: 2012-01-01 |
| unitOfMeasure optional |
The unitOfMeasure may be either ‘E’ for English units or ‘M’ for metric units. The value
of this parameter will affect data values in the response. For example, designating
English units will result in temperature values being returned in Fahrenheit rather than Celsius.
Default: 'E' |
| dataItems optional |
dataItems specifies one-to-many comma delimited data elements to include in your
response. See the Data Items section for a complete list of possible
data element values. Default: day-asce-eto, day-precip, day-sol-rad-avg, day-vap-pres-avg, day-air-tmp-max, day-air-tmp-min, day-air-tmp-avg, day-rel-hum-max, day-rel-hum-min, day-rel-hum-avg, day-dew-pnt, day-wind-spd-avg, day-wind-run, day-soil-tmp-avg |
| prioritizeSCS optional |
This parameter is relevant only when the targets parameter contains zip code(s). The value
for this parameter may be either 'Y' or 'N'. See the Considerations for Zip Code Requests
section above for details.
Default: 'Y' |
Data Items
WSN supports all daily and hourly data items. SCS supports ASCE ETo (PM ETo) and Solar Radiation (Rs) data items at a 2/km resolution. The following table shows the data items available for the WSN and SCS.
| Name | Data Item | Class | Data Provider Support |
|---|---|---|---|
| Average Air Temperature | day-air-tmp-avg | Daily | WSN |
| Average Air Temperature | day-air-tmp-avg | Daily | WSN |
| Minimum Air Temperature | day-air-tmp-min | Daily | WSN |
| Dew Point | day-dew-pnt | Daily | WSN |
| CIMIS ETo | day-eto | Daily | WSN |
| ASCE ETo | day-asce-eto | Daily | WSN & SCS |
| ASCE ETr | day-asce-etr | Daily | WSN |
| Precipitation | day-precip | Daily | WSN |
| Average Relative Humidity | day-rel-hum-avg | Daily | WSN |
| Maximum Relative Humidity | day-rel-hum-max | Daily | WSN |
| Minimum Relative Humidity | day-rel-hum-min | Daily | WSN |
| Average Soil Temperature | day-soil-tmp-avg | Daily | WSN |
| Maximum Soil Temperature | day-soil-tmp-max | Daily | WSN |
| Minimum Soil Temperature | day-soil-tmp-min | Daily | WSN |
| Average Solar Radiation | day-sol-rad-avg | Daily | WSN & SCS |
| Net Solar Radiation | day-sol-rad-net | Daily | WSN |
| Maximum Vapor Pressure | day-vap-pres-max | Daily | WSN |
| Average Vapor Pressure | day-vap-pres-avg | Daily | WSN |
| Wind East-North-East | day-wind-ene | Daily | WSN |
| Wind East-South-East | day-wind-ese | Daily | WSN |
| Wind North-North-East | day-wind-nne | Daily | WSN |
| Wind North-North-West | day-wind-nnw | Daily | WSN |
| Wind Run | day-wind-run | Daily | WSN |
| Average Wind Speed | day-wind-spd-avg | Daily | WSN |
| Wind South-South-West | day-wind-ssw | Daily | WSN |
| Wind West-North-West | day-wind-wnw | Daily | WSN |
| Wind West-South-West | day-wind-wsw | Daily | WSN |
| Name | Data Item | Class | Data Provider Support |
|---|---|---|---|
| Air Temperature | hly-air-tmp | Hourly | WSN |
| Dew Point | hly-dew-pnt | Hourly | WSN |
| CIMIS ETo | hly-eto | Hourly | WSN |
| Net Radiation | hly-net-rad | Hourly | WSN |
| ASCE ETo | hly-asce-eto | Hourly | WSN |
| ASCE ETr | hly-asce-etr | Hourly | WSN |
| Precipitation | hly-precip | Hourly | WSN |
| Relative Humidity | hly-rel-hum | Hourly | WSN |
| Resultant Wind | hly-res-wind | Hourly | WSN |
| Soil Temperature | hly-soil-tmp | Hourly | WSN |
| Solar Radiation | hly-sol-rad | Hourly | WSN |
| Vapor Pressure | hly-vap-pres | Hourly | WSN |
| Wind Direction | hly-wind-dir | Hourly | WSN |
| Wind Speed | hly-wind-spd | Hourly | WSN |
Examples
Default Daily Station Request
This example request will obtain a default station report. Notice the dataItems, unitOfMeasure, and prioritizeSCS parameters are unspecified; therefore, the default values will be used for each of those parameters.https://et.water.ca.gov/api/data?appKey=YOUR-APP-KEY&targets=2,8,127&startDate=2010-01-01&endDate=2010-01-05JSON Response
Set HTTP request's Accept Header to "application/json"
{
"Data": {
"Providers": [
{
"Name": "cimis",
"Type": "station",
"Owner": "water.ca.gov",
"Records": [
{
"Date": "2010-01-01",
"Julian": "1",
"Station": "2",
"Standard": "english",
"ZipCodes": "93624",
"Scope": "daily",
"DayAirTmpAvg": {
"Value": "39",
"Qc": " ",
"Unit": "(F)"
},
"DayAirTmpMax": {
"Value": "57.3",
"Qc": " ",
"Unit": "(F)"
},
"DayAirTmpMin": {
"Value": "29.8",
"Qc": " ",
"Unit": "(F)"
},
... Results Truncated ...
}
]
}
]
}
}
XML ResponseSet HTTP request's Accept Header to "application/xml"
<et-xml xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="https://www.w3.org/2001/XMLSchema">
<data>
<provider name="cimis" type="station" owner="water.ca.gov">
<record date="2010-01-01" julian="1" station="2" standard="english" zip-code="93624" scope="daily">
<day-air-tmp-avg qc=" " unit="(F)">39</day-air-tmp-avg>
<day-air-tmp-max qc=" " unit="(F)">57.3</day-air-tmp-max>
<day-air-tmp-min qc=" " unit="(F)">29.8</day-air-tmp-min>
<day-dew-pnt qc=" " unit="(F)">38.8</day-dew-pnt>
<day-asce-eto qc="R" unit="(in)">0.03</day-asce-eto>
<day-precip qc=" " unit="(in)">0</day-precip>
<day-rel-hum-avg qc=" " unit="(%)">99</day-rel-hum-avg>
<day-rel-hum-max qc=" " unit="(%)">100</day-rel-hum-max>
<day-rel-hum-min qc=" " unit="(%)">72</day-rel-hum-min>
<day-soil-tmp-avg qc=" " unit="(F)">50.5</day-soil-tmp-avg>
<day-sol-rad-avg qc=" " unit="(Ly/day)">141</day-sol-rad-avg>
<day-vap-pres-avg qc=" " unit="(mBars)">8</day-vap-pres-avg>
<day-wind-run qc=" " unit="(MPH)">33.4</day-wind-run>
<day-wind-spd-avg qc=" " unit="(MPH)">1.4</day-wind-spd-avg>
</record>
<record date="2010-01-02" julian="2" station="2" standard="english" zip-code="93624" scope="daily">
<day-air-tmp-avg qc="H" unit="(F)">5.4</day-air-tmp-avg>
<day-air-tmp-max qc="R" unit="(F)">32.5</day-air-tmp-max>
<day-air-tmp-min qc="S" unit="(F)"/>
<day-dew-pnt qc=" " unit="(F)">15.2</day-dew-pnt>
<day-asce-eto qc="R" unit="(in)">0.01</day-asce-eto>
<day-precip qc=" " unit="(in)">0.01</day-precip>
<day-rel-hum-avg qc=" " unit="(%)">100</day-rel-hum-avg>
<day-rel-hum-max qc="H" unit="(%)">100</day-rel-hum-max>
<day-rel-hum-min qc="H" unit="(%)">100</day-rel-hum-min>
<day-soil-tmp-avg qc=" " unit="(F)">50.3</day-soil-tmp-avg>
<day-sol-rad-avg qc=" " unit="(Ly/day)">100</day-sol-rad-avg>
<day-vap-pres-avg qc=" " unit="(mBars)">3</day-vap-pres-avg>
<day-wind-run qc=" " unit="(MPH)">41.1</day-wind-run>
<day-wind-spd-avg qc=" " unit="(MPH)">1.7</day-wind-spd-avg>
</record>
... Results Truncated ...
<record date="2010-01-05" julian="5" station="127" standard="english" zip-code="92275" scope="daily">
<day-air-tmp-avg qc=" " unit="(F)">55</day-air-tmp-avg>
<day-air-tmp-max qc=" " unit="(F)">74.5</day-air-tmp-max>
<day-air-tmp-min qc=" " unit="(F)">41.5</day-air-tmp-min>
<day-dew-pnt qc=" " unit="(F)">34.9</day-dew-pnt>
<day-asce-eto qc="N" unit="(in)"/>
<day-precip qc="N" unit="(in)"/>
<day-rel-hum-avg qc=" " unit="(%)">47</day-rel-hum-avg>
<day-rel-hum-max qc=" " unit="(%)">74</day-rel-hum-max>
<day-rel-hum-min qc=" " unit="(%)">25</day-rel-hum-min>
<day-soil-tmp-avg qc="N" unit="(F)"/>
<day-sol-rad-avg qc=" " unit="(Ly/day)">310</day-sol-rad-avg>
<day-vap-pres-avg qc=" " unit="(mBars)">6.9</day-vap-pres-avg>
<day-wind-run qc=" " unit="(MPH)">78.1</day-wind-run>
<day-wind-spd-avg qc=" " unit="(MPH)">3.3</day-wind-spd-avg>
</record>
</provider>
</data>
</et-xml>
Daily & Hourly Station Request
This example request will obtain a Daily and Hourly ASCE ETo station report. Notice the dataItems parameter include daily and hourly ASCE ETo data items. As a result, the system will respond with daily and hourly data from the WSN data provider.https://et.water.ca.gov/api/data?appKey=YOUR-APP-KEY&targets=5&startDate=2010-01-01&endDate=2010-01-01&dataItems=day-asce-eto,hly-asce-etoJSON Response
Set HTTP request's Accept Header to "application/json"
{
"Data": {
"Providers": [
{
"Name": "cimis",
"Type": "station",
"Owner": "water.ca.gov",
"Records": [
{
"Date": "2010-01-01",
"Julian": "1",
"Station": "5",
"Standard": "english",
"ZipCodes": "93263, 93280",
"Scope": "daily",
"DayAsceEto": {
"Value": "0.03",
"Qc": " ",
"Unit": "(in)"
}
}
]
},
{
"Name": "cimis",
"Type": "station",
"Owner": "water.ca.gov",
"Records": [
{
"Date": "2010-01-01",
"Julian": "1",
"Hour": "0100",
"Station": "5",
"Standard": "english",
"ZipCodes": "93263, 93280",
"Scope": "hourly",
"HlyAsceEto": {
"Value": "0",
"Qc": " ",
"Unit": "(in)"
}
},
{
"Date": "2010-01-01",
"Julian": "1",
"Hour": "0200",
"Station": "5",
"Standard": "english",
"ZipCodes": "93263, 93280",
"Scope": "hourly",
"HlyAsceEto": {
"Value": "0",
"Qc": " ",
"Unit": "(in)"
}
},
... Results Truncated ...
{
"Date": "2010-01-01",
"Julian": "1",
"Hour": "2400",
"Station": "5",
"Standard": "english",
"ZipCodes": "93263, 93280",
"Scope": "hourly",
"HlyAsceEto": {
"Value": "0",
"Qc": " ",
"Unit": "(in)"
}
}
]
}
]
}
}
XML ResponseSet HTTP request's Accept Header to "application/xml"
<et-xml xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="https://www.w3.org/2001/XMLSchema">
<data>
<provider name="cimis" type="station" owner="water.ca.gov">
<record date="2010-01-01" julian="1" station="5" standard="english" zip-code="93263, 93280"
scope="daily">
<day-asce-eto qc=" " unit="(in)">0.03</day-asce-eto>
</record>
</provider>
<provider name="cimis" type="station" owner="water.ca.gov">
<record date="2010-01-01" julian="1" hour="0100" station="5" standard="english"
zip-code="93263, 93280" scope="hourly">
<hly-asce-eto qc=" " unit="(in)">0</hly-asce-eto>
</record>
<record date="2010-01-01" julian="1" hour="0200" station="5" standard="english"
zip-code="93263, 93280" scope="hourly">
<hly-asce-eto qc=" " unit="(in)">0</hly-asce-eto>
</record>
... Results Truncated ...
<record date="2010-01-01" julian="1" hour="2300" station="5" standard="english"
zip-code="93263, 93280" scope="hourly">
<hly-asce-eto qc=" " unit="(in)">0</hly-asce-eto>
</record>
<record date="2010-01-01" julian="1" hour="2400" station="5" standard="english"
zip-code="93263, 93280" scope="hourly">
<hly-asce-eto qc=" " unit="(in)">0</hly-asce-eto>
</record>
</provider>
</data>
</et-xml>
Daily Zip Code Request w/ SCS Prioritization
This request example together with the one that follows illustrates the dynamics of how zip code requests are fulfilled. Your choice to prioritize SCS or not plays a major role in what data provider is used to fulfill your request. In this example we are specifying three zip codes (97544,95974,95938). Because this request prioritizes the SCS data provider the system attempts to fulfill each zip code using SCS. The response below shows that SCS supports all of the given zip codes.https://et.water.ca.gov/api/data?appKey=YOUR-APP-KEY&targets=97544,95974,95938&startDate=2010-01-01&endDate=2010-01-01&dataItems=day-asce-eto,day-eto,day-precip&unitOfMeasure=M;prioritizeSCS=YJSON Response
Set HTTP request's Accept Header to "application/json"
{
"Data": {
"Providers": [
{
"Name": "cimis",
"Type": "spatial",
"Owner": "water.ca.gov",
"Records": [
{
"Date": "2010-01-01",
"Julian": "1",
"Standard": "english",
"ZipCodes": "97544",
"Scope": "daily",
"DayAsceEto": {
"Value": "0.04",
"Qc": " ",
"Unit": "(in)"
}
},
{
"Date": "2010-01-01",
"Julian": "1",
"Standard": "english",
"ZipCodes": "95974",
"Scope": "daily",
"DayAsceEto": {
"Value": "0.03",
"Qc": " ",
"Unit": "(in)"
}
},
{
"Date": "2010-01-01",
"Julian": "1",
"Standard": "english",
"ZipCodes": "95938",
"Scope": "daily",
"DayAsceEto": {
"Value": "0.04",
"Qc": " ",
"Unit": "(in)"
}
}
]
}
]
}
}
XML ResponseSet HTTP request's Accept Header to "application/xml"
<et-xml xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="https://www.w3.org/2001/XMLSchema">
<data>
<provider name="cimis" type="spatial" owner="water.ca.gov">
<record date="2010-01-01" julian="1" standard="english" zip-code="97544" scope="daily">
<day-asce-eto qc=" " unit="(in)">0.04</day-asce-eto>
</record>
<record date="2010-01-01" julian="1" standard="english" zip-code="95974" scope="daily">
<day-asce-eto qc=" " unit="(in)">0.03</day-asce-eto>
</record>
<record date="2010-01-01" julian="1" standard="english" zip-code="95938" scope="daily">
<day-asce-eto qc=" " unit="(in)">0.04</day-asce-eto>
</record>
</provider>
</data>
</et-xml>
Daily Zip Code Request w/ WSN Prioritization
This request example is identical to the previous except the prioritizeSCS parameter is set to [N]o. Since the SCS data provider is not prioritized the system will attempt to obtain zip code data from the WSN data provider first. The system will then attempt to process any unprocessed zip codes using the SCS data provider. So, it's possible to have zip code data supplied by more than a single data provider, as with this example.
The first zip code (97544) is not supported by WSN data provider. The latter two zip codes (95974, 95938) are supported by WSN - specifically for Station #12. It's important to note that a single weather station may be associated with more than one zip code. You'll notice that since SCS was not prioritized that the system provides WSN data for Station #12 to satisfy zip codes 95974 & 95938, while providing SCS data for zip code 97544.
https://et.water.ca.gov/api/data?appKey=YOUR-APP-KEY&targets=97544,95974,95938&startDate=2010-01-01&endDate=2010-01-01&dataItems=day-asce-eto,day-eto,day-precip&unitOfMeasure=M;prioritizeSCS=NJSON Response
Set HTTP request's Accept Header to "application/json"
{
"Data": {
"Providers": [
{
"Name": "cimis",
"Type": "station",
"Owner": "water.ca.gov",
"Records": [
{
"Date": "2010-01-01",
"Julian": "1",
"Station": "12",
"Standard": "english",
"ZipCodes": "95974, 95958, 95938",
"Scope": "daily",
"DayEto": {
"Value": "0.02",
"Qc": " ",
"Unit": "(in)"
},
"DayAsceEto": {
"Value": "0.02",
"Qc": " ",
"Unit": "(in)"
},
"DayPrecip": {
"Value": "0.03",
"Qc": " ",
"Unit": "(in)"
}
}
]
},
{
"Name": "cimis",
"Type": "spatial",
"Owner": "water.ca.gov",
"Records": [
{
"Date": "2010-01-01",
"Julian": "1",
"Standard": "english",
"ZipCodes": "97544",
"Scope": "daily",
"DayAsceEto": {
"Value": "0.04",
"Qc": " ",
"Unit": "(in)"
}
}
]
}
]
}
}
XML ResponseSet HTTP request's Accept Header to "application/xml"
<et-xml xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="https://www.w3.org/2001/XMLSchema">
<data>
<provider name="cimis" type="station" owner="water.ca.gov">
<record date="2010-01-01" julian="1" station="12" standard="english"
zip-code="95974, 95958, 95938" scope="daily">
<day-eto qc=" " unit="(in)">0.02</day-eto>
<day-asce-eto qc=" " unit="(in)">0.02</day-asce-eto>
<day-precip qc=" " unit="(in)">0.03</day-precip>
</record>
</provider>
<provider name="cimis" type="spatial" owner="water.ca.gov">
<record date="2010-01-01" julian="1" standard="english"
zip-code="97544" scope="daily">
<day-asce-eto qc=" " unit="(in)">0.04</day-asce-eto>
</record>
</provider>
</data>
</et-xml>
Exceptions
The following are the HTTP errors you may experience if there are server errors or errors in your request. See the Online Service Test page for request examples of the following exceptions.
| Code | Name | HTTP Code | Description |
|---|---|---|---|
| ERR1006 | INVALID APP KEY | 403 - Forbidden | The appKey parameter contains an invalid application key. |
| ERR1019 | STATION NOT FOUND | 404 - Not Found | The targets parameter contains a value recognized as an invalid station number. |
| ERR1031 | UNSUPPORTED ZIP CODE | 404 - Not Found | The targets parameter contains a value recognized as an unsupported zip code. |
| ERR1034 | COORD NOT IN CA | 404 - Not Found | The targets parameter contains a value recognized as a coordinate outside the state of California. |
| ERR1035 | DATA ITEM NOT FOUND | 404 - Not Found | The dataItems parameter contains an invalid data item. |
| ERR1025 | INVALID COORDINATE | 400 - Bad Request | The targets parameter contains a value recognized as an invalid coordinate. |
| ERR2006 | INVALID TARGET | 400 - Bad Request | The targets parameter that cannot be classified as a valid target type. |
| ERR2115 | INVALID ADDRESS DATA ITEM | 400 - Bad Request | The targets parameter contains a data item this is not either 'day-asce-eto', 'day-sol-rad-avg'. |
| ERR2114 | INVALID COORDINATE DATA ITEM | 400 - Bad Request | The targets parameter contains a data item this is not either 'day-asce-eto', 'day-sol-rad-avg'. |
| ERR2007 | HLY COORDINATES FAULT | 400 - Bad Request | The targets parameter invalidly contains hourly data items for SCS data. |
| ERR1010 | FUTURE DATE FAULT | 400 - Bad Request | The startDate and/or endDate parameters specify future dates. |
| ERR1011 | ORIGIN DATE FAULT | 400 - Bad Request | The startDate and/or endDate parameters specify dates before June 7st, 1982, which is the earliest date for CIMIS data. |
| ERR1012 | DATE ORDER FAULT | 400 - Bad Request | The startDate is greater than the endDate. |
| ERR1032 | INVALID UNIT OF MEASURE | 400 - Bad Request | The unitOfMeasure parameter is something other than 'E' or 'M'. |
| ERR2112 | DATA VOLUME VIOLATION | 400 - Bad Request | The request exceeds data limitations. |
Station Request
Description
This operation returns CIMIS station information:
Get All Stations
https://et.water.ca.gov/api/station
JSON Example
{
"Stations": [
... Results Truncated ...
{
"StationNbr": "2",
"Name": "FivePoints",
"City": "Five Points",
"RegionalOffice": null,
"County": null,
"ConnectDate": "6\/7\/1982",
"DisconnectDate": "12\/31\/2030",
"IsActive": "True",
"IsEtoStation": "True",
"Elevation": "285",
"GroundCover": "Grass",
"HmsLatitude": "36\u00ba20'10N \/ 36.3360",
"HmsLongitude": "-120\u00ba6'47W \/ -120.1130",
"ZipCodes": [
"93624"
],
"SitingDesc": ""
},
... Results Truncated ...
{
"StationNbr": "149",
"Name": "Oakland Foothills",
"City": "Oakland",
"RegionalOffice": null,
"County": null,
"ConnectDate": "3\/25\/1999",
"DisconnectDate": "12\/31\/2030",
"IsActive": "True",
"IsEtoStation": "True",
"Elevation": "145",
"GroundCover": "Grass",
"HmsLatitude": "37\u00ba46'52N \/ 37.7810",
"HmsLongitude": "-122\u00ba10'44W \/ -122.1790",
"ZipCodes": [
"94613"
],
"SitingDesc": ""
},
... Results Truncated ...
]
}
XML Example
<data xmlns:xsd="https://www.w3.org/2001/XMLSchema" xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance"> <stations> ... Results Truncated ... <station station-nbr="2" name="FivePoints" city="Five Points"> <connect-date>6/7/1982</connect-date> <disconnect-date>12/31/2030</disconnect-date> <is-active>True</is-active> <is-eto-station>True</is-eto-station> <elevation>285</elevation> <ground-cover>Grass</ground-cover> <hms-latitude>36º20'10N / 36.3360</hms-latitude> <hms-longitude>-120º6'47W / -120.1130</hms-longitude> <zip-codes> <zip-code>93624</zip-code> </zip-codes> <siting-desc/> </station> ... Results Truncated ... <station station-nbr="149" name="Oakland Foothills" city="Oakland"> <connect-date>3/25/1999</connect-date> <disconnect-date>12/31/2030</disconnect-date> <is-active>True</is-active> <is-eto-station>True</is-eto-station> <elevation>145</elevation> <ground-cover>Grass</ground-cover> <hms-latitude>37º46'52N / 37.7810</hms-latitude> <hms-longitude>-122º10'44W / -122.1790</hms-longitude> <zip-codes> <zip-code>94613</zip-code> </zip-codes> <siting-desc/> </station> ... Results Truncated ... </stations> </data>