Manual
Alarm
Burst Data
Dashboard
Data Source
Manual Inclinometer
Loadsensing
Ackcio
CSI
File Import
Geokon
SAA
Sigicom
Total Stations
Waste Management
Profound
Axilog
GSS
Webcam import
Displacement Graph
GIS
Historical Graphs
Real Time Display
Virtual Variables
SSO
Setup Azure AD for VDV
Setup Single Sign-On in VDV
Single Sign-On setup checklist
Manual provider setup
Analysis
API
Contacts
Contact Groups
Completeness
Data Export Task
Documents
Download Data
Localization
Notes
Month Overview
Reports
Site Setup
QA/QC
Project
Prism
Update Overview
Users in VDV
Manual Import
Setting up a webcam
Embed API
Webcam
User interface
License Overview
Graph Configuration
Videos
Guides
After install action list
Install VDV on-premise
Creating a new project
Installing scheduled tasks
Restarting the Vista Data Vision System
Exporting site and unit lists from db.robot.c
Exporting the settings from the File Converter
Muting sounds in VDV
Updating VDV with the store in offline mode
Migrate/Move Vista Data Vision to a new server
FAQ
Server Side
File Converter gets empty
Update header - new sensors added to the data file
Import modified or historical data
The VI Not Executable
Email subject contains information from the mail server
Webcam not importing pictures
How to configure Text Message Service
Run tasks minimized
Units
System Requirements
Backing up VDV
Front end
How to extend VDV Timeout
System validation after PHP 8 update
- All Categories
-
- Data Handling
Data Handling
Updated
by Ragnar Tryggvason
There are many reasons why the wrong data or erroneous data ends up in the .dat files that is being imported into the VDV database. This tip shows how Data Handling can be used to take care of this problem.
- Open up the .dat files that is being imported into db.robot.c using text editor (Notepad++ recommended) and remove the bad or erroneous data.
- Delete the period containing the bad data from the VDV database.
Go to: db.robot.c > Edit > Data Handling > Select the correct Site > Click on Delete Data from Station
Select the time period containing the bad data using the From and To date pickers.
NOTE: It is alright if some data that is OK is deleted as long it is still in the raw .dat file
- Change the Latest Timestamp in db.robot.c.
Go to: db.robot.c > Edit > Data Handling > Select the correct Site > Change Last Timestamp
Using the date picker select a timestamp that is older than the From Timestamp in Step 2
- Now the .dat file has been fixed, data has been deleted from the database and the Latest Timestamp has been updated. This will force the db.robot.c to read this time period in the data file again and import the data lines again that are not in the database.
