data sharing without the vault

[trynders]

Me again,
If I am constructing everything in my working drawing, (alignments, surfaces, etc.) How can another user on my work network, view or reference my data. Is x-ref the way to go or is there another option?
Thanks

[Anonymous]

You are correct. Vault is a solution in search of a problem, and was not a
necessary addition, but a rather obvious marketing tactic. See my 9:17
post



wrote in message news:5257657@discussion.autodesk.com...
Yes. The only way to do projects is with vault.
You what though? The more I think about it, the more I don't understand why
vault is necessary. The only thing a drawing needs to get data is the pesky
little project.xml file. Is it REALLY being controlled by vault? Or is it
Civil 3D that reads/writes that file, and vault just "stores" it? Hmmmm...
I'm beginning to think conspiracy here.

[Anonymous]

I was just forwarded an FAQ on this very subject from Autodesk.

You can't share "projects" without vault like you could in 2006. They consider the software "fully functional" according to the FAQ despite yanking this functionality out unless you use the Vault software.

http://usa.autodesk.com/adsk/servlet/index?id=7340061&siteID=123112

[Anonymous]

"Landxml shuffle" are you referring to exporting and importing xml files back and forth? Basically creating several (base, design, layout, etc.) drawings with all design (previously projects subs in LDD) info in each? Matt's previous post stated it only worked for surfaces.

[Anonymous]

LandXML shuffle works only for surfaces.

I have been finding that a lot of the reason drawing were split up in the
past is because we had people slamming on changing labels.

I recommend in your pilot project try the absolute least number of drawings
humanly possible- and see how it goes. If it doesn't suit you, you need to
consider vault.

Though I don't know the size of your pilot, JF, I can speculate based on our
history that your project is a residential in the under 300 lot range
(maybe??) and I have personally done C3D production on a few in this scope
range with two "model" drawings using the shuffle as a data share.

We can post here or you can email me privately if you want. I am back from
NS.

--
Dana Breig Probert
http://civil3drocks.blogspot.com/
CADapult Ltd
Empowering Design With Innovative Solutions
www.cadapult.net
----------------------------------------------

[Anonymous]

Dana-
DingDingDing
It's a 67 lot KbK concept subdivision, so not only are we learning the software we aregoing against all recommendations and bringing an existing job forward.

[Anonymous]

it is ok to bring an existing job, just pretend it is new.

67 lots- and since i am lucky enough to know your jurisdiction and your
talent pool i would say you could break it down this way:


1) ebase houses points, surface (eg)
2) parcel base that houses just proposed parceling
3) pbase that houses surfaces, corridors, profiles, pipes, etc. shuffle
data share of (eg)
4) E+S "base"
5)SWM/TR-55 Pre --shuffle (eg)
6)SWM/TR-55 Post --shuffle (eg)
7) "sheet" drawings housing xref combos of above as appropriate

I'm stabbing quickly here, but if I make absolutely no sense let me know.

I think for 67 lots, despite all the sticky hands that want to stick
themselves in the pot, you should be able to tackle it without vault.



--
Dana Breig Probert
http://civil3drocks.blogspot.com/
CADapult Ltd
Empowering Design With Innovative Solutions
www.cadapult.net
----------------------------------------------