Anuncios

The Autodesk Community Forums has a new look. Read more about what's changed on the Community Announcements board.

Anonymous
en respuesta a: john.vellek

Thanks John, I think we're going to go with something fairly simple at this point along the lines of what you suggest, albeit not a perfect solution!

 

We use these blocks on large masterplans, usually 1-500 houses but sometimes up to 1000 or 2000 houses, so using an individual XRef for roof plans is likely to be pretty cumbersome (not to mention complicated for some of our less skilled technicians to grasp!). There's also the added complication that the convention is to show a simplified roof plan on the overall layout, and to exclude any roof overhangs, so it's a diagrammatic roof plan rather than an accurate one.

 

The solution we're going to follow is to have a "data" block, which contains all the technical back end data, and that will be used for the database extract etc. We'll then have a secondary block for the "cosmetic" geometry, such as the roof plan, and that this will contain the majority of the information that plots. Users will then be able to monkey around with the appearance of the house block as much as they want, but will be able to leave the data block intact.

 

Having two blocks is not ideal, but we think that this is the least stressful in terms of workload of creating the block library and in terms of giving  users the flexibility to amend things as they need without breaking the database extraction.

 

Still happy to hear of any other suggestions!