-
Notifications
You must be signed in to change notification settings - Fork 1
Locations like recTBXuIjttVmmZ88
not exported to mapbox or API due to availability tags
#701
Comments
Found this while investigating #702. |
I now have 353 examples of IDs that were reported as missing in #702 and for which the mapbox export preview comes back as an empty JSON object. I'm going to tag them |
Pasted that into https://vial.calltheshots.us/api/updateLocationConcordances/debug |
Mapbox export code filters through this: Lines 347 to 361 in 3aca574
|
Yes, that's why: |
|
recTBXuIjttVmmZ88
recTBXuIjttVmmZ88
not exported to mapbox or API due to availability tags
This is another hold-over from the world before we were importing most of our data: when we just had CA data and it was all based on reports, not exposing locations that had closed to our website and API made perfect sense. But now that we've reduced our report volume AND we're relying more on scrapers, that decision should be reconsidered |
This work will happen in #704. |
https://vial.calltheshots.us/api/exportMapboxPreview?id=recTBXuIjttVmmZ88 returns this:
{ "geojson": [] }
It should return something that looks like https://vial.calltheshots.us/api/exportMapboxPreview?id=recfh4U54QFppdCRw
The
https://vial.calltheshots.us/location/recTBXuIjttVmmZ88
page returns a 500 - which is caused by it trying to fetch that mapbox representation and failing: https://sentry.io/organizations/vaccinateca/issues/2457478645/?environment=production&project=5649843&query=is%3AunresolvedHere it is in the database: https://vial.calltheshots.us/dashboard/?sql=select+id%2C+name%2C+full_address%2C+soft_deleted+from+location+where+public_id+%3D+%27recTBXuIjttVmmZ88%27%3Aco3pgz0qKdFPsd5YdtqRcT76JfHC2F5hKhLMZ9PiCb4 - it's not soft deleted.
And in our API search: https://vial.calltheshots.us/api/searchLocations?id=recTBXuIjttVmmZ88
The text was updated successfully, but these errors were encountered: