You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
You are viewing the article in preview mode. It is not live at the moment.
Home > RAW > Support > RAW Data FAQs > Location data on job records and unmapped locations
Location data on job records and unmapped locations
print icon

Job records that LinkUp determines to be remote or work from home, are marked as an unmapped location where the unmapped location field in our job records file is set to TRUE. When a job posting is considered to be remote, any other location data is not indexed. Additionally, when a job record lists multiple remote vacancies, we count only one remote vacancy for that job record.

When a job is not work from home or remote, but we cannot determine an exact location down to the city, state, and zip code, the job is listed as unmapped location = TRUE but with the location data that was indexed from the job record.

 

The unmapped location field has always been available in RAW2 and was backfilled on Market Reports when it was implemented.

 

In Market Reports, location data for unmapped locations will show as OTHER.

 

LinkUp is working on a solution to positively flag remote job records, for example, differentiating non-remote jobs in the city of Remote, Oregon from actual remote jobs.

Feedback
0 out of 0 found this helpful

scroll to top icon