-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve language in spatial overlap validation messages #502
Comments
For this particular validation message, the workbench does some parsing & formatting to improve readability, so it will be important to make sure that still works well. There are workbench tests covering that formatting which will probably fail if the language is changed. So that will be a good reminder. |
I agree this is a tricky one. I wonder if something generic up front like Stacie has:
And then also dump some helpful debugging info for developer troubleshooting? If we wanted to be fancy it could even be a
|
Let's at least take action on this part of the suggestion:
|
improve validation message when bounding boxes don't intersect #502
@newtpatrol suggests the current language isn't well-understood by users and we could do better:
I agree the first half of this proposed language is clearer. But not all models require the "same projected coordinate system", so we may not want to go that far.
Often the problem is an incorrectly assigned coordinate system - meaning the user-defined CRS does not match the actual CRS of the coordinates. This is a notoriously tricky thing for GIS beginners and would be pretty challenging to instruct people how to fix this in a sentence or two.
The text was updated successfully, but these errors were encountered: