|
|
|
|
|
|
by xoa
1866 days ago
|
|
|
Advances in miniaturization and better economics for lidar definitely are making floor plan creation and 3D room scanning far more accessible. For work I've been experimenting over the last few months with "RoomScan LIDAR" and "magicplan", using both an iPhone 12 Pro's built-in lidar and the ability to link with a bluetooth laser distance/angle tool. While the market is definitely still in its infancy and a number of things remain frustrating (as does dealing with more complex room geometries), the potential is obviously there and they've already been useful tools. Being able to throw together decent floor layouts with fairly decent 3D point clouds for an entire building in a short period with just a few tools you have with you anyway can be fairly magical already. And there is a clear path for far more with another year or two of maturation. In some ways the biggest issue right now is lack of ability for other tools that could in principle make a lot of use of imported plans/point clouds to import them. Generating is getting better and better, but the pipeline after that is a weak point. And case in point, there's this very post. Why can't I just give it my PLY|OBJ|XYZ cloud, or at least USDZ|DAE model? Why is there a need to reinvent the wheel here? For 3D House Plan stuff to take off, there has to be amortization of the work of generating something in the first place. While it's more accessible than ever, there is still time/money cost to throw something together, and it's silly to need it done more than once (with necessary updates after major renovations, but those are unusual events). Of course for me this entire thing is an instant write-off as soon as I see any sort of cloud requirement. Optional maybe ok, another vertical silo/3rd party dependency? Hard no. And lack of leverage is an issue throughout for an effort like this, anything that doesn't work through existing Home Assistant or other ecosystems is also immediately on the back foot. |
|
|