Datasets Uploaded Directly by User – Client – Knowledge Base

Datasets Uploaded Directly by User – Client

Datasets uploaded as «dead» (static) tables must start with client_ to distinguish them from the rest, and to avoid conflicts between read and write permissions in the rest of the solution.

This is useful if you have data in e.g. Excel that you want to combine with other analyses. Be aware that datasets starting with client_ will not be updated unless you or someone else with access to the source file manually uploads a new version. You should therefore not use this method for data that needs to be updated more often than once per year.

Uploading Tabular Data (CSV)

Data in table format (such as CSV) has its own shortcut on the landing page (reached by clicking the InfoTiles logo in the upper left corner).

CSV upload shortcut on the InfoTiles landing page — The CSV/table upload shortcut is accessible from the landing page via the InfoTiles logo in the upper left corner.

Uploading Map Data

It is also possible to load your own map data while working in the map, using Add layer.

Add layer option in the map interface — Use «Add layer» in the map to load your own spatial data.

Followed by Upload file. It is recommended to use shapefile format as it automatically reprojects coordinates without pre-processing. Use the prefix client_ in the name and select Upload in chunks to avoid being blocked by a firewall.

Upload file dialog with Upload in chunks option — Select «Upload file» and choose «Upload in chunks» when uploading large or firewall-sensitive files.

Naming Conventions for User-Uploaded Datasets

A good practice when uploading your own dataset directly is to add a date at the end of the filename — either just the year, or the full date. The date format should be one of the following (y = digit of year, m = digit of month, d = digit of day):

yyyymmdd — This is a common way to write dates in the data world because it makes it easy to sort from newest to oldest or vice versa.
dd-mm-yyyy

In addition, give it a meaningful name that your colleagues will understand. Avoid spaces and periods in the name to prevent issues with system settings and file format interpretation.

Examples of good dataset names

client_watercourse_samples_2024
client_basement_floods_2018-2024
client_wastewater_zones_20230416 (i.e. the map was produced/published on 16 April 2023)
client_unidirectional_water_supply_16-04-2023 (i.e. the map was produced/published on 16 April 2023)

Datasets Uploaded Directly by User – Client