- API
dietz3
data.marincounty.org | Last Updated 2024-04-05T13:30:40.000ZEmergency Medical Service ambulance dispatch incidents in Marin County, CA, for the period beginning March 1, 2013 through March 31, 2017. Data is updated quarterly. Data includes time stamps of events for each dispatch, nature of injury, and location of injury. Data also includes geocoding of most incident locations, however, specific street address locations are "obfuscated" and are generally shown within a block and are not, therefore, exact locations. Geocoding results are also based on the quality of the address information provided, and should therefore not be considered 100% accurate. Some of the data may be interpreted incorrectly without adequate knowledge of the clinical context. Please contact EMS@marincounty.org if you have any questions about the interpretation of fields in this dataset.
- API
SBUV2/NOAA-11 Ozone (O3) Profile and Total Column Ozone Monthly L3 Global 5.0deg Lat Zones V1
nasa-test-0.demo.socrata.com | Last Updated 2015-07-20T04:54:41.000ZThe Solar Backscattered Ultra Violet (SBUV) from NOAA-11 Level-3 monthly zonal mean (MZM) product (SBUV2N11L3zm) is derived from the Level-2 retrieved ozone profiles. Ozone retrievals are generated from the v8.6 SBUV algorithm. A Level-3 MZM file computes zonal means covering 5 degree latitude bands for each calendar month. For this product there are 147 months of data from January 1989 through March 2001. There are a total of 36 latitudinal bands, 18 in each hemisphere. Profile data are provided at 21 layers from 1013.25, 639.318, 403.382,254.517, 160.589, 101.325,63.9317, 40.3382, 25.4517, 16.0589, 10.1325, 6.39317,4.03382, 2.54517, 1.60589, 1.01325,0.639317, 0.403382, 0.254517, 0.160589 and 0.101325 hPa (measured at bottom of layer). NOTE: Some profiles have 20 layers and do not report the top most layer. Mixing ratios are reported at 15 layers from 0.5, 0.7, 1.0, 1.5, 2.0, 3.0, 4.0, 5.0, 7.0, 10.0, 15.0, 20.0, 30.0, 40.0 and 50.0 hPa (measured at middle of layer). The MZM product averages retrievals that meet the criteria for a good retrieval as determined by error flags in the Level 2 data. A good retrieval is defined as satisfying the following conditions: 1) Profile Error Flag = 0 or 1 (0 = good retrieval; 1 = solar zenith angle > 84 deg.) 2) Total Error Flags = 0, 1, 2 or 5 (0 = good retrieval; 1 = not used; 2 = solar zenith angle > 84 deg; large discrepancy between profile total and best total ozone) NOTE - Total error flag = 5 is anomalously applied at high latitudes and high solar zenith angle where B-Pair total ozone estimate is not as reliable as profile under these conditions. This error flag may be removed in future version of algorithm. The zonal means computed for each month are screened according to the following statistical criteria: 1) number of good retrievals for the month greater than or equal to 2/3 of the samples for a nominal month. 2) mean latitude of good retrievals less than or equal to 1 degree from center of latitude band. 3) mean time of good retrievals less than or equal to 4 days from center of month (i.e., day = 15)
- API
Population Exposure Estimates in Proximity to Nuclear Power Plants, Country-Level Aggregates
nasa-test-0.demo.socrata.com | Last Updated 2015-07-20T04:36:37.000ZThe Population Exposure Estimates in Proximity to Nuclear Power Plants, Country-Level Aggregates data set consists of country-level estimates of total, urban, and rural populations and land area, country-wide, that are in proximity to a nuclear power plant. This data set was created using a global data set of point locations of nuclear power plants, with buffer zones at 30km, 75km, 150km, 300km, 600km, and 1200km, and the Global Population Count Grid Time Series Estimates, Version 1 to estimate the population within each buffer zone for the years 1990, 2000, and 2010. Global Rural-Urban Mapping Project, Version 1 (GRUMPv1) Land and Geographic Unit Area Grids were used to estimate land area within each buffer zone. The GRUMPv1 Urban Extents Grid was used to further delineate population and land area estimates within urban and rural areas. All grids used for population, land area, and urban mask were of 1 km (30 arc-second) resolution.
- API
SBUV2/NOAA-16 Ozone (O3) Profile and Total Column Ozone 1 Month Zonal Mean L3 Global 5.0 degree Latitude Zones V1 (SBUV2N16L3zm) at GES DISC
data.nasa.gov | Last Updated 2022-01-17T05:51:01.000ZThe Solar Backscattered Ultraviolet (SBUV) from NOAA-16 Level-3 monthly zonal mean (MZM) product (SBUV2N16L3zm) is derived from the Level-2 retrieved ozone profiles. Ozone retrievals are generated from the v8.6 SBUV algorithm. A Level-3 MZM file computes zonal means covering 5 degree latitude bands for each calendar month. For this product there are 154 months of data from October 2000 through July 2013. There are a total of 36 latitudinal bands, 18 in each hemisphere. Profile data are provided at 21 layers from 1013.25, 639.318, 403.382,254.517, 160.589, 101.325,63.9317, 40.3382, 25.4517, 16.0589, 10.1325, 6.39317,4.03382, 2.54517, 1.60589, 1.01325,0.639317, 0.403382, 0.254517, 0.160589 and 0.101325 hPa (measured at bottom of layer). NOTE: Some profiles have 20 layers and do not report the top most layer. Mixing ratios are reported at 15 layers from 0.5, 0.7, 1.0, 1.5, 2.0, 3.0, 4.0, 5.0, 7.0, 10.0, 15.0, 20.0, 30.0, 40.0 and 50.0 hPa (measured at middle of layer). The MZM product averages retrievals that meet the criteria for a good retrieval as determined by error flags in the Level 2 data. A good retrieval is defined as satisfying the following conditions: 1) Profile Error Flag = 0 or 1 (0 = good retrieval; 1 = solar zenith angle > 84 degrees). 2) Total Error Flags = 0, 1, 2 or 5 (0 = good retrieval; 1 = not used; 2 = solar zenith angle > 84 degrees; large discrepancy between profile total and best total ozone). NOTE - Total error flag = 5 is anomalously applied at high latitudes and high solar zenith angles where the B-Pair total ozone estimate is not as reliable as the ozone profile under these conditions. This error flag may be removed in future version of algorithm. The zonal means computed for each month are screened according to the following statistical criteria: 1) Number of good retrievals for the month greater than or equal to 2/3 of the samples for a nominal month. 2) Mean latitude of good retrievals less than or equal to 1 degree from center of latitude band. 3) Mean time of good retrievals less than or equal to 4 days from center of month (i.e., day = 15).
- API
GPM, DPR, GMI Level 3 Combined Precipitation V03
nasa-test-0.demo.socrata.com | Last Updated 2015-07-20T05:03:54.000ZThere are uncertainties in the interpretation of data from any one of the instruments (KuPR, KaPR, and GMI). By using data from multiple instruments, further constraints on the solution of precipitation structure improve the final product.The purpose of 3CMB is to give a daily and monthly accumulation of the 2BCMB precipitation product. The 3CMB product is a daily and monthly accumulation of the 2BCMB orbital combined product at two grid sizes, 5 x 5 degrees (G1) and 0.25 x 0.25 degrees (G2). Grid G1 contains the following physical measurements of general interest, among others. Grid G2 contains the same groups, but it is on the ltH x lnH grid and does not have the surface type (st) dimension or the histograms (see dimension definitions below). Below, conditional products represent means based upon precipitating areas only; unconditional products represent means for raining and non-raining areas combined. Probabilities represent the number of raining observations divided by the total number of raining and non-raining observations. precipTotRate (Group in G1)- Conditional mean rate for all precipitation phases (ice, liquid, mixed-phase). * count (4-byte integer, array size: ltL x lnL x ns x hgt x rt x st): Count. * mean (4-byte float, array size: ltL x lnL x ns x hgt x rt x st): Mean, mm/h. * stdev (4-byte float, array size: ltL x lnL x ns x hgt x rt x st): Standard deviation for the monthly product. Mean of squares for the daily product, mm/h. * hist (4-byte integer, array size: ltL x lnL x ns x hgt x rt x st x bin): Histogram. precipLiqRate (Group in G1) - Conditional mean rate for liquid precipitation. * count (4-byte integer, array size: ltL x lnL x ns x hgt x rt x st): Count. * mean (4-byte float, array size: ltL x lnL x ns x hgt x rt x st): Mean, mm/h. * stdev (4-byte float, array size: ltL x lnL x ns x hgt x rt x st): Standard deviation for the monthly product. Mean of squares for the daily product, mm/h. * hist (4-byte integer, array size: ltL x lnL x ns x hgt x rt x st x bin): Histogram. precipTotWaterContent (Group in G1) - Conditional mean water content for all precipitation phases. * count (4-byte integer, array size: ltL x lnL x ns x hgt x rt x st): Count. * mean (4-byte float, array size: ltL x lnL x ns x hgt x rt x st): Mean, g/m3. * stdev (4-byte float, array size: ltL x lnL x ns x hgt x rt x st): Standard deviation for the monthly product. Mean of squares for the daily product, g/m3. * hist (4-byte integer, array size: ltL x lnL x ns x hgt x rt x st x bin): Histogram. precipLiqWaterContent (Group in G1) - Conditional mean liquid water content. * count (4-byte integer, array size: ltL x lnL x ns x hgt x rt x st): Count. * mean (4-byte float, array size: ltL x lnL x ns x hgt x rt x st): Mean, g/m3. * stdev (4-byte float, array size: ltL x lnL x ns x hgt x rt x st): Standard deviation for the monthly product. Mean of squares for the daily product, g/m3. * hist (4-byte integer, array size: ltL x lnL x ns x hgt x rt x st x bin): Histogram. precipTotDm (Group in G1) - Conditional mass-weighted mean particle diameter. * count (4-byte integer, array size: ltL x lnL x ns x hgt x rt x st): Count. * mean (4-byte float, array size: ltL x lnL x ns x hgt x rt x st): Mean, mm. * stdev (4-byte float, array size: ltL x lnL x ns x hgt x rt x st): Standard deviation for the monthly product. Mean of squares for the daily product, mm. * hist (4-byte integer, array size: ltL x lnL x ns x hgt x rt x st x bin): Histogram. precipTotRateDiurnal (Group in G1) - Conditional mean total surface precipitation rate indexed by local time. * count (4-byte integer, array size: ltL x lnL x ns x st x tim): Count. * mean (4-byte float, array size: ltL x lnL x ns x st x tim): Mean, mm/h. * stdev (4-byte float, array size: ltL x lnL x ns x st x tim): Standard deviation for the monthly product. Mean of squares for the daily product, mm/h. surfPrecipTotRateDiurnalAllObs (4-byte integer, array size: ltL x lnL x ns x st x tim): Number of total observa...
- API
311 Service Requests - Street Lights - All Out - No Duplicates
data.cityofchicago.org | Last Updated 2019-04-18T00:53:09.000ZNote: This filtered view shows only those service requests from the underlying dataset that are not marked as duplicates. -- All open reports of "Street Lights - All Out" (an outage of 3 or more lights) made to 311 and all requests completed since January 1, 2011.The Chicago Department of Transportation (CDOT) oversees approximately 250,000 street lights that illuminate arterial and residential streets in Chicago. CDOT performs repairs and bulb replacements in response to residents’ reports of street light outages. Whenever CDOT receives a report of an “All Out” the electrician assigned to make the repair looks at all the lights in that circuit (each circuit has 8-16 lights) to make sure that they are all working properly. If a second request of lights out in the same circuit is made within four calendar days of the original request, the newest request is automatically given the status of “Duplicate (Open).” Since CDOT's electrician will be looking at all the lights in a circuit to verify that they are all working, any “Duplicate (Open)” address will automatically be observed and repaired. Once the street lights are repaired, the status in CSR will read “Completed” for the original request and “Duplicate (Closed)” for any duplicate requests. A service request also receives the status of “Completed” when the reported lights are inspected but found to be in good repair and functioning; when the service request is for a non-existent address; or when the lights are maintained by a contractor. Data is updated daily.
- API
BUV/Nimbus-04 Ozone (O3) Profile and Total Column Ozone Monthly L3 Global 5.0deg Lat Zones V1
nasa-test-0.demo.socrata.com | Last Updated 2015-07-20T05:06:00.000ZThe Solar Backscattered Ultra Violet (SBUV) from Nimbus-4 Level-3 monthly zonal mean (MZM) product (BUVN04L3zm) is derived from the Level-2 retrieved ozone profiles. Ozone retrievals are generated from the v8.6 SBUV algorithm. A Level-3 MZM file computes zonal means covering 5 degree latitude bands for each calendar month. For this product there are 72 months of data from May 1970 through April 1976. There are a total of 36 latitudinal bands, 18 in each hemisphere. Profile data are provided at 21 layers from 1013.25, 639.318, 403.382,254.517, 160.589, 101.325,63.9317, 40.3382, 25.4517, 16.0589, 10.1325, 6.39317,4.03382, 2.54517, 1.60589, 1.01325,0.639317, 0.403382, 0.254517, 0.160589 and 0.101325 hPa (measured at bottom of layer). NOTE: Some profiles have 20 layers and do not report the top most layer. Mixing ratios are reported at 15 layers from 0.5, 0.7, 1.0, 1.5, 2.0, 3.0, 4.0, 5.0, 7.0, 10.0, 15.0, 20.0, 30.0, 40.0 and 50.0 hPa (measured at middle of layer). The MZM product averages retrievals that meet the criteria for a good retrieval as determined by error flags in the Level 2 data. A good retrieval is defined as satisfying the following conditions: 1) Profile Error Flag = 0 or 1 (0 = good retrieval; 1 = solar zenith angle > 84 deg.) 2) Total Error Flags = 0, 1, 2 or 5 (0 = good retrieval; 1 = not used; 2 = solar zenith angle > 84 deg; large discrepancy between profile total and best total ozone) NOTE - Total error flag = 5 is anomalously applied at high latitudes and high solar zenith angle where B-Pair total ozone estimate is not as reliable as profile under these conditions. This error flag may be removed in future version of algorithm. The zonal means computed for each month are screened according to the following statistical criteria: 1) number of good retrievals for the month greater than or equal to 2/3 of the samples for a nominal month. 2) mean latitude of good retrievals less than or equal to 1 degree from center of latitude band. 3) mean time of good retrievals less than or equal to 4 days from center of month (i.e., day = 15)
- API
Veterans Employment
internal.open.piercecountywa.gov | Last Updated 2024-02-16T18:24:00.000ZEmployment levels and percentages of veterans and non-veterans in the labor force over time.
- API
NEW HORIZONS SDC PLUTO CRUISE RAW V2.0
data.nasa.gov | Last Updated 2023-01-26T20:54:05.000ZThis data set contains Raw data taken by the New Horizons Student Dust Counter instrument during the pluto cruise mission phase. This is VERSION 2.0 of this data set. SDC collected science data intermittently during the hibernation years following the Jupiter encounter, designated as the PLUTOCRUISE phase. There were also Annual Checkouts (ACOs), STIM calibrations, Noise calibrations, and an anomaly in November, 2007. SDC's main science data collection periods were during hibernation. During ACOs, science data are taken intermittently but the user must be careful in analyzing these data since there is usually more activity on the spacecraft during hibernation. STIM and Noise refer to scheduled calibrations and are done with a regular cadence of one per year after the Jupiter encounter; they occurred sporadically in the early years of the mission. Note that some SDC data files have the same stop and start time and a zero exposure time. The reason for this is that the start and stop time for SDC data files are the event times for the first and last events in the files, so for files that contain a single event, these two values are the same. The changes in Version 2.0 were re-running of the ancillary data in the data product, updated geometry from newer SPICE kernels, minor editing of the documentation, catalogs, etc., and resolution of liens from the December, 2014 review, plus those from the May, 2016 review of the Pluto Encounter data sets. New observations added with this version (V2.0) include ongoing cruise observations from August, 2014 through January, 2015.
- API
HS Dataset CARES Mortgage Program
internal.open.piercecountywa.gov | Last Updated 2021-09-23T16:44:24.000Z