RFC: API Use Cases

[vforgione]

The other issues we have open are great for semantics (which undoubtedly important when considering designing a new API), but they leave little room for how the data consumed via the API can be used.

For this I would like to open the floor to people to discuss what their use cases for the data are, what sorts of delivery considerations should be made, etc. If you have a sensitive project and cannot discuss in the open, please email me (Vince) directly at vforgione@uchicago.edu. There we can talk confidentially, and if possible scrub identifiable information and post it back to this thread.

If you want to be specific about data sets, for example Array of Things, please make that obvious in your comments: e.g.

**Regarding AoT Data**: I am working on a project that consumes sensor net data and ...

[vforgione]

(Meeting notes from Robb Drinkwater and Douglas Pancoast)

Regarding Array of Things Data

• Lane of Things

  • working with particle.io boards (photons)
  • 4kb load max
    • simplicity is crucial
  • needs single endpoints for single nodes with possibility of getting single data points
  • e.g. get node #abc123 and only humidity
  • JSON is a good output format

• Working with Grasshopper and Rhino 3d Modeling

  • creating components that can access AoT data
  • components can filter / drill down result data sets
  • this doesn't need to be slim -- components can link in workflows

[untilArch]

On Rhino / GH interaction with AoT data: Would great to make a small suite of GH components for getting / filtering AoT data in the R/GH work space. I've started to model that out - component types and simple information architecture. Attached here: AoT_hopper_0.pdf

[vforgione]

This is awesome @untilArch. Hopefully this week I'll have a flow of AoT data into the dev site and we'll start working on publishing our API spec. I need to have the data in hand to be confident about how best to make it available to everyone else.

[vforgione]

Docs for the API are at https://github.com/UrbanCCD-UChicago/plenario2/wiki/API-Documentation .

[untilArch]

Awesome. Thanks.

DP

---

On Mon, Mar 26, 2018 at 11:25 AM, Vince Forgione notifications@github.com wrote:

Docs for the API are at https://github.com/UrbanCCD- UChicago/plenario2/wiki/API-Documentation .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/UrbanCCD-UChicago/plenario2/issues/148#issuecomment-376226436, or mute the thread https://github.com/notifications/unsubscribe-auth/AKXUEiVuesHzQyeKQ9GcaHbyRkAp9wNZks5tiRZ0gaJpZM4Rojma .

-- Douglas Pancoast, AIA dpanco@saic.edu ~ Architect Skeptic Associate Professor - Dept. of Architecture, Interior Architecture & Designed Objects School of the Art Institute of Chicago