- API
Nano Dust Analyzer Project
data.nasa.gov | Last Updated 2020-01-29T04:54:41.000Z<p> We propose to develop a new highly sensitive instrument to confirm the existence of the so-called nano-dust particles, characterize their impact parameters, and measure their chemical composition. Simultaneous theoretical studies will be used to derive the expected&nbsp; mass and velocity ranges of these putative particles to formulate science and measurement requirements for the future deployment of&nbsp; the proposed Nano-Dust Analyzer (NDA)&nbsp;</p> <p> Early dust instruments onboard Pioneer 8 and 9 and Helios spacecraft detected a flow of submicron sized dust particles coming from the direction of the Sun. These particles originate in the inner solar system from mutual collisions among meteoroids and move on&nbsp; hyperbolic orbits that leave the Solar System under the prevailing radiation pressure force. Later dust instruments with higher&nbsp; sensitivity had to avoid looking toward the Sun because of interference from the solar wind and UV radiation and thus contributed&nbsp; little to the characterization of the dust stream. The one exception is the Ulysses dust detector that observed escaping dust particles&nbsp; high above the solar poles, which confirm the suspicion that charged nanometer sized dust grains are carried to high heliographic&nbsp; latitudes by electromagnetic interactions with the Interplanetary Magnetic Field (IMF). Recently, the STEREO WAVES instruments&nbsp; recorded a large number of intense electric field signals, which were interpreted as impacts from nanometer sized particles striking the&nbsp; spacecraft with velocities of about the solar wind speed. This high flux and strong spatial and/or temporal variations of nanometer&nbsp; sized dust grains at low latitude appears to be uncorrelated with the solar wind properties. This is a mystery as it would require that&nbsp; the total collisional meteoroid debris inside 1 AU is cast in nanometer sized fragments. The observed fluxes of inner-source pickup ions&nbsp; also point to the existence of a much enhanced dust population in the nanometer size range.&nbsp;</p> <p> This new heliospherical phenomenon of nano-dust streams may have consequences throughout the planetary system, but as of yet no dust instrument exists that could be used to shed light on their properties. &nbsp;We propose to develop a dust analyzer capable to detect and&nbsp; analyze these mysterious dust particles coming from the solar direction and to embark upon complementary theoretical studies to&nbsp; understand their characteristics. The instrument is based on the Cassini Dust Analyzer (CDA) that has analyzed the composition of&nbsp; nanometer sized dust particles emanating from the Jovian and Saturnian systems but could not be pointed towards the Sun. By&nbsp; applying technologies implemented in solar wind instruments and coronagraphs a highly sensitive dust analyzer will be developed and&nbsp; tested in the laboratory. The dust analyzer shall be able to characterize impact properties (impact charge and energy distribution of&nbsp; ions from which mass and speed of the impacting grains may be derived) and chemical composition of individual nanometer sized&nbsp; particles while exposed to solar wind and UV radiation. The measurements will enable us to identify the source of the dust by&nbsp; comparing their elemental composition with that of larger micrometeoroid particles of cometary and asteroid origin and will reveal&nbsp; interaction of nano-dust with the interplanetary medium by investigating the relation of the dust flux with solar wind and IMF&nbsp; properties.&nbsp;</p> <p> Complementary theoretically studies will be performed to understand the characteristics of nano-dust particles at 1 AU to answer the&nbsp; following questions:&nbsp; - What is the speed range at which nanometer sized particles impact
- 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
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
Vital Signs: Time in Congestion - Corridor (Updated October 2018)
data.bayareametro.gov | Last Updated 2018-10-24T00:31:33.000ZVITAL SIGNS INDICATOR Time Spent in Congestion (T7) FULL MEASURE NAME Time Spent in Congestion LAST UPDATED October 2018 DATA SOURCE MTC/Iteris Congestion Analysis No link available CA Department of Finance Forms E-8 and E-5 http://www.dof.ca.gov/Forecasting/Demographics/Estimates/E-8/ http://www.dof.ca.gov/Forecasting/Demographics/Estimates/E-5/ CA Employment Division Department: Labor Market Information http://www.labormarketinfo.edd.ca.gov/ CONTACT INFORMATION vitalsigns.info@bayareametro.gov METHODOLOGY NOTES (across all datasets for this indicator) Time spent in congestion measures the hours drivers are in congestion on freeway facilities based on traffic data. In recent years, data for the Bay Area comes from INRIX, a company that collects real-time traffic information from a variety of sources including mobile phone data and other GPS locator devices. The data provides traffic speed on the region’s highways. Using historical INRIX data (and similar internal datasets for some of the earlier years), MTC calculates an annual time series for vehicle hours spent in congestion in the Bay Area. Time spent in congestion is defined as the average daily hours spent in congestion on Tuesdays, Wednesdays and Thursdays during peak traffic months on freeway facilities. This indicator focuses on weekdays given that traffic congestion is generally greater on these days; this indicator does not capture traffic congestion on local streets due to data unavailability. This congestion indicator emphasizes recurring delay (as opposed to also including non-recurring delay), capturing the extent of delay caused by routine traffic volumes (rather than congestion caused by unusual circumstances). Recurring delay is identified by setting a threshold of consistent delay greater than 15 minutes on a specific freeway segment from vehicle speeds less than 35 mph. This definition is consistent with longstanding practices by MTC, Caltrans and the U.S. Department of Transportation as speeds less than 35 mph result in significantly less efficient traffic operations. 35 mph is the threshold at which vehicle throughput is greatest; speeds that are either greater than or less than 35 mph result in reduced vehicle throughput. This methodology focuses on the extra travel time experienced based on a differential between the congested speed and 35 mph, rather than the posted speed limit. To provide a mathematical example of how the indicator is calculated on a segment basis, when it comes to time spent in congestion, 1,000 vehicles traveling on a congested segment for a 1/4 hour (15 minutes) each, [1,000 vehicles x ¼ hour congestion per vehicle= 250 hours congestion], is equivalent to 100 vehicles traveling on a congested segment for 2.5 hours each, [100 vehicles x 2.5 hour congestion per vehicle = 250 hours congestion]. In this way, the measure captures the impacts of both slow speeds and heavy traffic volumes. MTC calculates two measures of delay – congested delay, or delay that occurs when speeds are below 35 miles per hour, and total delay, or delay that occurs when speeds are below the posted speed limit. To illustrate, if 1,000 vehicles are traveling at 30 miles per hour on a one mile long segment, this would represent 4.76 vehicle hours of congested delay [(1,000 vehicles x 1 mile / 30 miles per hour) - (1,000 vehicles x 1 mile / 35 miles per hour) = 33.33 vehicle hours – 28.57 vehicle hours = 4.76 vehicle hours]. Considering that the posted speed limit on the segment is 60 miles per hour, total delay would be calculated as 16.67 vehicle hours [(1,000 vehicles x 1 mile / 30 miles per hour) - (1,000 vehicles x 1 mile / 60 miles per hour) = 33.33 vehicle hours – 16.67 vehicle hours = 16.67 vehicle hours]. Data sources listed above were used to calculate per-capita and per-worker statistics. Top congested corridors are ranked by total vehicle hours of delay, meaning that the highlighted corridors reflect a combination of slow speeds and heavy t
- API
United States Senate 2020
data.nashville.gov | Last Updated 2024-03-22T12:30:13.000ZUnofficial results for multiple Davidson County elections over time. (Use the Filter option by Election Date to limit results to a single election. Results may be delayed during elections.)
- API
Budget - 2021 Budget Recommendations - Positions and Salaries - Chart
data.cityofchicago.org | Last Updated 2020-10-20T21:46:25.000ZThis dataset includes recommended positions and salaries for 2021 by title (without names) and salary. The dataset is excerpted from the 2021 Budget Recommendations, which is the line-item budget proposed by the Mayor to the City Council for approval. Disclaimer: the “Total Budgeted Unit” column displays either A) the number of employees AND vacancies associated with a given position, or B) the number of budgeted units (ie. hours/months) for that position. “Position Control” determines whether Total Budgeted Units column will count employees and vacancies or hours/months. If a Position Control is 1, then employees and vacancies are displayed; if a Position Control is 0, then the total number of hours/months recorded is displayed. This dataset follows the format of the equivalent datasets from past years except that Division Code, Section Code, Subsection Code, and Position Control have changed from Number to Text (not all in the same year) in order to accommodate non-numeric values. For more information about the budget process, visit the Budget Documents page: http://j.mp/lPotWf.
- API
City of Des Moines Council Position No. 2
data.kingcounty.gov | Last Updated 2018-12-15T00:44:53.000Z(Initial posting at 8:15 p.m. on Election Day) Election results, November 2011 general election. To see when this was updated, click "About" on the far right of this page. See the schedule for when results are posted, at http://www.kingcounty.gov/elections/elections/201111/resultsschedule.aspx
- API
Parks Stats
performance.franklintn.gov | Last Updated 2023-08-23T15:31:51.000ZData consisting of Parks and Recreation Statistics from Franklin, Tennessee - including parks acreage, Healthy City rankings, and Tree City USA.
- API
Registered Public Corporations Disclosures: Four Biennial Period Window
data.ny.gov | Last Updated 2023-07-13T22:52:47.000ZData provided by Public Corporation in their Biennial Registration and Bi-monthly filings submitted to NYS Joint Commission on Public Ethics.
- 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.