Topic: Map Query for Estimating

[dfarris75]

I'm looking at using a Map query to get estimates for structures, pipe, ditch, etc. and have some questions.

• Is there a way to get the report to tally up the lengths of pipe, ditch, etc. or must the user do the tallying in Excel after creating the report?
• Is there a way to report the total number of blocks (block count for structures, etc.)?
• Can you perform a report query on multiple sets of data (based on layers, object type, etc.) all at once or do you need to create a query for each set of data (ie - one query for pipes, another for structures, another for ditch, etc.)?

[dfarris75]

Also, if I wanted to label pipes via the query what is the value to place in the rotation field so that it will rotate the labels appropriately w/the pipe? Something with rtos I think...?

And can you add any other text in this process? ie - If you query a pipe and have it label the line with the length can you add LF to the end of said label?

[George]

If you're using C3D pipes, you'll find that they cannot be queried using Map. The joys of interoperability. If you use QTO you can get the report generated within C3D, then customize the output in a style sheet or take it to Excel if you want to. QTO is a 2010 only feature, but we use it quite a bit now after setting up the Parts List and Point Codes to generate the big ticket quantity items for us.

[dfarris75]

I'm using plain AutoCAD objects in this case. I am learning of annotation templates. This cures one ailment (additional text in labels).

[dfarris75]

Also, if I wanted to label pipes via the query what is the value to place in the rotation field so that it will rotate the labels appropriately w/the pipe? Something with rtos I think...?

And can you add any other text in this process? ie - If you query a pipe and have it label the line with the length can you add LF to the end of said label?

I've worked out these issues. Now just the initial post need be addressed.

rotation value in the query is (rtos .angle)
additional text is added via annotation template (is there another way from within the query definition?)

[sinc]

I believe the initial post was addressed.  Civil 3D elements cannot be queried with Map Queries.  Instead, they introduced Quantity Takeoff in 2010.

[dfarris75]

I'm using plain AutoCAD objects in this case. I am learning of annotation templates. This cures one ailment (additional text in labels).

[dfarris75]

Hehem.

[mjfarrell]

yes, you will find that setting your style up so that when reduced to acad objects they have some value...

then construct a report query of a nature

location=ALL
and Property type=Layer_Name=Sewer Pipe Size

then execute that query as a report...

you will want to experiment with this a bit, and probably need or want several such saved queries to run against your stupefied data set.

[dfarris75]

That's pretty much what I've done. I am able to query a report of all objects paid for in LF and use a SUMIF formula in Excel to sum up the individual quantities. Soooo much faster than sitting there with a calculator. I will be working on a template to also calc the areas of new pavement, sod, etc.

So far I haven't found anywhere in the query to have it tally up the number of instances of a given block though. If it can't do that I'll have to either use attribute extraction OR just query in the blocks and select > select similar and move or copy to get how many are in there... Other ideas welcome.

[mjfarrell]

one might consider placing an attribute (1) or object data record on the blocks in question
this then can be queried as a unique value (1) and summed for block counts

[dfarris75]

Object data record?

[mjfarrell]

Map>>Database>>Object Data

think of them as invisible attributes one can attach to objects to make the GIS smarter...

[dfarris75]

Oh yeah. I think I did a tutorial on that.

[dfarris75]

2 more things:

• Is there an expression to query the length of a MULTILINE?

• Is there an expression to query the VISIBILITY STATE of a block?

[mjfarrell]

yes for vis state see attached for clue...

Location
Property
Data is the key


MLINE(s) no joy yet...as even a generic autocad LIST on them doesn't not reveal a true lenth value.

(what are you using them for any way?)

[dfarris75]

None yer bizniss nosey.

Thx.

[mjfarrell]

None yer bizniss nosey.

Thx.

then I can't help you do what ever it is any better.....but that would be your choice....
for all you know I have a different way to do that (different isn't always better, although it can be)
and it can be annoying when it is, and you weren't the one that thought of it.   

[dfarris75]

Hehe. I'm exploring. So far I am not getting that vis state deal to query... What I was looking for with that was to query a block in a drawing and then be able to add the visibility state into the report so if I have a single inlet block with many visibility states for the various types of inlets I could use the visibility state as report data.

[mjfarrell]

you might try a 1-2 combo punch....

query the blocks
run DATAEXTRACTION and report on the vis setting from there....

or not



more on that query later....

[mjfarrell]

And here is where I must enter what others will find offensive...

How long have Dynamic Blocks been in the application?

Why will MAP actually NOT report to VISIBILITY State information of the block; even thought there are four different areas of object properties that have to do with VISIBILITY states listed to chose from?

What should this be called?  A defect?  A Bug?  Or just more of autodesk NOT verifying that there is any sort of logical product interoperability?

Don't get mad at me, I'm just telling you that MAP will NOT report a Block's visibility state.
Get mad at autodesk.

[dfarris75]

So that will leave me with attaching data to the objects. I guess that is OK. Happy Turkey Slay Autodesk.

This data attachment is pretty nifty, however, I wish that the annotations would be dynamic as w/C3d objects/labels. I reckon I could create a toolbar to hasten the process of replacing outdated annotations.

What I'm doing is basically just exploring different ways to work with just AutoCAD and Map in opposition to Civil 3d. With data attachment and/or blocks w/attributes I should be able to work out some fairly fluid methods of calc-ing quantities for tables and costs estimates. Hopefully it will make things easier for my engineers since they simply cannot, or will not, grasp C3d. That is OK with me. My loyalties are with my employer, not Autodesk. If we won't use Civil 3d, then we need to get the most out of AutoCAD and Map. I must say, this would be even better if I knew programming ie - autolisp, diesel, etc.

[dfarris75]

Oh wait a second! I just discovered the refresh annotation command! Beautiful! At least that is somewhat dynamic, or at least semi-automated.

[mjfarrell]

yes, and the WIERD part is even though the block visibility parameter is available to be queried; MAP simply will NOT display the information.
WIERDER still, I thought I could out think them and perform and EXPORT to say a shape file; and wondrous miracle (NOT), lo one can NOT select the block visibility parameter to include in the export.  Because in the EXPORT operation the block visibility parameter is NOT even exposed as a selection item.

Now, some of you out there might be OK with this sort of performance from your autodesk products (subscription investment), whatever you want to call it.  I know where I fall on this issue.  Send your hatemail to autodesk, your vendor, send a Tweet out to all those TWITS out there, and let them know where you stand.  

a key item you will want to consider there Rusty, save your queries to an external library for ease of repeating same query against different data.

(removed refresh annotation comment)

[dfarris75]

10-4 Mike. Thanks ole buddy!