The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
Error code: DatasetGenerationError
Exception: ValueError
Message: Invalid string class label A
Traceback: Traceback (most recent call last):
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1767, in _prepare_split_single
example = self.info.features.encode_example(record) if self.info.features is not None else record
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/features/features.py", line 1935, in encode_example
return encode_nested_example(self, example)
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/features/features.py", line 1252, in encode_nested_example
{k: encode_nested_example(schema[k], obj.get(k), level=level + 1) for k in schema}
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/features/features.py", line 1252, in <dictcomp>
{k: encode_nested_example(schema[k], obj.get(k), level=level + 1) for k in schema}
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/features/features.py", line 1310, in encode_nested_example
return schema.encode_example(obj) if obj is not None else None
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/features/features.py", line 1098, in encode_example
example_data = self.str2int(example_data)
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/features/features.py", line 1035, in str2int
output = [self._strval2int(value) for value in values]
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/features/features.py", line 1035, in <listcomp>
output = [self._strval2int(value) for value in values]
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/features/features.py", line 1056, in _strval2int
raise ValueError(f"Invalid string class label {value}")
ValueError: Invalid string class label A
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1391, in compute_config_parquet_and_info_response
parquet_operations, partial, estimated_dataset_info = stream_convert_to_parquet(
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 990, in stream_convert_to_parquet
builder._prepare_split(
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1629, in _prepare_split
for job_id, done, content in self._prepare_split_single(
File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1786, in _prepare_split_single
raise DatasetGenerationError("An error occurred while generating the dataset") from e
datasets.exceptions.DatasetGenerationError: An error occurred while generating the datasetNeed help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
image image | label class label |
|---|---|
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
3Derventa_B_5m_tele | |
3Derventa_B_5m_tele | |
3Derventa_B_5m_tele | |
3Derventa_B_5m_tele | |
4Derventa_C_5m_dron | |
4Derventa_C_5m_dron | |
4Derventa_C_5m_dron | |
4Derventa_C_5m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
3Derventa_B_5m_tele | |
3Derventa_B_5m_tele | |
3Derventa_B_5m_tele | |
3Derventa_B_5m_tele | |
3Derventa_B_5m_tele | |
3Derventa_B_5m_tele | |
4Derventa_C_5m_dron | |
4Derventa_C_5m_dron | |
4Derventa_C_5m_dron | |
4Derventa_C_5m_dron | |
4Derventa_C_5m_dron | |
4Derventa_C_5m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
3Derventa_B_5m_tele | |
3Derventa_B_5m_tele | |
3Derventa_B_5m_tele | |
3Derventa_B_5m_tele | |
4Derventa_C_5m_dron | |
4Derventa_C_5m_dron | |
4Derventa_C_5m_dron | |
4Derventa_C_5m_dron | |
4Derventa_C_5m_dron | |
4Derventa_C_5m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
0Derventa_A_10m_dron | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
1Derventa_A_5m_tele | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron | |
2Derventa_B_5m_dron |
The dataset is organised into directories coresponding to the dates when the images were taken.
Each directory has a sufix either '01' or '02' each corresponding to images taken by drone, or handheld camera, respectively.
Every directory is further divided into subdirectories named as letters of English alphabet (ex 'A', 'B', 'X', ...). These letters identify lots from which the images were taken.
Every lot directory is dividet into numbered direcotries that represent samples from each lot ex('01', '02', ..), the subdirectory '00' represents images of whole lots or images of the lots taken at the highest permisible altitute.
Each image file taken by the drone is named numericaly, where number represents the altidute at which the image is taken where '0 m' altidute is the ground level of the lot and then numbered sequentialy as they were taken. Each image file taken by handheld camera is named incrementaly and sequentialy by the camera, these filenames were retained.
- Downloads last month
- 18