Saltar al contenido
← Todos los conjuntos de datos

H-1B LCAs Listing a Georgia Secondary Worksite

H-1B (and H-1B1/E-3) labor condition applications certified for jobs based outside Georgia that also list a Georgia worksite, each fiscal year, statewide and by county.

Cobertura de años
2020–2025
Actualización
annual
Versión
1.0.0
Hash del esquema
9178df3c9eec

Niveles de detalle disponibles

Estado · predeterminadoCondado

Resumen

H-1B labor condition applications (LCAs) - and the H-1B1 (Chile, Singapore) and E-3 (Australia) applications on the same form - that the U.S. Department of Labor certified for a job whose FIRST worksite is outside Georgia but that also list a worksite in Georgia, by federal fiscal year: statewide by occupation group and visa program, and by the county of each listed Georgia worksite. These LCAs are the ones h1b_lca_positions (which counts each LCA at its first worksite) leaves out. From OFLC's LCA disclosure data and annual worksite files, FY2020-FY2025. The count of LCAs is exact; their positions are an upper bound on the positions that may work in Georgia, and a listed worksite is not proof of a hire.

Granularidad de fila: Una fila por year, county_fips, occupation_group, visa_class.

Métrica clave

num_applications — LCAs Listing a Georgia Secondary Worksite (count)

El valor principal que la mayoría de las consultas busca.

Variables

Todas las columnas de la tabla de hechos. El código es el nombre exacto del campo que devuelve la API.

ColumnaTipoUnidadRango¿Nulo?Descripción
yearYearinteger——noFederal fiscal year (October 1 - September 30; FY2025 = October 1, 2024 - September 30, 2025) of DOL's determination on the LCA, NOT the calendar year. FY2020-FY2025; FY2026 is withheld until DOL's full-year worksite file (its partial extract is incomplete). FY2020 is not comparable with later years: DOL's FY2020 filings list extra worksites about half as often (see limitations).
Descripción completa
Federal fiscal year (October 1 - September 30; FY2025 = October 1, 2024 - September 30, 2025) of DOL's determination on the LCA, NOT the calendar year. FY2020-FY2025; FY2026 is withheld until DOL's full-year worksite file (its partial extract is incomplete). FY2020 is not comparable with later years: DOL's FY2020 filings list extra worksites about half as often (see limitations).
county_fipsCounty FIPSstring——yes5-digit FIPS of a Georgia county where the LCA lists a worksite. NULL on statewide rows. An LCA listing worksites in several Georgia counties counts in each, so county rows do not sum to the statewide row (see limitations). Where the worksite street address geocodes with certainty to another county and a second sign agrees (DOL's county holds under 5% of the worksite ZIP's residents, or the address lies at least 500 m from DOL's county in a county holding some of the ZIP's residents), the address's county replaces DOL's (900 worksite rows); it also fills 415 counties DOL left blank. Where DOL's stated county is impossible for the worksite ZIP code (none of the ZIP's 2020 population lives there), it is replaced by the ZIP's county only when certain - at least 99% of the ZIP in that county and the city confirming the ZIP (9 worksite rows); 37 worksite rows that fail the test keep DOL's county (see limitations). Where DOL left the county blank (FY2025 fourth quarter) it comes from the street address or, failing that, the ZIP code's population-dominant county.
Descripción completa
5-digit FIPS of a Georgia county where the LCA lists a worksite. NULL on statewide rows. An LCA listing worksites in several Georgia counties counts in each, so county rows do not sum to the statewide row (see limitations). Where the worksite street address geocodes with certainty to another county and a second sign agrees (DOL's county holds under 5% of the worksite ZIP's residents, or the address lies at least 500 m from DOL's county in a county holding some of the ZIP's residents), the address's county replaces DOL's (900 worksite rows); it also fills 415 counties DOL left blank. Where DOL's stated county is impossible for the worksite ZIP code (none of the ZIP's 2020 population lives there), it is replaced by the ZIP's county only when certain - at least 99% of the ZIP in that county and the city confirming the ZIP (9 worksite rows); 37 worksite rows that fail the test keep DOL's county (see limitations). Where DOL left the county blank (FY2025 fourth quarter) it comes from the street address or, failing that, the ZIP code's population-dominant county.

Se une a counties; agrega sus columnas de etiqueta.

occupation_groupOccupation Groupstring——noOccupation group of the job (SOC): software developers, other computer/math, engineering, management/business, education/health, other, all.
Descripción completa
Occupation group of the LCA's job, from its SOC code, with the groups of h1b_lca_positions: 'software_developers' (2018 SOC 15-1252 and its 2010 predecessors 15-1132 / 15-1133), 'other_computer_mathematical' (other SOC 15), 'architecture_engineering' (SOC 17), 'management_business_finance' (SOC 11 and 13), 'education_health' (SOC 25, 29, 31), 'other', 'all'. Statewide rows only; county rows are 'all'.
7 valores permitidos
  • all — total / agregado
  • software_developers
  • other_computer_mathematical
  • architecture_engineering
  • management_business_finance
  • education_health
  • other
