Feedback: Capacity units , add MW/km2

[peterdudfield]

Not sure the units of Capacity.

Note that in Noted that London looks like there isn’t much solar in the MW view because there are so many GSPs with 50 MW capacity

We could use MW/km^2 to give some idea of that. plot this to see what it looks like

[peterdudfield]

Also having a hover over the GSP, would perhaps show what units its in

[akshayw1]

Could you pls assign this to me?

[peterdudfield]

@braddf just so you are aware, @akshayw1 might try this

[akshayw1]

Can you breif more over the issue, so that it could be clear to me @peterdudfield

[akshayw1]

Is there a contributor's document available for setting up the project locally? @peterdudfield

Edit - Figured out thanks

[akshayw1]

I have a couple of doubts regarding the issue. The repository contains two apps, Nowcasting and Quartz. Could you clarify which app this issue is related to? Additionally, could you specify the exact route involved? This will help me address and resolve the issue more quickly.

[peterdudfield]

I have a couple of doubts regarding the issue. The repository contains two apps, Nowcasting and Quartz. Could you clarify which app this issue is related to? Additionally, could you specify the exact route involved? This will help me address and resolve the issue more quickly.

nowcasting

[akshayw1]

Is there a communication channel available for OFX support? I’ve successfully set up both projects locally, but I’m encountering an issue with unauthorized access. Any guidance or support would be greatly appreciated.

I have setup all from auth0 and added https://api.quartz.solar/ IN API's too, Still getting unauthorised

Here’s a screenshot of the error for reference:

[peterdudfield]

The best way is on github discussions. I think this might be an issue that @braddf is aware off.

[peterdudfield]

But for a quick comment, are you passing a bearer token to the API?

[akshayw1]

@peterdudfield ofc yes, I have pass the bearer token, in request headers @braddf Pls help

[peterdudfield]

Your are using api-dev, did the bearer token get generated for that environment? Actually how did you make the bearer token?

[akshayw1]

The bearer token was generated specifically for the api-dev environment using the client credentials provided for this setup. The process involved authenticating via the OAuth endpoint with the correct client ID and secret for api-dev.

If there’s a possibility the token is mismatched or not valid for this environment, could you confirm if additional steps or configurations are required for generating a valid bearer token for api-dev?

[peterdudfield]

The bearer token was generated specifically for the api-dev environment using the client credentials provided for this setup. The process involved authenticating via the OAuth endpoint with the correct client ID and secret for api-dev.

If there’s a possibility the token is mismatched or not valid for this environment, could you confirm if additional steps or configurations are required for generating a valid bearer token for api-dev?

No, that sounds about right. Do you get any more details in the error?

[akshayw1]

Can you confirm me API_URL that is used, shoudl I try for https://api.quartz.solar/

[peterdudfield]

https://api-dev.quartz.solar/swagger looks good, thats the development env. One way you could do it is, go on to app.quartz.solar, use the inspect feature to get your bearer token. And use the bearer token for api.quartz.solar. Just an idea, and I dont know how feasible it is

[akshayw1]

Pls let me know,If possible, could we connect over a Meet session or another platform to review the configuration together? I believe a quick discussion could help identify and resolve the issue efficiently.

Tried as you. said, taking bearer and trying from postman

[akshayw1]

Hi @braddf and @peterdudfield,

Could you help with resolving the setup issue? I can quickly solve a issue,as I have solved similar issue in the past, but I'm currently facing challenges specifically with the API, as mentioned above

Your assistance would be greatly appreciated!

[peterdudfield]

Sorry. I think we are both away until early January. I'm sure we can pick it up then

[akshayw1]

Sure @peterdudfield , Thanks I would try and wait til, about me
I'm Akshay Waghmare, an undergrad at IIIT Allahabad, and I'm excited about contributing to Open Climate Fix for GSoC 2025. I recently got my first PR merged into the PV Live consumer project and would love to contribute further. I have experience in JavaScript, Python, ML, and web technologies, and I'm eager to work on projects involving real-time data analysis and AI solutions for climate challenges. Any guidance on how I can actively contribute would be appreciated!

[peterdudfield]

Did you have any luck @akshayw1 ?

[akshayw1]

After exploring it briefly, I shifted my focus to other things since I didn’t hear back from you. I was eagerly looking forward to your response and am now ready to dive back in! @peterdudfield

[peterdudfield]

So where did you get too?
You said you managed to make a create a brearer token? Did this work for api.quartz.solar or api-dev.quartz.solar? And did you pass that bearer token through with the code in this repo

[akshayw1]

I believe all the necessary configurations were set up correctly, including the bearer token, OAuth authentication, and adding the domain. The issue likely stemmed from something else that needs to be identified and addressed.

[akshayw1]

@peterdudfield any update

[peterdudfield]

I think @braddf is working on something