[LandXML] Re: LandXML attribute consistency
- From: nathan.crews@xxxxxxxxxxxx
- To: mostertag@xxxxxxxxxxx
- Date: Thu, 10 Oct 2002 03:34:13 -0700
To further extend the feature code data, the <Feature> element can be used.
For example,
<CgPoint name="11" state="existing" code="tree">315790.857525385
4839057.57432995 118.839
<Feature code="tree">
<Property label="Diameter" value="3 in"/>
<Property label="DripRadius" value="15 in"/>
<Property label="Height" value="37 feet"/>
<Property label="Species" value="Silver Maple"/>
</Feature>
</CgPoint>
Where the 'code' attribute is clearly associated with the addition metadata
contained in the <Feature code="tree"> element.
This approach does not preclude the use of additional <Feature code="xxx">
elements for the same CgPoint.
Nathan Crews
www.landxml.org
-----Original Message-----
From: Ostertag, Michael [mailto:mostertag@xxxxxxxxxxx]
Sent: Tuesday, October 08, 2002 2:55 PM
To: Nathan Crews
Subject: RE: [LandXML] LandXML attribute consistency
What about Feature Attributes...additional information pertaining to a
specific Feature Code. For instance a tree would have a Feature Code of
TREE and maybe Feature Attributes of SPECIES, HEIGHT, DIAMETER, etc.
Thanks,
Michael
-----Original Message-----
From: nathan.crews@xxxxxxxxxxxx [mailto:nathan.crews@xxxxxxxxxxxx]
Sent: Tuesday, October 08, 2002 12:02 PM
To: landxml@xxxxxxxxxxxxx
Subject: [LandXML] LandXML attribute consistency
There is a suggestion that we clarify the use of the common attributes name,
desc, and code. The issue comes from real-world data exchange customer
issues and I think there is a simple solution.
Here is a suggested and consistant use of the attributes in the data types
most common in LandXML data:
Cogo Points seems to be a simple item however there are at least 3 vendors
are placing feature coding in different attributes. We use Feature > Style,
LDD uses code and Moss uses desc. I suggest for discussion that beside the
actual geometry, we have a minimum of:
name - point name (we all seem to get this one.)
desc - a note on the point that adds information to the feature code
code - feature code. we use this to control displays and classify points
Alignments are an area where I have not had a lot of comments back from the
public but besides the required geometry I suggest the same information as
the cogo points.
name - alignment name
desc - a note on the point that adds information to the feature code
code - feature code. we use this to control displays and classify points
Parcels are the same as alignments to InRoads except they are closed.
name - parcel name
desc - a note on the point that adds information to the feature code
code - feature code. we use this to control displays and classify points
This really suggests that we use 'desc' for a simple note and use the 'code'
attribute to mean feature code, classification or category.
What do you think?
Nathan Crews
www.landmxl.org
Other related posts:
