This issue can be found on the publish interactive map, but here's a screenshot from the same data loaded into QGIS that makes the issue more apparent by displaying the primary and secondary roads as a label.
The location is just to the south east of Kirkwood and College Avenue. So, all the labels should read something like "COLLEGE AVE & KIRKWOOD", but instead they have a random assortment of streets around town and even I-69.
There are so many points and they can't all be easily displayed here, but in QGIS I counted them as 345.
I don't think they street names are really random, though. I believe they are all addresses that failed to geocode normally.
For example, I think "MCNUTT CIRCLE" may be the informal drive in front of the building, and I don't expect mile marker notations like "I-69 MM#109" to geocode well either. My guess is that failing a street-level accuracy, the geocoder was allowed to fallback to "city-level" accuracy, with courthouse being the symbolic point that represents the location of Bloomington, and this intersection being one of the closest to the courthouse.
Sometimes geocoders can be configured to fail if they can't return a precise location, which may have been appropriate here.
This issue was found in master.geojson. The dates for the crashes involves span the whole range from 2003-2022.
I reviewed the accuracy of the source data around College Ave & Kirkwood and it looks highly accurate. It appears that the issue was introduced during the re-geocode step here in an attempt to fill in missing coordinates and make others more accurate.
This issue can be found on the publish interactive map, but here's a screenshot from the same data loaded into QGIS that makes the issue more apparent by displaying the primary and secondary roads as a label.
The location is just to the south east of Kirkwood and College Avenue. So, all the labels should read something like "COLLEGE AVE & KIRKWOOD", but instead they have a random assortment of streets around town and even I-69.
There are so many points and they can't all be easily displayed here, but in QGIS I counted them as 345.
I don't think they street names are really random, though. I believe they are all addresses that failed to geocode normally.
For example, I think "MCNUTT CIRCLE" may be the informal drive in front of the building, and I don't expect mile marker notations like "I-69 MM#109" to geocode well either. My guess is that failing a street-level accuracy, the geocoder was allowed to fallback to "city-level" accuracy, with courthouse being the symbolic point that represents the location of Bloomington, and this intersection being one of the closest to the courthouse.
Sometimes geocoders can be configured to fail if they can't return a precise location, which may have been appropriate here.
This issue was found in master.geojson. The dates for the crashes involves span the whole range from 2003-2022.
I reviewed the accuracy of the source data around College Ave & Kirkwood and it looks highly accurate. It appears that the issue was introduced during the re-geocode step here in an attempt to fill in missing coordinates and make others more accurate.