Manual
Alarm
Burst Data
Dashboard
Data Source
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
Manual Inclinometer
Reports
Site Setup
Validation
QA/QC
Project
Prism
Validation
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
Future data imported into VDV
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
- FAQ
- Server Side
- Future data imported into VDV
Future data imported into VDV
Updated
by Andres Andresson
In rare occasions data sources can produce erroneous data with future timestamp that is imported into the VDV database.
db.robot.c is designed to know what timestamps already have been imported into the database and will not import new data unless the timestamp is newer then the latest timestamp in the database. When data with future timestamps have been imported into the database this becomes a problem because no new data will be imported until that date has passed.
There is a three step solution to this problem:
- Fix the data source and make sure that the raw .dat files does not have any future dates in it.
- Go to db.robot.c > Data Handling > Delete Data From Station
Select From and To dates from the Date Picker and make sure that the future data is within that range and delete the data - Go to db.robot.c > Data Handling > Change Last Timestamp
Change the Latest Timestamp to date and time prior to the latest that that is correctly in the database.
db.robot.c will import all data in the raw .dat file that is newer the configured Latest Timestamp.NOTE: The Data Handling feature is only available in VDV 2016 and later