Page MenuHomePhabricator

Help organisers repair broken coordinates
Open, Needs TriagePublic

Description

When T202280: prox_search failing finally made prox_search run again the result is that a lot of broken coordinates were revealed . These seem to be of the type where lat or lon is present but not the others.

The reasons differ see e.g. lat and lon are both entered into the lat field or lon is just missing (85697)

This seems to be particularly common for the be_vlg_(nl) dataset (Flanders on Dutch Wikipedia).

We should figure out a way of exposing these errors so that the organisers can repair them.

1Location data out of range: stdClass Object
2(
3 [country] => be-vlg
4 [lang] => fr
5 [id] => 13586
6 [lat] => 51.1703
7 [lon] =>
8)
9Location data out of range: stdClass Object
10(
11 [country] => be-vlg
12 [lang] => nl
13 [id] => 15112
14 [lat] => 51.16971
15 [lon] =>
16)
17Location data out of range: stdClass Object
18(
19 [country] => be-vlg
20 [lang] => nl
21 [id] => 15146
22 [lat] => 51.1692
23 [lon] =>
24)
25Location data out of range: stdClass Object
26(
27 [country] => be-vlg
28 [lang] => nl
29 [id] => 15216
30 [lat] => 51.15597
31 [lon] =>
32)
33Location data out of range: stdClass Object
34(
35 [country] => be-vlg
36 [lang] => nl
37 [id] => 15253
38 [lat] => 51.16733
39 [lon] =>
40)
41Location data out of range: stdClass Object
42(
43 [country] => be-vlg
44 [lang] => fr
45 [id] => 16199
46 [lat] => 51.10106
47 [lon] =>
48)
49Location data out of range: stdClass Object
50(
51 [country] => be-vlg
52 [lang] => nl
53 [id] => 28726
54 [lat] => 50.75177
55 [lon] =>
56)
57Location data out of range: stdClass Object
58(
59 [country] => be-vlg
60 [lang] => nl
61 [id] => 28864
62 [lat] => 50.75135
63 [lon] =>
64)
65Location data out of range: stdClass Object
66(
67 [country] => be-vlg
68 [lang] => nl
69 [id] => 77128
70 [lat] => 51.18714
71 [lon] =>
72)
73Location data out of range: stdClass Object
74(
75 [country] => be-vlg
76 [lang] => nl
77 [id] => 79736
78 [lat] => 51.275
79 [lon] =>
80)
81Location data out of range: stdClass Object
82(
83 [country] => be-vlg
84 [lang] => fr
85 [id] => 85697
86 [lat] => 51.08677
87 [lon] =>
88)
89Location data out of range: stdClass Object
90(
91 [country] => be-vlg
92 [lang] => nl
93 [id] => 85950
94 [lat] => 51.27316
95 [lon] =>
96)
97Location data out of range: stdClass Object
98(
99 [country] => be-vlg
100 [lang] => fr
101 [id] => 87162
102 [lat] => 51.01767
103 [lon] =>
104)
105Location data out of range: stdClass Object
106(
107 [country] => be-vlg
108 [lang] => nl
109 [id] => 87810
110 [lat] => 50.93213
111 [lon] =>
112)
113Location data out of range: stdClass Object
114(
115 [country] => be-vlg
116 [lang] => nl
117 [id] => 87848
118 [lat] => 51.15609
119 [lon] =>
120)
121Location data out of range: stdClass Object
122(
123 [country] => be-vlg
124 [lang] => nl
125 [id] => 88185
126 [lat] => 51.09384
127 [lon] =>
128)
129Location data out of range: stdClass Object
130(
131 [country] => be-vlg
132 [lang] => nl
133 [id] => 88320
134 [lat] => 51.09593
135 [lon] =>
136)
137Location data out of range: stdClass Object
138(
139 [country] => be-vlg
140 [lang] => nl
141 [id] => 88332
142 [lat] => 51.07319
143 [lon] =>
144)
145Location data out of range: stdClass Object
146(
147 [country] => be-vlg
148 [lang] => nl
149 [id] => 88376
150 [lat] => 51.10745
151 [lon] =>
152)
153Location data out of range: stdClass Object
154(
155 [country] => be-vlg
156 [lang] => nl
157 [id] => 89487
158 [lat] => 50.90016
159 [lon] =>
160)
161Location data out of range: stdClass Object
162(
163 [country] => be-vlg
164 [lang] => nl
165 [id] => 89507
166 [lat] => 50.90648
167 [lon] =>
168)
169Location data out of range: stdClass Object
170(
171 [country] => be-vlg
172 [lang] => nl
173 [id] => 89602
174 [lat] => 50.91047
175 [lon] =>
176)
177Location data out of range: stdClass Object
178(
179 [country] => be-vlg
180 [lang] => nl
181 [id] => 90018
182 [lat] => 50.95815
183 [lon] =>
184)
185Location data out of range: stdClass Object
186(
187 [country] => be-vlg
188 [lang] => nl
189 [id] => 90486
190 [lat] => 51.04288
191 [lon] =>
192)
193Location data out of range: stdClass Object
194(
195 [country] => fr
196 [lang] => fr
197 [id] => PA00091544
198 [lat] => 47.8114
199 [lon] =>
200)
201Location data out of range: stdClass Object
202(
203 [country] => pl
204 [lang] => pl
205 [id] => 603912
206 [lat] => 52.54475
207 [lon] =>
208)
209Location data out of range: stdClass Object
210(
211 [country] => pl
212 [lang] => pl
213 [id] => 616929
214 [lat] => 50.056052
215 [lon] =>
216)
217Location data out of range: stdClass Object
218(
219 [country] => pl
220 [lang] => pl
221 [id] => 617424
222 [lat] => 50.063414
223 [lon] =>
224)
225Location data out of range: stdClass Object
226(
227 [country] => pl
228 [lang] => pl
229 [id] => 625737
230 [lat] => 52.250417
231 [lon] =>
232)
233Location data out of range: stdClass Object
234(
235 [country] => pl
236 [lang] => pl
237 [id] => 625835
238 [lat] => 52.247778
239 [lon] =>
240)
241Location data out of range: stdClass Object
242(
243 [country] => pl
244 [lang] => pl
245 [id] => 625838
246 [lat] => 52.247778
247 [lon] =>
248)
249Location data out of range: stdClass Object
250(
251 [country] => pl
252 [lang] => pl
253 [id] => 648913
254 [lat] => 54.009944
255 [lon] =>
256)
257Location data out of range: stdClass Object
258(
259 [country] => pl
260 [lang] => pl
261 [id] => 657699
262 [lat] => 53.555
263 [lon] =>
264)

