|
|
|
|
|
by elfprince13
1220 days ago
|
|
We are doing inverse procedural modeling rather than photogrammetry, so there will be some idealization/iconification that takes place - but this also allows end-users to bring in their own material libraries in a pretty seamless way. |
|
Inverse procedural modeling discovers a procedural representation of an existing geometric model and the discovered procedural model then supports synthesizing new similar models.
Not sure what the "discovers" actually means, need to find a better reference ... This page [2] summarizes the method like this:
We propose an inverse modeling approach for stochastic trees that takes polygonal tree models as input and estimates the parameters of a procedural model so that it produces trees similar to the input.
So I guess that's roughly the same, then. I still don't quite understand it, if you have to manually model a building, and then get a procedural model's parameter out of that, you still had to model it (=do a lot of work)? Is the benefit that you then can store the parameters and use the model to regenerate the building, thus compressing the representation a bunch?
Cool project anyway, makes me long for NYC! :)
[1]: https://www.cs.purdue.edu/cgvlab/urban/urban-procedural-mode...
[2]: https://juliankratt.info/inverse_modeling.php