[PavanRaghavendraKulkarni]

Pull Request

Description

Adds support for reading tilt/orientation from Data Platform location metadata, falling back to the database when a location hasn't been backfilled with that metadata yet (or isn't found in DP at all). This is a prerequisite for eventually eliminating the database dependency entirely (see the follow-up PR, "Stripping out the datamodel") — DP has no native field for tilt/orientation, so they have to be read from each location's metadata Struct, written there by pv-site-api's create_location/update_location.

DbPvDataSource.get() now prefers DP-sourced tilt/orientation when present in a location's metadata, falling back to the site database's tilt/orientation columns otherwise — so behavior is unchanged for any site not yet backfilled in DP.

Fixes #

How Has This Been Tested?

• Added unit tests covering: DP metadata present (used), DP metadata absent (falls back to DB), site not found in DP at all (falls back to DB)

• Full existing test suite still passing

• This one tested against the dev platform

• Yes

Checklist:

• My code follows OCF's coding style guidelines
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• I have checked my code and corrected any misspellings

[peterdudfield]

• Update PR descirptions with how its tested
• Run locally, and plot forecast against current forecast (this cane ben viewed on site forecast page on the dashboard)

[PavanRaghavendraKulkarni]

Analysis Dashboard

Local forecast