I have been asked to edit a previous drawing. The drawing already has a local map installed. I have been asked to add a grid reference system to this map, so that when I create an Object Data table, there will be a column (where pipework passes through) with grid refs listed. Hopefully, I am explaining this ok? I am new to Object Data and the Map side of things in Autocad. Below, I have shown the sort of Grid system I have been asked to do.
Hi @Craig_Swan
I'm not doubting the capabilities of Arc Pro. I would caution you on identifying the grid 'cell' the pipe passes through. If the pipe only resides in one cell, great. Identify that cell and you're done.
However, if the pipe passes through two cells, then name both, not just ONE!! If the pipe passes through three cells, then name all three. If four cells, name all four.
FYI, your uploaded drawing also has long pipes broken up into multiple pieces. Why? I'd suggest you make as few pieces as possible. <<Connect multiple pieces when possible.>> Making more than one piece of pipe would require you manage info for each individual pipe piece. For example, a 250m pipe should list ALL cells it passes through. If that pipe was broken up into 8 different pieces, you'd have to list each grid cell for each INDIVIDUAL piece and that's not efficient. The way it's set up now, you have only ONE cell indicated in the SECTION column of your database, meaning a long length passing through multiple cells wouldn't be accurate because it appears to be located in just one cell.
As far as creating a database with columns and rows informing a reader the grid cell where it pipe passes through, I don't like it. I don't like it because it suggests a reader can confidently rely on Excel or Access document to determine pipe location. I would prefer the map remain a 'MAP' or a Graphical Tool which clearly shows the grid cell(s) and indicates WHERE it's located on the project site. I don't think a column with 'Section' provides much benefit. A well drawn map would be more valuable, more meaningful.
For example, you could create a centralized staging area where pipes can be dropped off by a supplier prior to installation. A centralized location can save both time and money due to efficiency in storage/retrieval while a column in a database may not. You can't store pipe where it interferes with another subcontractor's work. The column named Section ignores this. Creating an accurate, user friendly Grid can provide the right info. Creating a separate Access column that displays only one section may create confusion....and confusion may result in an increase of expen$e$. Your task requires not only Grid Info......it entails providing the RIGHT info too.
FWIW, your Access (or Excel) database can provide info if the Access author gave it meaningful info such are pipe material, thickness, diameter, supplier, and cost per meter. You can create a list of metal pipe vs. reinforced concrete pipe vs. corrugated pipe. You can further break it down by pipe diameter & wall thickness, vendor, and cost per pipe meter. You could generate an accurate raw material cost per linear meter and cost of installation.
Chicagolooper
Hi @Craig_Swan
Thanks for the upload. Your uploaded Nevis doc only explains HOW to create an Object Data (OD) Table. What's an OD Table? A finished table is merely document that contains a ROWS and COLUMNS. A table has individual CELLS and that makes it similar to a spreadsheet in appearance. A row represents a record, meaning each row record corresponds to an individual pipe. If you have many pieces of pipes then you have just as many records. A column represents an attribute (also called a field).
The instructions you've uploaded deal with HOW to create an OD Table. It doesn't provide Values for attributes. If meaningful data exists, then such data may or may not, provide Values for attributes such as, but not limited to, Pipe ID, Length, and Section.
The Forum knows HOW to create an Object Data Table. Trust me. We know.
What we don't know is how many individual pipes exist and how to identify each of those individual pieces. We also don't know (and neither do you) is HOW the original author made each ROW to correspond to each individual pipe piece. The process he used to LINK each pipe drawn with a record was likely an ID number. It would be beneficial to know, in great detail of course, the process he used, so we, the Forum, can duplicate his process. The actual, real-deal Microsoft Access database might (or might not) provide insight.
From what you've provided so far, I'd offer to say your linework and data would work better in SHAPEFILE format. Someone else, maybe the person who sent you the DWG, maybe not, converted from it's original shapefile format to plain vanilla AutoCAD entities using the MAPIMPORT command. If this is the case, then I'd go back to shapefile and forget about using vanilla linework with object data. Shapefile provides more versatility than plain vanilla Cad linework even if that linework has OD. And FYI, Map3D can create, read, understand, and work with shapefile.
Questions for the drawing's original author:
How does an Object Data Record relate to an individual pipe?
In other words, WHY does this data record correspond to this specific pipe in modelspace and NOT that one?!?!
Chicagolooper
