Description Keys and Point data attributes

[dcolenutt]

I am looking for a way of efficiently bringing in point data created by our GPS units. Aside from the typical PNEZD fields, we have also added atttributes to the data (i.ie. PNEZD(Attribute 1)(Attribute 2)(Attribute 3)...(Attribute 5). Each of these attributes are further information on the point shot. As an example, if an IRON POST is shot, the next prompt(Attribute 1) is FOUND or PLACED, then GOOD, BENT,RESTORED, then Depth countersunk, and so forth.
A typical Iron Post shot would look like:

1, 50000.50, 1002.34, 1104.234, IRON_POST, FOUND, GOOD, 0.4
2, 51000.50, 1010.34, 1108.321, IRON_POST, PLACED, GOOD, 0.1

Now without using endless amount of point groups to show the correct point style and point label style (believe me, I've had up to 140 point groups, and plenty of headaches!), what is the best way of bringing this data in?
We have tried using Description Keys to some marginal success. The description key codes for the above 2 points look like:

IRON_POST_FOUND*
IRON_POST_PLACED*

AND within the point file(CSV), we've created a CONCATENATE macro that combines the Description with the Attributes:

1, 50000.50, 1002.34, 1104.234, IRON_POST_FOUND_GOOD_0.4,IRON_POST, FOUND, GOOD, 0.4
2, 51000.50, 1010.34, 1108.321, IRON_POST_PLACED_GOOD_0.1,IRON_POST, PLACED, GOOD, 0.1

This way the correct point style is used for both the FOUND Iron post and the PLACED Iron post.

What would be really great is if the Description Keys were able to look into these attributes(extra fields) and apply the point styles without having to Concatenate the data prior to importing the points.
Any suggestions?

Thanks a lot,

Dean Colenutt
Eclipse Geomatics & Engineering Ltd.

[Anonymous]

This is what I get from my TOPCON FC-100 with TopSurv software:

1,298122.072,1784104.092,140.280, MON: STATUS.LIST = FOUND STAMPED.TEXT =
"G-349" ,
2,298134.350,1785425.908,100.000, MON: STATUS.LIST = FOUND STAMPED.TEXT =
"G-350" ,
101,298094.082,1784120.304,140.368, IP: TYPE.LIST = IP SIZE.LIST = 1/2
TAGGED.TEXT = "-" ,
102,297778.594,1784123.158,139.681, IP: TYPE.LIST = IP SIZE.LIST = 1/2
TAGGED.TEXT = "LLS0000" ,
103,297883.300,1784114.691,137.162, IP: TYPE.LIST = IP-BENT SIZE.LIST = 1/2
TAGGED.TEXT = "-" ,
104,297883.300,1784114.690,137.160, EP: ,

I wrote a small VBA macro that takes this data and converts it to this:
1,298122.072,1784104.092,140.280, MON FOUND G-349
2,298134.350,1785425.908,100.000, MON FOUND G-350
101,298094.082,1784120.304,140.368, IP IP 1/2 -
102,297778.594,1784123.158,139.681, IP IP 1/2 LLS000
103,297883.300,1784114.691,137.162, IP IP-BENT 1/2 -
104,297883.300,1784114.690,137.160, EP

Which is a format the allows the Description Key params $0 $1 $2 etc. to be
used to complete the description as desired. For instance, my IP* Desc. Key
shows for the description:
$2" $1 $3
Which, when shown in the drawning, converts to this for Point 101:
1/2" IP LLS0000

I've been unable to get the output from the Topcon equipment to jive 100%
with the Autodesk software.


wrote in message news:5548900@discussion.autodesk.com...
I am looking for a way of efficiently bringing in point data created by our
GPS units. Aside from the typical PNEZD fields, we have also added
atttributes to the data (i.ie. PNEZD(Attribute 1)(Attribute 2)(Attribute
3)...(Attribute 5). Each of these attributes are further information on the
point shot. As an example, if an IRON POST is shot, the next
prompt(Attribute 1) is FOUND or PLACED, then GOOD, BENT,RESTORED, then Depth
countersunk, and so forth.
A typical Iron Post shot would look like:

1, 50000.50, 1002.34, 1104.234, IRON_POST, FOUND, GOOD, 0.4
2, 51000.50, 1010.34, 1108.321, IRON_POST, PLACED, GOOD, 0.1

Now without using endless amount of point groups to show the correct point
style and point label style (believe me, I've had up to 140 point groups,
and plenty of headaches!), what is the best way of bringing this data in?
We have tried using Description Keys to some marginal success. The
description key codes for the above 2 points look like:

IRON_POST_FOUND*
IRON_POST_PLACED*

AND within the point file(CSV), we've created a CONCATENATE macro that
combines the Description with the Attributes:

1, 50000.50, 1002.34, 1104.234, IRON_POST_FOUND_GOOD_0.4,IRON_POST, FOUND,
GOOD, 0.4
2, 51000.50, 1010.34, 1108.321, IRON_POST_PLACED_GOOD_0.1,IRON_POST, PLACED,
GOOD, 0.1

This way the correct point style is used for both the FOUND Iron post and
the PLACED Iron post.

What would be really great is if the Description Keys were able to look into
these attributes(extra fields) and apply the point styles without having to
Concatenate the data prior to importing the points.
Any suggestions?

Thanks a lot,

Dean Colenutt
Eclipse Geomatics & Engineering Ltd.

[Anonymous]

Hi Dean,

The best way of bringing the data in? There is only one way of importing
the data, but what happens with the data is what is concerning you.

Are you concerned with how the data displays, or with accessing aspects of
the data for other purposes?

Can you clarify what you want to happen to the data after you import it?

If you are concerned merely with the display arising from your data, it is
not clear to me how many levels of granularity and types of display you are
looking for.

How do you generate the file containing this data? Surely you don't key all
this into the data recorder for every shot.
Do you fully understand how Civil 3D uses "parameters" in point
descriptions?

--

Laurie Comerford
CADApps
www.cadapps.com.au
www.civil3Dtools.com

wrote in message news:5548900@discussion.autodesk.com...
I am looking for a way of efficiently bringing in point data created by our
GPS units. Aside from the typical PNEZD fields, we have also added
atttributes to the data (i.ie. PNEZD(Attribute 1)(Attribute 2)(Attribute
3)...(Attribute 5). Each of these attributes are further information on the
point shot. As an example, if an IRON POST is shot, the next
prompt(Attribute 1) is FOUND or PLACED, then GOOD, BENT,RESTORED, then Depth
countersunk, and so forth.
A typical Iron Post shot would look like:

1, 50000.50, 1002.34, 1104.234, IRON_POST, FOUND, GOOD, 0.4
2, 51000.50, 1010.34, 1108.321, IRON_POST, PLACED, GOOD, 0.1

Now without using endless amount of point groups to show the correct point
style and point label style (believe me, I've had up to 140 point groups,
and plenty of headaches!), what is the best way of bringing this data in?
We have tried using Description Keys to some marginal success. The
description key codes for the above 2 points look like:

IRON_POST_FOUND*
IRON_POST_PLACED*

AND within the point file(CSV), we've created a CONCATENATE macro that
combines the Description with the Attributes:

1, 50000.50, 1002.34, 1104.234, IRON_POST_FOUND_GOOD_0.4,IRON_POST, FOUND,
GOOD, 0.4
2, 51000.50, 1010.34, 1108.321, IRON_POST_PLACED_GOOD_0.1,IRON_POST, PLACED,
GOOD, 0.1

This way the correct point style is used for both the FOUND Iron post and
the PLACED Iron post.

What would be really great is if the Description Keys were able to look into
these attributes(extra fields) and apply the point styles without having to
Concatenate the data prior to importing the points.
Any suggestions?

Thanks a lot,

Dean Colenutt
Eclipse Geomatics & Engineering Ltd.