Cannot support treatments that intersect multiple superbasins

[rhodges]

We cannot realistically support this. The big question is what do we do when someone draws or uploads a treatment that crosses this boundary?

• OPTION 1: Tell them 'NO.'
  • Not easy to detect, but this is the simplest solution if we can figure out a quicker detection
• OPTION 2: Clip their drawing to the 'best match' basin
  • This will take some extra logic to figure out which basin, but should be straight-forward to model
  • The hard part is explaining to the user what we did, especially if we want to show them before the run so they can verify
• OPTION 3: Run both
  • This is probably the hardest, but doesn't come with the tricky bit of verifying everything with the user:
    • HARD: separating the geometry and running two separate model runs
    • Vegetation results could be calculated the same (from the original veg unit footprint)
    • Identifying a lowest common ppt is impossible, but if that's done after splitting the job into 2 treatments that's easy.

[rhodges]

Decision: Tell them "NO." (At least for 5/5)

Use the ppt_id field to test:

• sort veg units by ppt_id
• get first 5 characters of first unit in sorted list
• test against first 5 characters of last unit in sorted list