Pollination API Viewers R4.1

[theo-armour]

@ladybug-tools/spiders

Pollination API Viewers

R3

• Adds: Click any face to view its attributes

Demo: model pollination viewer

Source

Demo: model face-by-face viewer

Source

• Updated to newer aperture schema

[mostaphaRoudsari]

@theo-armour thanks for the update! We dropped the Pollination model in favor of face-by-face model. The final sample file has a new place. This will always follow the latest version of the schema: https://github.com/pollination/model-service/blob/master/app/models/samples/model.py

Now that we only have one schema we can concentrate on a single viewer. I will give you a more complex model in the coming weeks. A single room is not really fun! :)

Also when I clicked on the window it gave me an undefined output.

[theo-armour]

@mostaphaRoudsari

R3.1.0 model face-by-face viewer

• Opens local, modified copy of: https://github.com/pollination/model-service/blob/master/app/models/samples/model.py
• Translates JSON XYZ object to numeric array then to Three.jd Vector3 object
  • Work-around for { x: 0, y: 10, z: 100 } object
  • New extra step not required on previous models
• Displays the JSON attributes of apertures

[mostaphaRoudsari]

Beautiful! Thank you for the quick update! looks great.

How do you like the new schema? Does it closer to what you have been looking for? Any suggestions?

If I may suggest the next step it should probably be removing the aperture from the parent wall.

[theo-armour]

@mostaphaRoudsari

Adding the x,y and z to the vertices slows things down, because first they have to be taken out to create a numeric array prior to transforming coordinates into a Three.js vector3.

Having each face with all its attributes and vertices as a single collection is a good thing. Ditto having apertures as separate groups of vertices.

Saving as a .PY file, I hope is a temporary thing. .PY files are not one of the standard files type that browsers are permitted to open via a URL.

Naming things can get to be quite tricky. Is there a document that sets out the conventions you plan to use?

Other than that, looks fine. Do you ever plan to add construction information - for use with energy analysis? If so, how would that be added?

Apertures as holes in faces is a tricky thing. I have to remember how to conjugate my quaternions and so on. We will get there.

[mostaphaRoudsari]

@theo-armour,

Adding the x,y and z to the vertices slows things down, because first they have to be taken out to create a numeric array prior to transforming coordinates into a Three.js vector3.

I removed them originally but an array doesn't work well with our database structure as well as data validation. Unfortunately we have to keep them as x, y, z knowing it causes an overhead for visualization!

Having each face with all its attributes and vertices as a single collection is a good thing. Ditto having apertures as separate groups of vertices.

🎉

Saving as a .PY file, I hope is a temporary thing. .PY files are not one of the standard files type that browsers are permitted to open via a URL.

Yes. We can save them as JSON file if that makes it easier for you. At least for the model. cc: @AntoineDao

Naming things can get to be quite tricky. Is there a document that sets out the conventions you plan to use?

If you mean naming for models. We will only have one model type so it will be called model!

Other than that, looks fine. Do you ever plan to add construction information - for use with energy analysis? If so, how would that be added?

Yes. That will be added later and will be another property for each Pollination Face. Now we have rad_modifier and we will have energy_construction.

Apertures as holes in faces is a tricky thing. I have to remember how to conjugate my quaternions and so on. We will get there.

I hear you. You have done it once before. We will get there as you said.

[theo-armour]

@mostaphaRoudsari

R4.0.0

Demo: pollination model viewer

Source

• Opens files directly from Pollination GitHub page
• Adds wireframe display show/hide button
• Displays quad meshes with a single quad aperture with an opening for the aperture
• Displays apertures with the opacity indicated by rad_modifier.r_transmittance

Being a weekend and time for taking things easy, I cheated and reduced the spec to quads. ;- )

---

Yes. We can save them as JSON file if that makes it easier for you. At least for the model. cc: @AntoineDao

I figured out how to get and hack the .PY file. If you are trying to create a launguage independent industry standard then real JSON would be good.

If you mean naming for models. We will only have one model type so it will be called model!

I am wondering for definitions and uses of words in the file. For example what types and face types might be available.

[mostaphaRoudsari]

This looks great. The fact that the opacity is set based on transmittance values is so fancy.

I am wondering for definitions and uses of words in the file. For example what types and face types might be available.

Yes. The schema is documented here so you can see all the possible items for each JSON field.

https://pollination.cloud/api/#operation/create_model

[theo-armour]

@mostaphaRoudsari @chriswmackey @AntoineDao

pollination model viewer R4.1.0

Source

• F ~ Adds open files on local disk
• F ~ Processes triangles and quads