Skip to content

Conversation

@alexwlchan
Copy link
Contributor

Previously we were only filtering out null coordinates with accuracy=16, but actually they can occur at any accuracy level. We should ignore the accuracy for the purposes of detecting whether some coordinates are null.

h/t WMC user HenkvD for spotting this:
https://commons.wikimedia.org/wiki/User_talk:FlickypediaBackfillrBot#c-HenkvD-20240709145200-Alexwlchan-20240624084500

Previously we were only filtering out null coordinates with `accuracy=16`,
but actually they can occur at any accuracy level.  We should ignore the
accuracy for the purposes of detecting whether some coordinates are null.

h/t WMC user HenkvD for spotting this:
https://commons.wikimedia.org/wiki/User_talk:FlickypediaBackfillrBot#c-HenkvD-20240709145200-Alexwlchan-20240624084500
@alexwlchan alexwlchan merged commit b085505 into main Jul 10, 2024
@alexwlchan alexwlchan deleted the null-location-statement branch July 10, 2024 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants