Skip to content

g.region: Add more detail into LL error messages #1988

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

Merged
merged 1 commit into from
Nov 24, 2021

Conversation

wenzeslaus
Copy link
Member

When setting up region in LL, this adds the actual values to the error messages in case these are computed
in the g.region call or function call itself. The value may also provide more explanation to what was actually violated.

Similar to #1140 (e0ce155) but for the lat-lon extent cases.

When setting up region in LL, this adds the actual values to the error messages in case these are computed
in the g.region call or function call itself. The value may also provide more explanation to what was actually violated.

Similar to OSGeo#1140 (e0ce155) but for the lat-lon extent cases.
@wenzeslaus wenzeslaus added the enhancement New feature or request label Nov 24, 2021
@wenzeslaus wenzeslaus merged commit a1c9c22 into OSGeo:main Nov 24, 2021
@wenzeslaus wenzeslaus deleted the more-details-to-region-msg branch November 24, 2021 21:20
@neteler neteler added this to the 8.0.1 milestone Dec 9, 2021
ninsbl pushed a commit to ninsbl/grass that referenced this pull request Oct 26, 2022
When setting up region in LL, this adds the actual values to the error messages in case these are computed
in the g.region call or function call itself. The value may also provide more explanation to what was actually violated.

Similar to OSGeo#1140 (e0ce155) but for the lat-lon extent cases.
ninsbl pushed a commit to ninsbl/grass that referenced this pull request Feb 17, 2023
When setting up region in LL, this adds the actual values to the error messages in case these are computed
in the g.region call or function call itself. The value may also provide more explanation to what was actually violated.

Similar to OSGeo#1140 (e0ce155) but for the lat-lon extent cases.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants