8000 Incorrect Areas Units · Issue #564 · Riverscapes/QRiS · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Incorrect Areas Units #564

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.

Sign up for GitHub

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

Jump to bottom
Closed
philipbaileynar opened this issue Jan 22, 2025 · 3 comments · Fixed by #565
Closed

Incorrect Areas Units #564

philipbaileynar opened this issue Jan 22, 2025 · 3 comments · Fixed by #565
Assignees
@KellyMWhitehead
Labels
🐛 bug Something isn't working

Comments

@philipbaileynar
Copy link
Contributor

Steps to Repro

  1. Create new manual AOI
  2. Digitize polygon

Observed

The modal popup when finishing a polygon shows the area field with the units "m". Should be "m2" preferably superscripted... but regular "2" is fine in a pinch.

Image
@philipbaileynar philipbaileynar added the 🐛 bug Something isn't working label Jan 22, 2025
KellyMWhitehead added a commit that referenced this issue Jan 23, 2025
@KellyMWhitehead
Fix Virtual Area Fields and VB,AOI field fixes #564
898f900
@KellyMWhitehead
Copy link
Collaborator

There were a few things going on here:

  1. area was not calculating on projected data, so the value was some sort of units of square degrees. I have added a transform to EPSG:5070 (Conus Albers). We can change this if we want a different projection system.
  2. Field Type was INT, so very large areas were showing up as NULL. I have changed this to DOUBLE.
  3. Set the Apply on Update flag so this recalculates if the geometry is changed.
  4. Fixed the label
  5. Hide the flows_into and flow_path fields in the attribute table and attribute editor forms for both Valley Bottom and AOI (which do not use these). These started showing up since we moved these features to the Sample Frame Feature Class.

@philipbaileynar
Copy link
Contributor Author

Is this just on-the-fly changes, or is there any risk to legacy/existing projects?

@KellyMWhitehead
Copy link
Collaborator

Is this just on-the-fly changes, or is there any risk to legacy/existing projects?

On the fly field expression for a virtual field. No changes are made to the underlying data.

@KellyMWhitehead KellyMWhitehead mentioned this issue Jan 24, 2025
Merged
KellyMWhitehead added a commit that referenced this issue Jan 24, 2025
@KellyMWhitehead
Fix Virtual Area Fields and VB,AOI field fixes #564
83353a0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KellyMWhitehead KellyMWhitehead

Labels
🐛 bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Version 1.0.9 Riverscapes/QRiS
2 participants
@philipbaileynar @KellyMWhitehead
0