If you have a list of locations in a spreadsheet you can use Import CSV to create them all as point markups in one go, rather than adding them one by one. You can also import into a custom content type, so each row arrives with the right attributes already filled in.
Before you start:
Your file must be a .csv file, no larger than 10MB, with up to 500 rows. If you have more than 500 records, split them across several files.
Every row needs a name, an X coordinate and a Y coordinate.
Coordinates should be in your project's Coordinate Reference System (CRS). See Understanding Sensat's Coordinate Reference System (CRS).
You'll need permission to add content to the project.
Step 1: Upload your CSV
Go to Content, open the folder that you want to add your content to and click the down arrow on the Upload content button, then select Import CSV.
Drag and drop your CSV into the upload area, or click browse to select it. Once added, you'll see the file name and size. Click the x to remove it and choose a different file.
Under Content type, choose what each row should be created as. Choose a standard point markup, or you can pick one of your project's custom content types.
If your file contains dates, pick which order they are displayed in the file. Don't worry about the separator for dates, we will automatically pick this up.
If your file has cells with more than one value, such as multiple choice options or several mentioned people, choose the separator used between those values: ; , / or |. Use the same separator throughout the file.
Click Next.
Step 2: Map & Preview
Next, tell Sensat which column in your CSV holds each piece of information.
On the left you'll see the list of Sensat attributes for the content type you chose, such as Name, Description, X coordinate and Y coordinate, plus any custom attributes. Next to each one, use the drop-down to select the CSV column that should fill it. Leave an attribute unmapped if your CSV doesn't contain that information.
As you map columns, the preview on the right updates so you can check your data before importing:
All rows shows every row in your file.
Issues shows only rows with a problem. Each problem cell is highlighted in red with a short explanation.
Tip: You can edit the fields directly in the preview to resolve the errors.
Common issues include:
Required field: a row is missing a name or coordinate.
Doesn't match attribute type/options: a coordinate or number attribute contains text, or a date that can't be read or a choice that isn't one of the attribute's options.
You can't continue until Name, X coordinate and Y coordinate are all mapped. When you're happy, click Import. Only valid rows are imported; rows with issues are skipped and listed at the end, so you can fix and re-import them.
Which attribute types can be imported?
Single line text, multi-line text, single choice, multiple choice, date, number, phone number, people and URL. People must be member's email addresses; groups can't be imported and members who aren't invited to the project will fail.
Date formats
Dates can be written day/month/year, month/day/year, year/month/day or year/day/month, with the parts separated by . , / - : or a space. Sensat detects the format automatically.
đĄ Tip: if you've just added a new attribute to your content type in another tab, reopen the drop-down and it will appear in the list.
Step 3: Results
Sensat will show progress while your points are created. Keep the window open until it finishes; larger files can take a little longer.
When it's done, you'll see:
How many items were imported successfully.
How many rows were skipped, with the reason for each (e.g. "Row 7: Missing field Content name").
If any rows were skipped, click Download failed rows as CSV. This gives you a file of just those rows with the error reason added, so you can correct them and import again. Click Done to close and see your new content.
Example: bringing in assets from another system
Import CSV is a quick way to get records out of an asset register or other system and onto your map, even if not every record has an accurate location yet. A typical workflow looks like this:
Set up a content type with attributes matching the fields you want to bring across, including one for each record's ID in the source system. See Setting up custom Content Types.
Export a CSV from the source system with a name, X and Y coordinates, the record ID and any other fields you need. If some records don't have coordinates yet, give them placeholder coordinates inside your project area, such as a single known point on site.
Import the CSV into its own folder, choosing your content type and mapping each column to its attribute.
Check positions on the map by linking the folder to a Workspace (see Adding and removing content to a Workspace), then move any placeholder points to their correct locations.
Export the corrected points as a CSV (see How to export Markups). The export includes each of your content type's attributes as its own column, so the updated locations can be matched back to the original records using the source ID.