Upload Configuration

Configure upload sets for importing data in the Upload section of Configuration. Only administrators can manage upload sets.

This documentation helps you with:

• Preparing CSV files with the correct structure and formats
• Creating and managing upload sets via the interface

Table of contents

This documentation is divided into two parts:

Preparing CSV files

• CSV file requirements - Technical specifications for the CSV file

Working with upload sets

• Upload sets table - Overview of all upload sets
• Create upload set - Step-by-step instructions
• Load and view file - How to load a file
• Manage upload set - Add, edit, and delete
• Tips and troubleshooting - Help with problems

CSV file requirements

Ensure your CSV file has the correct structure:

• Use commas as the separator
• The first row contains column headers
• Each subsequent row contains one object
• Null values are allowed as NA, N/A, or an empty field

Required columns

• geometry (text, WKT): geometry as POINT(x y) or LINESTRING(x1 y1, x2 y2, ...)
  • WKT (Well-Known Text) is an OGC standard format for representing geometries
  • Precision: use a maximum of 6 decimals for lon/lat coordinates (for example 5.073885). This gives a precision of approximately 10 cm, which is sufficient for traffic measurements and location determination.
  • Examples:
    • Point: POINT(5.073885 5.073885) (lon lat, for example Utrecht)
    • Line: LINESTRING(5.073885 5.073885, 5.076046 52.069516) (multiple lon lat points)
• entity_type (text): entity type. Available options: car, bicycle, pedestrian
• metric_type (text): metric type. Available options: volume, speed, traveltime
• source (text): origin of the data, for example kwc, opendata, overig
• date (text): date in format YYYY-MM-DD, for example 2025-01-15
• time (text): time in format HH:mm, for example 13:00
• period_duration (integer): duration of the measurement period in seconds (automatically converted to minutes). Available options: 60 (1 minute), 300 (5 minutes), 900 (15 minutes), 3600 (1 hour)
• metric_value (decimal): measured value. Must be > 0 (or exactly 0 for volume)
  • If metric_type = volume: absolute counts (automatically converted to per hour)
  • If metric_type = speed: km/h
  • If metric_type = traveltime: seconds
• client_id (text): unique identifier of the measurement point or segment
• client_name (text): readable name of the measurement point or segment

Unique ID for measurement locations:

When processing upload files, rows are grouped based on the combination of geometry, entity_type, and metric_type. This means that multiple rows with the same geometry, entity_type, and metric_type are merged into one metadata item, regardless of the client_id.

How the unique ID is determined differs between points and lines:

• For points: client_id is used as the unique ID for the measurement point (with fallback to id if client_id is missing)
  • If multiple rows have the same geometry, entity_type, and metric_type, they are grouped and the client_id of the first row is used
• For lines: client_id is stored in the metadata and used for display, but the unique ID for line objects is generated automatically based on the combination of geometry, entity_type, and metric_type
  • This means that lines with the same geometry, entity_type, and metric_type get the same ID, regardless of the client_id

Important: Use unique combinations of geometry, entity_type, and metric_type per measurement location, or ensure that rows with the same combination also have the same client_id to avoid confusion.

Examples

Download voorbeeld upload bestanden.zip for complete sample files.

Point measurement (volume)

geometry,entity_type,metric_type,source,date,time,period_duration,metric_value,client_id,client_name
"POINT(4.9000 52.3700)",car,volume,kwc,2024-01-15,08:00,900,120,P123,Sensor A

Line measurement (traveltime)

geometry,entity_type,metric_type,source,date,time,period_duration,metric_value,client_id,client_name
"LINESTRING(4.9000 52.3700, 4.9100 52.3750)",car,traveltime,opendata,2024-01-15,08:00,300,420.5,L456,Segment B

Common errors and solutions

• Missing required column: add the column or fill it in.
• geometry not in WKT format: use POINT(x y) for points or LINESTRING(x1 y1, x2 y2, ...) for lines.
• Incorrect column order: ensure the columns are in the correct order (see examples above).

Upload sets table

The table shows all upload sets with:

• Upload set name
• Created (date and time when the upload set was created)
• Last edited (date and time of the last change, or ”-” if it has not been edited)
• Actions (add upload, edit name, delete)

Creating an upload set

1. Navigate to Configuration > Upload
2. Click the “Create upload set” button (top right)
3. Fill in the form:
   • Set name: Give the upload set a clear name
   • Load file: Select or drag a CSV file (see Load and view file for details)
4. Review the loaded objects in the table and map
5. Click “Save”

Loading and viewing a file

There are two ways to load a CSV file for display in the table and map:

1. Drag & Drop

   • Drag a CSV file to the upload area
   • The file is automatically loaded and displayed in the table and map when you release it

2. Choose file

   • Click “Upload a file” or the upload area
   • Select a CSV file from your computer
   • The file is automatically loaded and displayed in the table and map

Supported formats

• CSV files: Only CSV files are supported
• Ensure the file has the correct structure

What you see after loading

After loading a file you see:

• Object table: Shows all loaded objects with columns for ID, Name, Entity type, Metric type, and number of new entries
• Map view: Visualises the uploaded objects on a map based on their geometry

Managing an upload set

Adding an upload to an upload set

1. Find the upload set in the table
2. Click the ”+” button (add upload to upload set)
3. Load a new CSV file for display in the table and map
4. Review the loaded objects
5. Click “Save”

Note: When adding an upload, you cannot change the upload set name.

Editing the upload set name

1. Find the upload set in the table
2. Click the edit button (pencil icon)
3. Change the upload set name
4. Click “Save”

Note: When editing the name, you cannot upload a new file.

Deleting an upload set

1. Find the upload set in the table
2. Click the delete button
3. Confirm the deletion

Note: Deleting an upload set removes all associated uploaded objects. This action cannot be undone.

Tips and troubleshooting

Tips for effective use

1. Check file format: Ensure your CSV file is correctly formatted according to the CSV file requirements
2. Review loaded objects: Check the objects in the table and map before clicking “Save”
3. Use clear names: Give upload sets logical names so you can later easily find which data they contain
4. Test first: Test with a small file before loading large datasets

Common issues

File is not loaded

• Check that the file is a CSV file
• Check the file size (maximum 100 MB)

Objects are not recognised

• Check that all required columns are present
• Check the data formats (date, time, coordinates)
• Check the column order

Error messages after loading

• Watch for any error messages that appear after loading
• Check the common errors above
• Contact an administrator if the problem persists