has a couple of entries with an address on "greenswamp" road. That needs to be "Green Swamp" in order to geocode correctly. The "fix" link goes to the admin page for the news item, where indeed you can change the location address to "Green Swamp"...but saving that doesn't cause the item to be re-geocoded, so it remains "unmapped" on the front end.
We could go to a page that WOULD cause the item to be re-geocoded if we linked to the geocode admin entry (that is, whatever is the right item under /admin/data_dashboard/geocode/. If, on that page, you fixed the address and saved it, the item is again geocoded and now the front end is able to map it (however this route does NOT update the new item's location name...)
(Now greenswamp can probably be "fixed" by a street misspelling...but in general we don't seem to have achieved a way where the fix link can be useful for actually fixing up bad addresses in data...)
I think we gave bad instructions when it came to creating the fix links on the data dashboard failure list. Eg:
http://columbusco-staging.openrural.org/data-dashboard/restaurants/failures/?page=4
has a couple of entries with an address on "greenswamp" road. That needs to be "Green Swamp" in order to geocode correctly. The "fix" link goes to the admin page for the news item, where indeed you can change the location address to "Green Swamp"...but saving that doesn't cause the item to be re-geocoded, so it remains "unmapped" on the front end.
We could go to a page that WOULD cause the item to be re-geocoded if we linked to the geocode admin entry (that is, whatever is the right item under /admin/data_dashboard/geocode/. If, on that page, you fixed the address and saved it, the item is again geocoded and now the front end is able to map it (however this route does NOT update the new item's location name...)
(Now greenswamp can probably be "fixed" by a street misspelling...but in general we don't seem to have achieved a way where the fix link can be useful for actually fixing up bad addresses in data...)