Skip to main content
Every job on your careers site can appear on a map and be filtered by distance (“jobs near me”). To do that, inploi needs a precise point on the map — a latitude and longitude — for each role. This page explains where those coordinates come from for imported jobs, why some jobs can end up sharing the same map point, and how a bad location can be corrected.

​
Where coordinates come from

Most ATS feeds send inploi the text of a job’s location — some combination of address lines, town, city, postcode, and country — but not a reliable set of coordinates. A small number of integrations do send coordinates directly, but for the majority inploi has to work them out from the address text. inploi does this automatically during import. You do not need to set coordinates yourself.

​
How it works

1

Read the location

inploi takes the location fields sent by your ATS — address lines, town, city, postcode, and country — and combines them into a single address.
2

Check for a saved location

inploi keeps a shared list of addresses it has already placed on the map. If that exact address has been looked up before, the saved coordinates are reused straight away. This keeps imports fast and consistent, so two jobs at the same address always land on the same point.
3

Look up the address

If the address has never been seen before, inploi asks Google to find its coordinates. Google returns the best matching point for the address it was given.
4

Save for next time

The result is saved against that address, so any future job with the same location reuses it instead of being looked up again.
If a job comes in without a postcode, inploi can also read the postcode back from Google’s response and fill it in.

​
Why some jobs share the same map point

The quality of a job’s map point depends entirely on the quality of the location data your ATS sends. When the source location is precise — a full street address and postcode — the map point is precise. When it is vague, the point is vague. For example:
  • If several jobs only provide a city (with no street or postcode), they will all be placed at the centre of that city, on top of one another.
  • If several jobs share the same postcode but no street address, they will all sit on the same postcode point.
  • If a store or site name is used in place of a street address, every role at that site shares one point.
This is expected behaviour, not a fault: inploi can only be as accurate as the address it is given. Improving the location detail in the ATS is the most reliable way to spread these jobs out correctly.
Because inploi reuses saved coordinates for an address, the map point for a repeated address is fixed the first time it is looked up. Later imports of the same address reuse that saved point rather than looking it up again.

​
Correcting a bad location

If a job — or a group of jobs sharing an address — is showing in the wrong place on the map, inploi can set an override so that address always maps to the correct point. Once an override is in place, every current and future job with that address uses the corrected coordinates. If you notice a job in the wrong place, contact your Customer Success Manager with the job and the correct location. They can either help improve the location data in the ATS or apply an override for that address.