Ecoregions

[joewheaton]

We need *.lyr and Business Logic in RS_Context for ecoregions. We should expose as

• Ecoregions
  • Level I
  • Level II
  • Level III

We need to have Symbology for the Ecoregions. It should match what the colors the US EPA uses.

Level I

Level II

Level III

@Cashe93 and @wally-mac if you think someone else should do this, please reassign.

[tyler1218hatch]

Looks good, I'll probably start on this sometime this weekend.

[wally-mac]

@joewheaton what project should this worked be billed to? @Cashe93 is busy all week producing deliverables for Utah BLM. @tyler1218hatch has assigned this task.

[wally-mac]

@tyler1218hatch on this EPA website there are instructions to assigning symboloy to ecoregion data.

[wally-mac]

Okay, keep track of these hours separately until I know what index to use.

On Wed, Jul 29, 2020 at 7:19 PM Tyler Hatch notifications@github.com wrote:

Looks good, I'll probably start on this sometime this weekend.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Riverscapes/RaveAddIn/issues/79#issuecomment-666018852, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFHZAUR7OOGOQFMCMJVJKTTR6DDAPANCNFSM4PMIY3IA .

-- Wally Macfarlane 435.512.1839

[joewheaton]

@wally-mac and @tyler1218hatch, put this on Task 1... as part of Kern. When I know what you've got there, I'll decide whether we split it to a new task order.

[wally-mac]

Thanks @joewheaton, @tyler1218hatch please keep track of your hours under South Fork Kern.

[tyler1218hatch]

@philipbaileynar There appears to be an issue when the L3_key field is created. The field should essentially be a combination of the code and the name (This is true with L1_Key and L2_Key). Yet the L3_key field only has when number, when is should have 3 (formatted as #.#.#).

I could make the symbology work with the broken field, or I could make the symbology now with the assumption that the field names will be correct in the future. Ideas?

[philipbaileynar]

@tyler1218hatch the L3_Key field that I'm looking at has both the code and the name 25 High Plains. This is a concatenation of the US_L3CODE and US_L3NAME fields. I don't know if this helps or clears anything up? Do we need a quick chat?

[tyler1218hatch]

@philipbaileynar I believe it should concatenate the NA_L3CODE and NA_L3NAME codes instead. This would make the symbology and naming consistent with level 2 and level 1.

[joewheaton]

What's the status of this @wally-mac and @tyler1218hatch ? Eco regions still don't show up in RAVE (even thought they are in some projects now). Even if there is an issue with that L3-KEY, can we still make some progress to at least expose them and get a release of RAVE with some business logic for them if not some prelim symbology? Thanks!

[tyler1218hatch]

@joewheaton I've just created a pull request for @philipbaileynar to integrate.

[tyler1218hatch]

@philipbaileynar The pull request is all ready to go. The new national ecoregions dataset is here, and should replace what is currently on the national dataset in the warehouse.

[MattReimer]

@philipbaileynar the national project has been updated and the ZIP is rebuilding.