- What is the Mean Job Proximity Index?
- What is the Population Count?
- What is the Population Density?
- What is the Land Area?
- What is the Percent who did not finish the 9th grade?
- What is the Student Teacher Ratio?
- What is the Median Earnings?
- What is the Number of Employees?
- What is the Percent Without Health Insurance?
- What is the Mean Environmental Health Hazard Index?
The median job proximity index of Fairfax County, VA was 40 in 2015.
Median Jobs Proximity Index
The jobs proximity index quantifies access to employment opportunities in a region. Values are percentile ranked and range from 0 to 100, with higher values corresponding to better access to jobs. Data is computed for U.S. counties by applying summary statistics across all census tracts present in a county and is current as of 2015.
The underlying index quantifies the accessibility of a given residential neighborhood as a function of its distance to all job locations within a census tract, with distance to larger employment centers weighted more heavily. Specifically, a gravity model is used, where the accessibility (Ai) of a given residential block-group is a summary description of the distance to all job locations, with the distance from any single job location positively weighted by the size of employment (job opportunities) at that location and inversely weighted by the labor supply (competition) to that location.
Jobs and Job Proximity Datasets Involving Fairfax County, VA
- API data.iowa.gov | Last Updated 2018-03-19T22:46:22.000Z
This dataset contains Iowa unemployment insurance benefit payments, weeks compensated, and number of benefit recipients by county. County data is based on the recipient’s place of residence. (2000 to date)
- API data.iowa.gov | Last Updated 2018-03-19T22:46:31.000Z
This dataset contains Iowa unemployment insurance benefit payments, weeks compensated, and number of benefit recipients by county. County data is based on the recipient’s place of residence.
- API data.iowa.gov | Last Updated 2018-03-19T22:47:18.000Z
The dataset provides vehicle (both motor vehicle and trailer) registration numbers and annual fees by year, county and vehicle types. Vehicle types include: Automobile, Bus, Moped, Motor Home - A, Motor Home - B, Motor Home - C, Motorcycle, Multi-purpose, Regular Trailer, Semi Trailer, Small Regular Trailer, Small Semi Trailer, Truck Tractor, Travel Trailer, Truck, Truck - Business Trade, and Truck - Weight and List.
- API data.iowa.gov | Last Updated 2018-03-19T22:53:30.000Z
This dataset contains Iowa unemployment insurance initial claims by county. County data is based on the claimant’s place of residence. (2011 to date)
- API data.iowa.gov | Last Updated 2018-03-19T22:50:30.000Z
This dataset provides budgeted expenditures for the counties within the State of Iowa beginning with FY 2004 (fiscal year ending 6/30/2004).
- API data.transportation.gov | Last Updated 2017-12-19T17:26:31.000Z
Contains all Basic Safety Messages (BSMs) collected during the Advanced Messaging Concept Development (AMCD) field testing program. For this project, all of the Part I BSM message fields were populated. Additional data fields were also added to the row to identify sender, time of communication, mode of communication, etc., allowing the consumer of this data set to accurately track messages through the system. All BSMs are generated by OBUs and ultimately received by the VCC Cloud server.
- API data.transportation.gov | Last Updated 2017-10-31T19:54:11.000Z
Contains all Basic Mobility Control Message (BMCMs) generated during the Advanced Messaging Concept Development (AMCD) field testing program. While there is no specific standard in existence that addresses the content of a BMCM, the following format was derived to control the configuration and content of BMMs requested from the vehicle. All BMCMs are generated by the VCC Cloud server and transmitted to OBU clients through either a DSRC or cellular communications channel.
- API data.iowa.gov | Last Updated 2018-03-19T22:49:53.000Z
This dataset contains is a list of Iowa features contained in the Geographic Names Information System (GNIS). The GNIS is the Federal standard for geographic nomenclature. The U.S. Geological Survey developed the GNIS for the U.S. Board on Geographic Names, a Federal inter-agency body chartered by public law to maintain uniform feature name usage throughout the Government and to promulgate standard names to the public. The GNIS is the official repository of domestic geographic names data; the official vehicle for geographic names use by all departments of the Federal Government; and the source for applying geographic names to Federal electronic and printed products of all types. See http://geonames.usgs.gov for additional information. The Geographic Names Information System contains information about physical and cultural geographic features of all types, current and historical, but not including roads and highways. The database assigns a unique, permanent feature identifier, the Feature ID, as a standard Federal key for accessing, integrating, or reconciling feature data from multiple data sets. The GNIS collects data from a broad program of partnerships with Federal, State, and local government agencies and other authorized contributors.
- API data.transportation.gov | Last Updated 2017-10-26T12:50:47.000Z
Contains all PVDs generated during the AMCD field testing program. The probe vehicle message is used to exchange status about a vehicle with other DSRC readers to allow the collection of information about a typical vehicle’s traveling behaviors along a segment of road. The exchanges of this message as well as the event which caused the collection of various elements defined in the messages are in Annex B of the SAE J2735 standard.
- API data.transportation.gov | Last Updated 2017-10-26T12:48:12.000Z
Contains all Basic Mobility Messages (BMMs) collected during the Advanced Messaging Concept Development (AMCD) field testing program. While there is no specific standard in existence that addresses the content of a BMM, the descriptive definitions of the variables were derived from the J2735 standard where applicable. All BSMs are generated by OBUs and ultimately received by the VCC Cloud server.