Event Timeline

I've been fixing some of these manually. I'm sure we had some other mechanism for finding and highlighting these but cannot find it.

I'm sure we had some other mechanism for finding and highlighting these but cannot find it.

Perhaps checkLat/checkLon in checkers ?

I'm sure we had some other mechanism for finding and highlighting these but cannot find it.

Perhaps checkLat/checkLon in checkers ?

They don't prevent e.g. a valid lat and a missing lon. I thought the fill_Table_monuments_all.py should ensure we don't add null island but also misses when only one is missing.

Neither of these creates a report which organisers could use to correct the lists/wikidata, they simply try to prevent crap from being entered into the database.

Neither of these creates a report which organisers could use to correct the lists/wikidata, they simply try to prevent crap from being entered into the database.

I'm just bad as remembering. checkLat/checkLon should report to the talk page of the list. Still all checkers are unaware of all other values so one missing + one present doesn't trigger it

I've updated the list of broken entries based on the latest logs

This open task is tagged with Wiki-Loves-Monuments 2018 which was two years ago. If this task was/is resolved, then please update the task status. If this task was not resolved but is still valid, then please update the project tags to include at least one active project tag, so this task could be found when looking at that other project. (Without reaction, this task might get declined at some point.) Thanks a lot!

Removing Wiki-Loves-Monuments 2018 tag as that was two years ago; adding general Wiki-Loves-Monuments tag.