Back

How to add sites to an existing data version

Site lists change: a store opens, a competitor's estate turns up late, an RFI answer arrives. You don't have to start a new data version for any of it - sites can be added to the one you're already working in.

One or two sites

On the Data page, Add new site above the table creates an empty site and opens the editor, where you fill in the name, fascia and location. Quickest route when it's a handful.

Add new site, for adding one site by hand
A batch of sites

Click the upload icon at the top right and choose Upload site data.

The upload icon, with Upload site data

In the window, switch from Create new to Add to existing. It names the version the sites will join - the one you have open - so there's no doubt about where they're going.

Upload site data on Add to existing, naming the version the sites go into

Then upload a CSV or XLSX, or use Search for sites to pull them from the location database. The screen shows the limits: file size and row count.

The import screen, with Upload file, Search for sites and the file limits

From here it's the normal import: map your columns to Sloc's fields, check the fascia names and duplicates, and import. That's covered in how to import sites: map fields, fascia and duplicate names.

The round trip

The tidiest way to make a lot of changes is to export, edit and bring it back. The download icon gives you the site data as CSV or XLSX - the same columns Sloc holds, so the file comes back in a shape it already understands.

The download icon on the Data page, with the site data exports

Edit it outside Sloc, then upload it with Add to existing. Download site data with change reasons adds why each site is as it is - handy when you're sending the file to a client or a colleague to check rather than editing it yourself.

After adding

New sites arrive without coordinates unless your file had them, so geocode them: on the Locate sites panel choose Geocode sites with missing lat/lon rather than all of them, which saves time and allowance.

Subsets built on the version pick up the new sites, but any scenario you've already run has not - re-run it before reading the results.

Pro tips
  • If the new sites change the analysis materially, consider a new data version instead. Adding to the version you've already reported from quietly changes what those results meant.

  • Export first, even when you're adding a handful. Matching the existing columns beats guessing them.

  • Check the fascia names on the way in. "Tesco Express" and "Tesco" as separate fascias will split a party in two.

  • Geocode missing sites only, and check the match confidence on the new ones before trusting them - see how to check geocoding quality and look up addresses.