visa_classVisa Programstring——noLCA program: H-1B, H-1B1 Chile, H-1B1 Singapore, E-3, all.
Descripción completa
The program the LCA supports: 'h1b', 'h1b1_chile', 'h1b1_singapore', 'e3_australia'; 'all' = every program. Filter to 'h1b' for H-1B alone. Statewide rows only; county rows are 'all'.
5 valores permitidos
  • all — total / agregado
  • h1b
  • h1b1_chile
  • h1b1_singapore
  • e3_australia
num_applicationsLCAs Listing a Georgia Secondary Worksiteintegercount—yesCertified LCAs whose first worksite is outside Georgia that list a Georgia worksite.
Descripción completa
Number of labor condition applications DOL certified in the fiscal year (DOL's rule: certified, including those withdrawn later the same year) whose first worksite is outside Georgia and that list at least one Georgia worksite; on a county row, those listing a worksite in that county. Exact. None of these LCAs is in h1b_lca_positions.
num_positions_certifiedPositions on Those LCAsintegercount—yesPositions certified on those LCAs - an upper bound on the positions that may work in Georgia.
Descripción completa
Worker positions DOL certified on those LCAs (TOTAL_WORKER_POSITIONS, DOL's counting rule). An UPPER BOUND on the positions that may work in Georgia: the positions may work at any of the LCA's worksites in any state, and DOL lists the full count at each site, so no Georgia share can be separated. DOL counts these positions in the first worksite's state, not Georgia.

Filtros

Parámetros de consulta que acepta el endpoint de hechos. Los valores separados por comas son OR dentro de un parámetro; varios parámetros se combinan con AND.

ParámetroTipoValores permitidosNotas
yearyear_exactcualquier valor—
year_minyear_rangecualquier valor—
year_maxyear_rangecualquier valor—
detaildetailcountiesstatesenum validado, predeterminado: states
county_fipsforeign_keycualquier valorvalores múltiples
occupation_groupcategorical
7 valores permitidos
  • all
  • software_developers
  • other_computer_mathematical
  • architecture_engineering
  • management_business_finance
  • education_health
  • other
valores múltiples, enum validado
visa_classcategoricalallh1bh1b1_chileh1b1_singaporee3_australiavalores múltiples, enum validado

Ejemplos de solicitudes

Ejecútalos contra la URL base: devuelven datos en vivo.

All rows (first page), states level

curl "https://georgiacivicdata.org/api/v1/immigration/h1b_lca_secondary_worksites"

states data for 2025

curl "https://georgiacivicdata.org/api/v1/immigration/h1b_lca_secondary_worksites?year=2025"

Filtered to occupation_group = software_developers for 2025

curl "https://georgiacivicdata.org/api/v1/immigration/h1b_lca_secondary_worksites?year=2025&occupation_group=software_developers"

One county (FIPS 13121), 2025

curl "https://georgiacivicdata.org/api/v1/immigration/h1b_lca_secondary_worksites?county_fips=13121&year=2025&detail=counties"

Download 2025 as CSV

curl "https://georgiacivicdata.org/api/v1/immigration/h1b_lca_secondary_worksites?year=2025&format=csv"

Notas y limitaciones

Manejo de NULL

  • El cero es un valor real y reportado.

Limitaciones

Three cautions. County rows count an LCA in every Georgia county where it lists a worksite, so never add counties up: use the statewide row for Georgia. Positions are an upper bound: an LCA's positions may work at any of its worksites, in any state. FY2020 is not comparable with later years: DOL's FY2020 filings list extra worksites about half as often, so the FY2020 to FY2021 rise is not growth. Scope: an LCA is counted here when its FIRST worksite - the one DOL reports as the state of employment - is outside Georgia and it lists at least one other worksite in Georgia. Such LCAs are NOT in h1b_lca_positions, which counts each LCA once at its first worksite; the two topics' LCAs never overlap, so h1b_lca_positions' certified applications (case_status 'certified' plus 'certified_withdrawn') plus this topic's num_applications are every certified LCA that lists a Georgia worksite. The first worksites are mostly in TX 2,883, CA 2,495, IL 1,751, NC 1,103, NJ 1,019 (LCAs, all years). An LCA is not a visa: certified positions are employer attestations approved before any USCIS petition, lottery or hire, and a listed worksite is a place the workers may be employed, not proof that anyone worked there. Federal fiscal years (October 1 - September 30), not calendar years: `year` is the fiscal year of DOL's determination on the labor condition application (LCA), with each year's quarterly disclosure files unioned and deduplicated by case number exactly as in h1b_lca_positions. Only LCAs DOL counts as certified are included (certified in the year, including those the employer withdrew later that year); withdrawn and denied LCAs are not, because DOL's FY2020 worksite file lists none of them. The Georgia worksites come from DOL's separate annual LCA worksite files, which list every worksite of an LCA. FY2020 is not comparable with later years and understates Georgia secondary worksites: DOL's FY2020 filings list a second worksite far less often - on 20% of certified LCAs, about 9%-11% of those decided October 2019 - March 2020, against 40%-44% in every later year - so do not read the FY2020 to FY2021 rise as growth. The FY2020 worksite file also has no rows for 9,095 of the year's 558,626 certified LCAs nationally (1.6%); the other years are complete (missing: FY2023 8). FY2026 is not published: DOL's FY2026 (third-quarter) worksite extract lists only about three quarters of the year's LCAs, so the year will be added when DOL posts the full-year files. `num_applications` (LCAs) is the headline: it is exact. `num_positions_certified` is the positions DOL certified on those LCAs and is an UPPER BOUND on the positions that may work in Georgia: an LCA's positions may work at any of its worksites, and DOL's worksite file repeats the LCA's full position count at every site (on 99.8% of the LCAs with one Georgia site the Georgia site's worker count equals the LCA's positions), so no share of them can be attributed to Georgia. 18,271 of the 19,140 LCAs are for one position; the largest is for 70. DOL counts these positions in the first worksite's state. County rows count an LCA once in EACH Georgia county where it lists a worksite, so they are not additive: 416 LCAs of 19,140 (2.2%) list worksites in two or more Georgia counties and count in each, and the sum of the county rows differs from the statewide row by FY2020 +65 LCAs; FY2021 +50 LCAs; FY2022 +87 LCAs; FY2023 +63 LCAs; FY2024 +81 LCAs; FY2025 +81 LCAs. DOL's worksite file gives no order among an LCA's worksites, so there is no 'first Georgia worksite' to choose. Use the statewide row for Georgia's total, never a sum of counties. 3 LCAs whose Georgia worksites have no placeable county count in the statewide rows only. Each Georgia worksite's county is placed with the rules of h1b_lca_positions, applied to every listed Georgia worksite rather than to the first worksite. Worksite counties are checked against the worksite street address. The Census Bureau's geocoder located the Georgia worksite addresses in 2020 Census geography and matched 16,311 Georgia worksite rows (82%) to the same street address (house number and street, or intersection) in the same ZIP code. For 14,831 of them the address lies in DOL's county. For 900 Georgia worksite rows (972 positions certified; FY2020 91, FY2021 184, FY2022 215, FY2023 179, FY2024 134, FY2025 97) it lies in another county and a second sign agrees DOL's county is wrong - DOL's county holds under 5% of the worksite ZIP's residents, or the address lies at least 500 m from DOL's county, too far for a small placement error to explain, in a county where some of the ZIP's residents live, or property records confirm the address's county (26 Georgia worksite rows) - so the address's county is used. It also gives a county to 415 Georgia worksite rows DOL left blank (462 positions certified). For 165 Georgia worksite rows (201 positions certified) the address points to another county but lies within 500 m of DOL's county, where a geocoder can err, and DOL's county holds at least 5% of the ZIP's residents, so DOL's county is kept; some are DOL errors and some geocoder errors, and the geocoder alone cannot tell which. Where the address could not settle it, DOL's own worksite county is sometimes impossible for the worksite ZIP code - none of the ZIP's 2020 population lives in it. Such a county is replaced only when the right one is certain: at least 99% of the ZIP's population lives in one other county, and the worksite city is the ZIP's postal name or a Census place in that county, and not also a place or postal name in the stated county. 9 Georgia worksite rows (9 positions certified) were moved to the ZIP's county this way (FY2020 2, FY2021 1, FY2022 1, FY2023 1, FY2024 2, FY2025 2); they sit in 9 ZIP codes, 9 wholly inside the new county and 0 at least 99% inside it. Another 37 worksite rows (40 positions certified) keep a stated county that is impossible for their ZIP, because the evidence falls short of certain: in 6 the ZIP straddles a county line, in 13 the city does not match the ZIP (the ZIP itself may be mistyped) and in 18 the city lies on both sides of the county line. Their county may be wrong. DOL left the county blank on 532 Georgia worksite rows (its FY2025 fourth-quarter files omit counties): 415 are placed by their street address and 114 in the county holding most of the population of their ZIP code (2020 Census crosswalk). `occupation_group` and `visa_class` are the LCA's, as in h1b_lca_positions (occupation from the SOC code, 2010 and 2018 SOC joined for software developers). County rows are totals only (both categoricals 'all'). No suppression: rows are LCAs (job slots), not people, so the domain's county small-cell rule does not apply and every zero is real. Employers, secondary-entity names, wages and street addresses are not published.