As a PI Web API user, I would like a simple method to perform bulk deletes of a particular attribute or PI tag. Currently, a bulk delete requires 2 calls. One to retrieve the event I wish to delete and another to delete it.11 votes
Web ID 2.0 should allow you to compute the WebID of a resource without needing to make a call to PI Web API. With that computed WebID, you can make the single call to PI Web API to delete the resource.
Does this solution meet your needs? Have I understood it correctly?
As an end-user, I want to be able to see to which PI Collective member I am connecting to. I also want to be able to toggle programmatically from one PI Collective member to the other so I can make sure the informaiton I am seeing is aligned and in synch accross all PI Collective members without going into thick PI clients or through log files.10 votes
This is a novel idea for monitoring PI Collective health, but there are no plans to add this ability to PI Web API. What advantages do you see in using PI Web API here?
When requesting time series data for multiple attributes using a streamset request and the PlotValues endpoint, it would be helpful if the response had the timestamps all lined up. This makes it easier to render the data, particularly if the data is being visualized in a stacked area series.0 votes
This is something we would like to do but the nature of PlotValues makes this difficult to do if not impossible. The PlotValues endpoint returns a time series with the most visually significant values for each pixel on a display. Even though the data values are actual recorded values, the values from different data streams have nothing to do with each other. The timestamps for different streams probably won’t line up.
- Don't see your idea?