A new draft (April 19, 2005) of the LandXML-1.1 schema, change document and sample road data file have been posted. One of our astute participants in Japan pointed out that the design cross sections had no defined location. He was correct, the new <DesignCrossSectSurfs> element was moved up to <Alignment> to check a validation issue and forgot to move it back to it's proper parent element <CrossSect>. Design cross section locations are governed by the parent <CrossSect> station and now the schema reflects that. Here are the corrections: In each cross section <CrossSect> there are two collections of design cross sections, Left and Right of the center line or profile grade line. Road design cross section schema definition added to existing <Alignment>.<CrossSects>.<CrossSect> structure: <xs:element name="CrossSect"> <xs:complexType> <xs:choice> <xs:element ref="CrossSectSurf" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="DesignCrossSectSurfs" minOccurs="0" maxOccurs="2"/> <xs:element ref="Feature" minOccurs="0" maxOccurs="unbounded"/> </xs:choice> <xs:attribute name="sta" type="xs:double" use="required"/> <xs:attribute name="name" type="xs:string"/> <xs:attribute name="desc" type="xs:string"/> <xs:attribute name="angleSkew" type="angle"/> <xs:attribute name="areaCut" type="xs:double"/> <xs:attribute name="areaFill" type="xs:double"/> <xs:attribute name="centroidCut" type="xs:double"/> <xs:attribute name="centroidFill" type="xs:double"/> <xs:attribute name="sectType"/> <xs:attribute name="volumeCut" type="xs:double"/> <xs:attribute name="volumeFill" type="xs:double"/> </xs:complexType> </xs:element> Regards, Nathan Crews <http://www.landxml.org>