During my daily news readings (flipping through websites, blogs, news feeds, journal and newspaper apps, etc...) I stumbled upon a recent article by Rob Walker in then New York Times:
See the Article Here
This article touched upon the idea of using people in architecture renderings. Reading through the article I began to ponder... First, what a world it has become when a great blog like BLDGBLOG is featured in a New York Times article isn't a Blogspot.com address... cool. Geoff also adds a nice commentary about the subject:
See the Post Here
Anyways, read the article. The article makes you think quite a bit more about why, who, and what are these people doing in your rendering? Fellow students, professionals, and myself are all using some form of people texture in our renderings. Sometimes its a simple silhouette and other times it is a photorealistic representation.
Due to the fact that I tend to relate everything I do in my life to Revit, BIM, and Architecture I couldn't help but think about these people. Revit has a decent set up RPC (Rich Photorealistic Content) people. Autodesk so nicely names these people, but, leaves it at that. Given the concept of Information in BIM, should these people have more information? Should we provide some parameters about these people?
Hmm... Maybe Alex, with his briefcase, standing in front of the building is a salesman with three kids and a wife named Julia? Would there be any benefit from doing this? One could argue, as a designer, understanding and studying possible subjects that will occupy your building and then placing them in it could be a beneficial task.
Would Jerry's head clash with duct work when the MEP model is built?
Very important information could be drawn from these little RPC people that actually live inside your model.
Anyways... to get back to being a bit more serious... Read the article. It really makes you think about these semi-fictitious people...
The Revit Kid.com! by Jeffrey A. Pinheiro is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. Based on a work at The Revit Kid.com.