Hugging Face's logo

Datasets:
joey234
/
GPSBench

Tasks:
Question Answering
Modalities:
Text
Geospatial
Formats:
json
Languages:
English
Size:
10K - 100K
ArXiv:
Tags:
geospatial
gps
benchmark
geography
spatial-reasoning
coordinates
Libraries:
Datasets
pandas
Polars
License:
Dataset card Data Studio Files
xet
 Community
joey234 commited on
Commit
64dfdd9
·
verified ·
1 Parent(s): bc0f837

Add 18-task configs to README so HF can load + auto-generate Croissant

Browse files
Files changed (1) hide show
  1. README.md +146 -5
README.md CHANGED
@@ -14,11 +14,152 @@ tags:
14
  size_categories:
15
  - 10K<n<100K
16
  pretty_name: "GPSBench: GPS Reasoning Benchmark for LLMs"
17
- dataset_info:
18
- - config_name: pure_gps
19
- description: "Pure GPS track: coordinate manipulation tasks"
20
- - config_name: applied
21
- description: "Applied track: geographic reasoning tasks"
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
22
  ---
23
 
24
  # GPSBench: Do Large Language Models Understand GPS Coordinates?
 
14
  size_categories:
15
  - 10K<n<100K
16
  pretty_name: "GPSBench: GPS Reasoning Benchmark for LLMs"
