My way of thinking of this would be to do it with versioning. Ie for each city square you have a base mesh possibly as emdl to be referenced in. e.g. square_001_base
In your first project you will pull those in and place via reference so their edges are correct. Once you have that you can then create different versions of the base squares wether its by naming convention i.e. square_001_x, square_001_y or something like Git / mercurial Then in order to change which squares you pull into the project you can just edit the scntoc file for file bases versioning , or the files will be replaced by the correct ones if you use some form of source control. You could also possibly do it via Level of detail proxies (they will be about the same amount of detail but that’s not really an issue for this) I am sure there is also likely a scripting way to do this easily as well. Kind regards Angus From: Christian Gotzinger <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Tuesday 07 January 2014 at 12:56 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: OT: Organizing files that belong together Hi list, We have a digital city model that's divided up into several hundred squares. Our projects require us to make different versions of these squares for planning purposes. So for any given square, we may have 4 or 5 different versions. The more projects we do, the more complicated it gets for us to keep track of what belongs (and what fits) together. When we need to quickly prepare a file that contains "City model with Project X + Project Y", we have two main problems: a) For squares with multiple versions we need to figure out which of these versions are part of Project X and which are Project Y. b) We need to figure out how squares may be combined. Let's say that the square F003_C belongs to Project X, but square G003 is not part of Project X. We now can't be sure which version(s) of G003 properly match(es) F003_C at the seam. I'm unsure how common a problem this is and whether I explained it properly. Does anybody have any pointers as to what may be a good way to tackle this? Maybe some kind of specialized software? Thank you Christian <table width="100%" border="0" cellspacing="0" cellpadding="0" style="width:100%;"> <tr> <td align="left" style="text-align:justify;"><font face="arial,sans-serif" size="1" color="#999999"><span style="font-size:11px;">This communication is intended for the addressee only. It is confidential. If you have received this communication in error, please notify us immediately and destroy the original message. You may not copy or disseminate this communication without the permission of the University. Only authorised signatories are competent to enter into agreements on behalf of the University and recipients are thus advised that the content of this message may not be legally binding on the University and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of The University of the Witwatersrand, Johannesburg. All agreements between the University and outsiders are subject to South African Law unless the University agrees in writing to the contrary. </span></font></td> </tr> </table>
