Location Overview

AdeptID supports locations in the United States at the city, county, metropolitan area, state and national levels.

Location Schema

AdeptID’s location schema uses standard US Government taxonomies. We use FIPS (Federal Information Processing Standard) codes as IDs.

Implementation tip: For most job search and analytical use cases, we recommend using a Metropolitan Statistical Area (MSA) as the search region. MSAs are defined by the US government as a city and economically connected surrounding communities. Note that MSAs may cross state boundaries and some rural areas are not part of any MSA.

FIELD	TYPE	SHORT DESCRIPTION
`city_name`	`string`	Name of the city.
`county_fips`	`string`	Code of the county containing the specified location.
`county_name`	`string`	Name of the county containing the specified location.
`msa_fips`	`string`	Code of the MSA containing the specified location.
`msa_name`	`string`	Official name of the MSA containing the specified location.
`metro`	`string`	Common name of the metropolitan area. In most cases, the metro is the name of the largest city in the MSA.
`state_abbreviation`	`string`	Two letter abbreviations of the state containing the specified location.
`state_fips`	`string`	2 digit code of the state containing the specified location.
`state_name`	`string`	Name of the state containing the specified location.
`geo_coordinates`	`object`	Latitude and longitude of the metro. See below for schema information.
`postal_code`	`string`	Postal code for an address.
`street_address`	`array of strings`	Individual lines of a mailing address.

Geo Coordinates

Locations include geographic coordinates for the center of the associated MSA.

FIELD	TYPE	SHORT DESCRIPTION
`latitude`	`float`	Latitude of the MSA.
`longitude`	`float`	Longitude of the MSA.

Location Example

{
	"city_name": "Jersey City",
	"county_fips": "34017",
	"county_name": "Hudson",
	"msa_common_name": "New York, NY",
	"msa_fips": "35620",
	"msa_name": "New York-Newark-Jersey City, NY-NJ-PA",
	"state_abbreviation": "NJ",
	"state_fips": "34",
	"state_name": "New Jersey"
}

Location Taxonomy

Use Cases for Location Taxonomy

Location Standardization: AdeptID classifies locations, taking in city, state or metropolitan area and returning a full set of locational metadata. This use case is satisfied with Location Search.
Analysis of Occupational Data: AdeptID provides occupational metadata such as demographics, supply and demand which vary by location. This use case is satisfied with Occupation Metadata.
Filtering of Job and Candidate Results: When searching against a feed of jobs or candidates, users may filter results to only include those in specific locations.

Location Taxonomy Overview

The locations in the AdeptID location taxonomy and data model include:

LOCATION TYPE	DESCRIPTION
`city`	Individual cities and towns. In some cases, APIs recognizes neighborhoods which are not official political designations as cities. Cities do not have IDs according to the FIPS information systems.
`county`	Counties are composed of a set of one or more cities. Each county has a unique FIPS code.
`state`	US States, territories and Washington, DC. Each state has a unique FIPS code.
`MSA`	Metropolitan Statistical Areas are region that consists of a city and surrounding communities linked by social and economic factors. They are defined by US Government and each MSA has a unique FIPS code. Note that MSAs may cross state boundaries (e.g. the New York MSA includes parts of Connecticut, New Jersey, and Pennsylvania) and some areas (particularly rural ones) may not be a part of any MSA.
`country`	Nations. Currently, AdeptID supports US locations only.

Canonical Locations

A list of the `MSAs' or metro areas supported by AdeptID is linked here.