Good afternoon,
We're combining some separated office detail libraries. I poured through the various articles you all have made and determined 2 methods that could work.
Combine / Merge - This method is easy cause it's just a simple copy + paste. However the "rebuilding" function would take us quite some time as we have 100s of folders and subfolders.
Import / Export - This method is great because we have access to all of our various separate detail libraries. We could export the various ones and import into the chosen master, without needing to "rebuild" all of the folders.
My question it - is it not BMP to use the import / export process? Feels like this is a much better route but wanted to check to see if there's a reason it is not suggested in the merge / combine article.
Thanks,
Kevin
We're combining some separated office detail libraries. I poured through the various articles you all have made and determined 2 methods that could work.
Combine / Merge - This method is easy cause it's just a simple copy + paste. However the "rebuilding" function would take us quite some time as we have 100s of folders and subfolders.
Import / Export - This method is great because we have access to all of our various separate detail libraries. We could export the various ones and import into the chosen master, without needing to "rebuild" all of the folders.
My question it - is it not BMP to use the import / export process? Feels like this is a much better route but wanted to check to see if there's a reason it is not suggested in the merge / combine article.
Thanks,
Kevin
Steve,
I do cover a lot on office detail organization in this webinar: Intermediate Detail Tools
When using a single detail folder for multiple offices, where they each want to use different standards, there's of course a few ways to consider.
1. Set up standard detail folders up top for each office.
2. If saving into CSI, consider adding folders for local municipality standard details.
3. You could make consistent numbering in each folder for each office's details.
Then it's also useful to organize offices' project folders into office named folders too.
I hope that gives you some ideas.
-Amanda
I do cover a lot on office detail organization in this webinar: Intermediate Detail Tools
When using a single detail folder for multiple offices, where they each want to use different standards, there's of course a few ways to consider.
1. Set up standard detail folders up top for each office.
2. If saving into CSI, consider adding folders for local municipality standard details.
3. You could make consistent numbering in each folder for each office's details.
Then it's also useful to organize offices' project folders into office named folders too.
I hope that gives you some ideas.
-Amanda
Hi Jer,
We have been contemplating merging our four office installs to one. We're considering carious cloud install options now. The id3ea of merging the four office's details without breaking them (especially if they shade detail numbers but are completely different details) is scary. Would LandFX consider a detailed webinar going over the various options. The new could consider which options we could consider our BMP.
(BTW, The term BMP is used often for describing water quality and erosion control field practices).
We have been contemplating merging our four office installs to one. We're considering carious cloud install options now. The id3ea of merging the four office's details without breaking them (especially if they shade detail numbers but are completely different details) is scary. Would LandFX consider a detailed webinar going over the various options. The new could consider which options we could consider our BMP.
(BTW, The term BMP is used often for describing water quality and erosion control field practices).
Steven,
Well 3 hours is clearly far too long to have to wait. As for the error message, it is due to an errant XML file in the folder.
There technically is not a need to do the Export/Import process, and the details can manually be merged, certainly in less than 3 hours.
To manually merge detail libraries, you simply copy over various folders of details, and then you do need to manually recreate the folder structure. So it does take some time and effort, but at this point seems the better direction to go, rather than chasing issue after issue in try to merge such large detail libraries.
--J
Well 3 hours is clearly far too long to have to wait. As for the error message, it is due to an errant XML file in the folder.
There technically is not a need to do the Export/Import process, and the details can manually be merged, certainly in less than 3 hours.
To manually merge detail libraries, you simply copy over various folders of details, and then you do need to manually recreate the folder structure. So it does take some time and effort, but at this point seems the better direction to go, rather than chasing issue after issue in try to merge such large detail libraries.
--J
I work with Kevin and in the process of trying to export one of our project folders in the detail explorer, I received an error message. After waiting for it to export (approximately 3 hours) I received the pop up to save the folder location. I selected the location and clicked ok, then almost instantly, I got an error message and it failed to save the full detail export. Screen shot of the dialogue box attached. Is there a reason for receiving this error? I would like to try exporting again but it is a big time commitment not knowing if this will happen again.
Thanks
Thanks
Ah yes, correct, the export folder is not zipped.
As for BMP, I think the only BMP practice that applies here would be in ideally setting up detail folders so that a future integration like this goes without conflict. As in, accounting for one's current office within the detail hierarchy, so that other similar structured detail libraries could merge easily. But that would also mean having project numbers unique across offices, which would be challenging to foresee.
Overall, it will always be challenging to merge detail libraries, as there will inevitably be conflicts.
--J
As for BMP, I think the only BMP practice that applies here would be in ideally setting up detail folders so that a future integration like this goes without conflict. As in, accounting for one's current office within the detail hierarchy, so that other similar structured detail libraries could merge easily. But that would also mean having project numbers unique across offices, which would be challenging to foresee.
Overall, it will always be challenging to merge detail libraries, as there will inevitably be conflicts.
--J
Thanks for the feedback.
Sorry, too much alphabet soup in the industry! BMP = Best Management Practice.
To confirm - the export function does not export out ZIP files, but just regular folders.
Sorry, too much alphabet soup in the industry! BMP = Best Management Practice.
To confirm - the export function does not export out ZIP files, but just regular folders.
Kevin,
If you have Export zips of other detail libraries, and they do not run the risk of overwriting any existing details, then that is the best course of action. Otherwise, manually creating detail folders and copying over folders of details is the next best option. I am not familiar with the term BMP in this regard.
--J
If you have Export zips of other detail libraries, and they do not run the risk of overwriting any existing details, then that is the best course of action. Otherwise, manually creating detail folders and copying over folders of details is the next best option. I am not familiar with the term BMP in this regard.
--J
Kevin Pfeiffer
set the type of the post as
Issue — 2 months ago
- Page :
- 1
There are no replies made for this post yet.
Contact
- Land F/X
Our software tailors AutoCAD® to the needs of landscape architects, irrigation designers, and other professionals. We automate your most tedious tasks and ensure accuracy, giving you more time to design.