We crowd-source for data venues in NUS. As part of the input, there's a map on screen with the default venue being CLB:
This has resulted in many venues being incorrectly labelled as being at or near CLB.
Currently, the "Submit" button is only enabled after the user has moved the map, which prevents people from submitting CLB directly. However, there are still many submissions where the location is near CLB. The way we do quality control is super manual right now (i.e. maintainers eyeball if the location looks correct).
I don't know if there's an actual way to improve the quality control, but I'm opening this issue to document this known issue.
Edit: Maybe making emails mandatory would help?
Edit: NUS may have some building-related data (i.e. where the locations are). We could add some heuristics to guess which building a room should be in, and then check if the proposed location is within the general vicinity.
We crowd-source for data venues in NUS. As part of the input, there's a map on screen with the default venue being CLB:
This has resulted in many venues being incorrectly labelled as being at or near CLB.
Currently, the "Submit" button is only enabled after the user has moved the map, which prevents people from submitting CLB directly. However, there are still many submissions where the location is near CLB. The way we do quality control is super manual right now (i.e. maintainers eyeball if the location looks correct).
I don't know if there's an actual way to improve the quality control, but I'm opening this issue to document this known issue.
Edit: Maybe making emails mandatory would help?
Edit: NUS may have some building-related data (i.e. where the locations are). We could add some heuristics to guess which building a room should be in, and then check if the proposed location is within the general vicinity.