Project map

[Anonymous]

I am still working on my tpl file
and my view map organization is in progress
but once I've had it done
I don't see reason to use project map any more...

So, you guys with finished templates,
Do you use project map at all?

[Erika Epstein]

Very quick way to move around stories when the story when all other view settings remain the same.

[Anonymous]

Sometimes I use it to open a Section View to Check something, but do not want the Hassle of having the Layer Combinations changing back and forth.

[Anonymous]

About the only time I use the Project Map is to create New Independant Details

[Link]

In theory you wouldn't think so but in reality you do:

Moving quickly between viewpoints without any layer combos changing. Or scale.

Creating and opening new viewpoints, especially temporary ones like check sections.

Selecting viewpoints to trace reference (as they are much less intensive than views that recall their view settings and tend to bog AC down).

Going into the different 3D window types.

Opening viewpoints that may not even reside in the view map. For example, as BIM Manager I have schedules that I use for checking purposes, but I don't want to confuse my users by saving views of them.

I think you'll find yourself back in the Project Map quite a bit.

Cheers,
Link.

[Barry Kelly]

Remember that the Project Map allows you to access everything that has been created in you model - stories, sections, elevations, 3D views, schedules, etc.
And you can choose exactly how you want to see them - scale, layers, partial structure display, etc.

The View Map is only as usefull as the views you create.
If a view is missing or has the wrong settings then there is no point in having it there in the first place.
When set up correctly the View Map is fantastic as you can have as many or as few views as you need.
Organising it into a logical structure with the use of folders is essential as you can expand or hide these folders as necessary.
A good template is essential to already have the necessary views in place and automate the creation of new views with "Cloned" folders.

But no matter how good your View Map is you will still use the Project Map as others have said.

Barry.

[Anonymous]

Barry wrote:
If a view is missing or has the wrong settings then there is no point in having it there in the first place.

I have always agreed with this and that is why in the Past I had never had a template with Cloned folders.

Barry wrote:
A good template is essential to already have the necessary views in place and automate the creation of new views with "Cloned" folders.

I now am using many of the Cloned Folders in my View Map. I often Place a "N/A" before the view name on the views that are not used.

[Anonymous]

Tnx for all this useful info,
fast navigation through project is probably the best one...

[Stress Co_]

Barry wrote:
When set up correctly the View Map is fantastic as you can have as many or as few views as you need.
Organising it into a logical structure with the use of folders is essential as you can expand or hide these folders as necessary.

Barry:
Have you noticed any problems with Teamwork projects not "remembering" whether or not folders are expanded/hidden?

"Save" works for solo projects... but not Teamwork.

EDIT:
Ah, never mind, found it
HERE

[Barry Kelly]

Stress wrote:

Barry wrote:
When set up correctly the View Map is fantastic as you can have as many or as few views as you need.
Organising it into a logical structure with the use of folders is essential as you can expand or hide these folders as necessary.

Barry:
Have you noticed any problems with Teamwork projects not "remembering" whether or not folders are expanded/hidden?

"Save" works for solo projects... but not Teamwork.

EDIT:
Ah, never mind, found it
HERE

That's good because I don't use teamwork.
Barry.