Update Solar Resource UI form location name parser to be more robust#929
Conversation
Also remove old Solar Resource Data page
… and other extensions
…when writing to CSV open in Excel.
|
@cpaulgilman I tried to test this by copying private.h from sam-private to the sam repository, but got the following error: I'm guessing I've missed a file - can you point me at the relevant instructions? |
|
@brtietz The email address comes from the registration code, rather than private.h so you would have to build SAM from sam-private to get the full functionality. I updated the SAM-private readme: https://github.com/NREL/SAM-private/blob/patch/README.md. It references the DocHub folder: https://github.com/NREL/SAM-documentation/tree/master/Releases%20and%20Updates/Build%20Instructions%20for%20NREL%20Releases%20and%20Updates. Perhaps an easier but hacky way to test is to temporarily copy the Solar Resource Data.ui file to SAM 2021.12.02. |
|
Some of the options in the test script produce the desired behavior. For example 34.818N,118.397W gives this: However, the issue that re-opened #710 (a period instead of a comma in a lat/lon pair) is interpreted as an address: Is that in or out of scope for this PR? I'd be happy to create a follow up issue and add more error-proofing logic later. |
|
My goal was to avoid the callback error described in #710 rather than try to interpret lat/lon separated by a period. A careful user would notice that the lat/lon in the returned weather file is different from the requested values, so I am not inclined to try to handle period-separated lat/lon values. |



Pull Request Template
Description
Improve parsing of location names typed on the Location and Resource page for NSRDB downloads and fix layout issues on Location and Resource page.
Testing requires either building sam-private or copying the Solar Resource Data.ui file to an official release version of SAM to access private API keys for geocoding and NSRDB downloads.
Fixes #710 and #874
While we're at it, fix some other minor UI issues: #848, #795, #617, #799.
Type of change
Please delete options that are not relevant.
Checklist:
If you have added a new compute module in a SSC pull request related to this one, be sure to check the Process Requirements.