rlmead
commented
1 year ago Notes on cleanup, remaining problems, and future considerations here
Queries used to find bad data (probably not comprehensive):
select name, address from venues where state != 'Kentucky';
select id, name, g_map_link from venues where g_map_link not like 'https://goo%' and g_map_link not like 'https://www.google.com%' and g_map_link not like 'https://g.page%';
select name, address from venues where city is null;
select name, address from venues where state is null;
Remaining tasks related to this work as of 3/19/23:
mode:onlinetag (and change the wording in the submission interface to account for on-air events)After we have cleaned up and reworked venue location data, we can manually review location information in the database and/or at infinite.industries/admin-venue-edit. Based on what we know of the data, we might find problems like:
The following information is outdated but may still be helpful. There is also related information about bad Google Maps URLs in the archived issue #316.
You can find a list of venues that need corrected addresses in the
incomplete_addressessheet of this spreadsheet.The list in that spreadsheet corresponds to the output from this query as of 12/4/22:
The list returned here may not be comprehensive - could be worth doing some other data validation checks, too. We'll probably find more buggy data as we work through #318.