Skip to content
This repository has been archived by the owner on Jun 1, 2022. It is now read-only.

Walgreens with 63 matched source locations looks like bad data #651

Open
simonw opened this issue Jun 9, 2021 · 0 comments
Open

Walgreens with 63 matched source locations looks like bad data #651

simonw opened this issue Jun 9, 2021 · 0 comments
Labels
bad-data Data that looks bad and needs investigating, or tasks to clean up bad data

Comments

@simonw
Copy link
Collaborator

simonw commented Jun 9, 2021

https://vial-staging.calltheshots.us/location/lpptz is the top one - that's Walgreens Co. #19134 in CT - because of the CT scrapers: https://vial.calltheshots.us/dashboard/?sql=select+source_uid%2C+source_name%2C+name+from+source_location+where+matched_location_id+%3D+35007%3AncVcHDs5Axbk6K_g7YTGp8BW-m7RT3HWkoABzBgzpgE

Actually that looks bad - I think a bunch of different CT Walgreens may have been incorrectly matched:

source_uid	source_name	name
ct_covidvaccinefinder_gov:605a3748494866ed91e08065	
ct_covidvaccinefinder_gov	Walgreens Pharmacy (Glastonbury)
ct_covidvaccinefinder_gov:605a374a494866ed91e0807c	
ct_covidvaccinefinder_gov	Walgreens Pharmacy (Hartford, Albany Ave)
ct_covidvaccinefinder_gov:605a374a494866ed91e0807f	ct_covidvaccinefinder_gov	Walgreens Pharmacy (Bristol, Main St)
...

Originally posted by @simonw in #650 (comment)

@simonw simonw added the bad-data Data that looks bad and needs investigating, or tasks to clean up bad data label Jun 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bad-data Data that looks bad and needs investigating, or tasks to clean up bad data
Projects
None yet
Development

No branches or pull requests

1 participant