17
+ configs:
18
+ - config_name: task11_missing_data
19
+ data_files:
20
+ - split: train
21
+ path: data/track_applied/splits/task11_missing_data_train.json
22
+ - split: validation
23
+ path: data/track_applied/splits/task11_missing_data_dev.json
24
+ - split: test
25
+ path: data/track_applied/splits/task11_missing_data_test.json
26
+ - config_name: task13_terrain_classification
27
+ data_files:
28
+ - split: train
29
+ path: data/track_applied/splits/task13_terrain_classification_train.json
30
+ - split: validation
31
+ path: data/track_applied/splits/task13_terrain_classification_dev.json
32
+ - split: test
33
+ path: data/track_applied/splits/task13_terrain_classification_test.json
34
+ - config_name: task1_place_association
35
+ default: true
36
+ data_files:
37
+ - split: train
38
+ path: data/track_applied/splits/task1_place_association_train.json
39
+ - split: validation
40
+ path: data/track_applied/splits/task1_place_association_dev.json
41
+ - split: test
42
+ path: data/track_applied/splits/task1_place_association_test.json
43
+ - config_name: task3_name_disambiguation
44
+ data_files:
45
+ - split: train
46
+ path: data/track_applied/splits/task3_name_disambiguation_train.json
47
+ - split: validation
48
+ path: data/track_applied/splits/task3_name_disambiguation_dev.json
49
+ - split: test
50
+ path: data/track_applied/splits/task3_name_disambiguation_test.json
51
+ - config_name: task5_relative_position
52
+ data_files:
53
+ - split: train
54
+ path: data/track_applied/splits/task5_relative_position_train.json
55
+ - split: validation
56
+ path: data/track_applied/splits/task5_relative_position_dev.json
57
+ - split: test
58
+ path: data/track_applied/splits/task5_relative_position_test.json
59
+ - config_name: task6_proximity
60
+ data_files:
61
+ - split: train
62
+ path: data/track_applied/splits/task6_proximity_train.json
63
+ - split: validation
64
+ path: data/track_applied/splits/task6_proximity_dev.json
65
+ - split: test
66
+ path: data/track_applied/splits/task6_proximity_test.json
67
+ - config_name: task7_route_analysis
68
+ data_files:
69
+ - split: train
70
+ path: data/track_applied/splits/task7_route_analysis_train.json
71
+ - split: validation
72
+ path: data/track_applied/splits/task7_route_analysis_dev.json
73
+ - split: test
74
+ path: data/track_applied/splits/task7_route_analysis_test.json
75
+ - config_name: task8_boundary_analysis
76
+ data_files:
77
+ - split: train
78
+ path: data/track_applied/splits/task8_boundary_analysis_train.json
79
+ - split: validation
80
+ path: data/track_applied/splits/task8_boundary_analysis_dev.json
81
+ - split: test
82
+ path: data/track_applied/splits/task8_boundary_analysis_test.json
83
+ - config_name: task9_spatial_patterns
84
+ data_files:
85
+ - split: train
86
+ path: data/track_applied/splits/task9_spatial_patterns_train.json
87
+ - split: validation
88
+ path: data/track_applied/splits/task9_spatial_patterns_dev.json
89
+ - split: test
90
+ path: data/track_applied/splits/task9_spatial_patterns_test.json
91
+ - config_name: task10_relative_position
92
+ data_files:
93
+ - split: train
94
+ path: data/track_pure_gps/splits/task10_relative_position_train.json
95
+ - split: validation
96
+ path: data/track_pure_gps/splits/task10_relative_position_dev.json
97
+ - split: test
98
+ path: data/track_pure_gps/splits/task10_relative_position_test.json
99
+ - config_name: task1_format_conversion
100
+ data_files:
101
+ - split: train
102
+ path: data/track_pure_gps/splits/task1_format_conversion_train.json
103
+ - split: validation
104
+ path: data/track_pure_gps/splits/task1_format_conversion_dev.json
105
+ - split: test
106
+ path: data/track_pure_gps/splits/task1_format_conversion_test.json
107
+ - config_name: task3_coordinate_system_transformation
108
+ data_files:
109
+ - split: train
110
+ path: data/track_pure_gps/splits/task3_coordinate_system_transformation_train.json
111
+ - split: validation
112
+ path: data/track_pure_gps/splits/task3_coordinate_system_transformation_dev.json
113
+ - split: test
114
+ path: data/track_pure_gps/splits/task3_coordinate_system_transformation_test.json
115
+ - config_name: task4_distance_calculation
116
+ data_files:
117
+ - split: train
118
+ path: data/track_pure_gps/splits/task4_distance_calculation_train.json
119
+ - split: validation
120
+ path: data/track_pure_gps/splits/task4_distance_calculation_dev.json
121
+ - split: test
122
+ path: data/track_pure_gps/splits/task4_distance_calculation_test.json
123
+ - config_name: task5_bearing_computation
124
+ data_files:
125
+ - split: train
126
+ path: data/track_pure_gps/splits/task5_bearing_computation_train.json
127
+ - split: validation
128
+ path: data/track_pure_gps/splits/task5_bearing_computation_dev.json
129
+ - split: test
130
+ path: data/track_pure_gps/splits/task5_bearing_computation_test.json
131
+ - config_name: task6_interpolation
132
+ data_files:
133
+ - split: train
134
+ path: data/track_pure_gps/splits/task6_interpolation_train.json
135
+ - split: validation
136
+ path: data/track_pure_gps/splits/task6_interpolation_dev.json
137
+ - split: test
138
+ path: data/track_pure_gps/splits/task6_interpolation_test.json
139
+ - config_name: task7_area_perimeter
140
+ data_files:
141
+ - split: train
142
+ path: data/track_pure_gps/splits/task7_area_perimeter_train.json
143
+ - split: validation
144
+ path: data/track_pure_gps/splits/task7_area_perimeter_dev.json
145
+ - split: test
146
+ path: data/track_pure_gps/splits/task7_area_perimeter_test.json
147
+ - config_name: task8_bounding_box
148
+ data_files:
149
+ - split: train
150
+ path: data/track_pure_gps/splits/task8_bounding_box_train.json
151
+ - split: validation
152
+ path: data/track_pure_gps/splits/task8_bounding_box_dev.json
153
+ - split: test
154
+ path: data/track_pure_gps/splits/task8_bounding_box_test.json
155
+ - config_name: task9_route_geometry
156
+ data_files:
157
+ - split: train
158
+ path: data/track_pure_gps/splits/task9_route_geometry_train.json
159
+ - split: validation
160
+ path: data/track_pure_gps/splits/task9_route_geometry_dev.json
161
+ - split: test
162
+ path: data/track_pure_gps/splits/task9_route_geometry_test.json
163
  ---
164
 
165
  # GPSBench: Do Large Language Models Understand GPS Coordinates?