Inspection
After we have setup the cshapes dataset to be compatible with the Time Editor plugin, we now can check for potential errors in the data set and see if we can fix them.
Start by Opening the Inspect Layer Vector -> Time Editor -> Inspect Layer
dialog.
Date Integrity and Geometric Integrity Check
The Checks for Date and Geometric Integrity should run without errors. This tells you that all date-values are entered in the correct format (YYYY-MM-DD) and all geometries are spatially valid (no self intersections or other). This shows already the high quality of the Cshapes data set.
Time Integrity
The Time Integrity check returns 15 errors.
We can export all the errors into a csv-file using the file-chooser under
the tabular views of the errors and pressing Export CSV
:
To inspect the potential errors it is best to filter by the common identifier
(in our case gwcode
).
Example France
One of the error will involve the common identifier code 220
(France). While the original datefield
has been set correctly the attribute gweday
apparently was not updated.
We can fix this by changing the field value to 27
and updating valid_to
accordingly (1919-06-27
).
After these edits the code of France (220
) will not show up in the Time Integrity
Check.
Serbia
Another example involves the code 340
for serbia.
As the date-integrity check states the feature with the id
126
results in
an error. This is correct from the point of view of the algorithm as there
is a missing date history from 1918-11-10
to 2006-06-06
. This obviously
is due to to the the lost sovereinity after the first world war and its dissolvement.
You can add this to the list of temporal exceptions for the Cshapes layer, for details refer to the Time Integrity Section in the Tutorial Basics.