- 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
Índice de Gobierno Digital 2018 entidades orden nacional
www.datos.gov.co | Last Updated 2024-04-20T20:18:18.000ZEl Índice de Gobierno Digital permite medir el desempeño y cumplimiento de las entidades públicas en la Política de Gobierno Digital. Este Índice permite al Ministerio de Tecnologías de la Información y las Comunicaciones determinar los avances específicos en cada temática de la Política de Gobierno Digital, buenas prácticas de implementación y estrategias focalizadas de acompañamiento. Así mismo, la información generada a través del Índice de Gobierno Digital permite a las entidades públicas tomar decisiones y definir acciones orientadas a mejorar su desempeño y cumplimiento de la Política de Gobierno Digital.
- 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
Election Results, Special Election Runoff, February 3, 2015
data.fultoncountyga.gov | Last Updated 2024-01-30T22:52:06.000ZThis data set consists of all Fulton County Election results from the Special Election Runoff, February 3, 2015, to present. Included with each record is the race, candidate, precinct, number of election day votes, number of absentee by mail votes, number of advance in person votes, number of provisional votes, total number of votes, name of election, and date of election. This data set is updated after each election.
- API
NEW HORIZONS SDC JUPITER ENCOUNTER CALIBRATED V4.0
data.nasa.gov | Last Updated 2023-01-26T20:41:44.000ZThis data set contains Calibrated data taken by the New Horizons Student Dust Counter instrument during the Jupiter encounter mission phase. This is VERSION 4.0 of this data set. For the Jupiter encounter mission phase, SDC collected no science data during the Jupiter flyby, as the requisite spacecraft configuration prevented SDC from operating. There were some very sparse data taken from December, 2006 through April, 2007, and some of very short (or zero) duration after the Jupiter flyby from April, 2007 through June, 2007. The changes in Version 4.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. No new observations were added with Version 4.0.
- 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
Elections: Applications, Line, September 2020 Election
sharefulton.fultoncountyga.gov | Last Updated 2023-01-30T16:56:12.000ZThis dataset contains information on absentee ballot applications for the September 29, 2020 Special Election.
- API
Election Results, Special Election Runoff, December 5, 2017
data.fultoncountyga.gov | Last Updated 2024-01-30T22:52:27.000ZThis data set consists of all Fulton County Election results from the Special Election Runoff, December 5, 2017 to present. Included with each record is the race, candidate, precinct, number of election day votes, number of absentee by mail votes, number of advance in person votes, number of provisional votes, total number of votes, name of election, and date of election. This data set is updated after each election.
- API
Campaign Finance Disclosure Expense Data Current State
data.pa.gov | Last Updated 2019-04-16T21:25:15.000ZThis file contains information about expenditures made by candidates, lobbyists or committees for the purpose of influencing elections. It includes the identification number of the filer and information about the election (s) and filing cycle (s) during which expenditures were made, as well as general information about the payees. The data is also available and searchable on www.campaignfinanceonline.pa.gov.