Greenbyte Ideas
13 results found
-
Automatic updates of technicians GWO records
Create an API link between the personnel page and WINDA to automatically update technicians GWO records/qualifications using their WINDA ID.
12 votes -
description api key
It would be good to be able to add descriptions to API keys so you can document the purpose of the API key.
4 votes -
Lost production of statuses in the API should follow the selected period
For the Status endpoint, statuses overlapping over start date and/or end date should only take that part of the Lost production value that corresponds to the selected time interval.
Otherwise the Lost production does not match what you can see in the platform, e g in Data Studio, for the same time interval.
2 votes -
Ability to export only overdue site access via the API
We can export the site access via the API but it would be great if we could filter the overdue site access in the export.
4 votesThanks for your feedback, this is a great request. It's open for voting from other users.
-
Include other data signals with the Status API
When using export data, it is possible to get other datasignals during the time of a status, for example the exact windspeed, nacelle direction etc. at the moment of a status.
This is not yet possible with API using the Status endpoint. Could this be made possible?
5 votesThanks for your feedback, this is a great request. It's open for voting from other users.
-
Status changes trazability via API
when it comes to refreshing a status database via API, it is quite challenging to update manual changes in the status (i.e, category changes, group structure change, manually added stops that change the group structure,,,)
Would be great to have in the API some way to trace those changes. For example, "last modified" point in the API would already help. It would also be nice to know if the event was added manually, see image.
4 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Allow API permissions that limit the period of data that can be accessed
I would like to share data, but just for a set time period, for example from Jan-2020 to Dec-2020. As such I propose having a start-date, end-date and "all time" period option when creating (or editing) the API keys
3 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Export high resolution data at wind farm level
We would like to be able to export high resolution data at wind farm level instead of at wind turbine level.
6 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
API Endpoint - 'Try it out' gives 401
The Greenbyte Developer Portal shows the endpoints, with a TRY IT OUT button on the right hand side. Could you show some (fake) data there?
Whenever I click this button, I always get an empty body with 401 status.
1 vote -
Make all device power curves available from the API
Currently only the default power curves for each device are available via the API. It would be good to be able to extract all of the power curves assigned to a device
8 votesThanks for your feedback, this is a great request. It’s open for voting from other users.
-
Add turbine "title" in the data.json
In order to obtain "turbine title" in addition to "turbine Id" directly from same json please add the "turbine title" in the data.json.
For instance I am gathering data with data request and always need to make a second request to have the "turbine title" which is not present in data.json and more useful than turbine ID for final utilisation.5 votes -
Make all data readable through the API
I'd like to be able to access all data visible in GEC through the API.
For example the "potential power order" and "reference devices" from the Admin Turbine view, and data signal mappings from the Comms view.
14 votes -
API write endpoints for Metadata fields
We would like to be able to use the API for writing values to metadata fields.
21 votes
