[LandXML] LandXML-1.2 change request and ratification voting status
- From: "Nathan Crews" <nathan.crews@xxxxxxxxxxx>
- To: <landxml@xxxxxxxxxxxxx>
- Date: Tue, 29 Jul 2008 10:39:13 -0600
While there have been many “Yes” votes for the latest LandXML-1.2 schema
draft, there are a few additions that would round out the LandXML-1.2 data
model for official online cadastral survey submission. There is one instance
of changing an attribute to an element, but I believe the impact to be quite
limited - at least prior to the ratification and broad adoption of
LandXML-1.2. Please review the following proposal and let me know if there
are any issues as soon as possible.
Draft dated July 29, 2008 at
http://www.landxml.org/schema/LandXML-1.2/LandXML-1.2.xsd
Details in the http://www.landxml.org/schema/LandXML-1.2/Cumulative
<http://www.landxml.org/schema/LandXML-1.2/Cumulative%20LandXML-1.2%20Change
s.doc> LandXML-1.2 Changes.doc
Schema Diagram Documentation at
http://www.landxml.org/schema/LandXML-1.2/documentation/LandXML-1.2Doc.html
This will effectively reset the LandXML-1.2 ratification voting period until
August 15, 2008 and I will post the results on August 16, 2008.
If you have already voted and DO NOT wish to change your vote based on these
changes, then there is NO need to vote again.
The LandXML-1.2 SDK will be updated to match these changes if accepted.
Nathan Crews
www.landxml.org
The following proposal was made by the ePlan project in Australia:
ReducedObservation
The current ReducedObservation element contains the horizAngle element but
does not have the same metadata elements as does the distance and
measurement attributes.
A solution could be to use the metadata elements for azimuth in Reduced
Observation and the TargetPoint Element for the from station. This is not
optimal because the rest of the setup points refer to Instrument points (as
consistent with the rest of the model).
The possible optimum solution would be to change the schema to be consistent
for angles and include elements as shown. This would be more logical and
provide a more elegant solution.
CSD Element
LandXML1.1 (ReducedObservation)
Proposed Solution
Recordid
Name
Name
locangno
Locpntno
setupID
Setupid
Locfromlinno
TargetPoint (Element)
targetPointID
Loctolinno
targetSetupID
targetPoint2ID (New)
Angval
horizAngle
horizAngle
Angacc
azimuthAccuracy
angleAccutacy (New)
angderiv
azimuthType
angleType (New)
adoptedAzimuthSurvey
adoptedAngleSurvey (New)
azimuthAccClass
angleAccClass (New)
The proposed additions for the ReducedObservation Element would be :
<xs:element name="ReducedObservation">
<xs:annotation>
<xs:documentation>This has been modified to include
new fields such as accuracy, date, class and adoption. I've added in bearing
(azimuth is in terms of true north whereas bearing is the projection north)
</xs:documentation>
<xs:documentation> - maybe this doesn't matter, may
need to discuss</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element ref="TargetPoint"
minOccurs="0"/>
<xs:element ref="OffsetVals"
minOccurs="0"/>
<xs:choice minOccurs="0"
maxOccurs="unbounded">
<xs:element
ref="FieldNote" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="Feature"
minOccurs="0" maxOccurs="unbounded"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="purpose"
type="purposeType"/>
<xs:attribute name="setupID"
type="xs:IDREF"/>
<xs:attribute name="targetSetupID"
type="xs:IDREF"/>
<xs:attribute name="targetSetup2ID"
type="xs:IDREF"/>
<xs:attribute name="setID"/>
<xs:attribute name="targetHeight"
type="xs:double"/>
<xs:attribute name="azimuth"
type="direction" use="optional"/>
<xs:attribute name="horizDistance"
type="xs:double" use="optional"/>
<xs:attribute name="vertDistance"
type="xs:double" use="optional"/>
<xs:attribute name="horizAngle"
type="angle" use="optional"/>
<xs:attribute name="slopeDistance"
type="xs:double" use="optional"/>
<xs:attribute name="zenithAngle"
type="zenithAngle" use="optional"/>
<xs:attribute name="equipmentUsed"
type="equipmentType"/>
<xs:attribute name="azimuthAccuracy"
type="xs:double"/>
<xs:attribute name="distanceAccuracy"
type="xs:double"/>
<xs:attribute name="angleAccuracy"
type="xs:double"/>
<xs:attribute name="date"
type="xs:date"/>
<xs:attribute name="distanceType"
type="observationType"/>
<xs:attribute name="azimuthType"
type="observationType"/>
<xs:attribute name="angleType"
type="observationType"/>
<xs:attribute
name="adoptedAzimuthSurvey" type="xs:string"/>
<xs:attribute
name="adoptedDistanceSurvey" type="xs:string"/>
<xs:attribute name="adoptedAngleSurvey"
type="xs:string"/>
<xs:attribute name="distanceAccClass"
type="xs:string"/>
<xs:attribute name="azimuthAccClass"
type="xs:string"/>
<xs:attribute name="angleAccClass"
type="xs:string"/>
<xs:attribute
name="azimuthAdoptionFactor" type="xs:double"/>
<xs:attribute
name="distanceAdoptionFactor" type="xs:double"/>
<xs:attribute name="coordGeomRefs"
type="coordGeomNameRefs"/>
<xs:attribute name="name"
type="xs:string"/>
<xs:attribute name="desc"
type="xs:string"/>
<xs:attribute name="state"
type="stateType"/>
<xs:attribute name="oID"
type="xs:string"/>
<xs:attribute name="MSLDistance"
type="xs:string"/>
<xs:attribute name="spherDistance"
type="xs:string"/>
<!-- coordGeomRefs identifies one or
more 'name' values that link to specific <Line>, <Curve>, <Spiral> or
<IrregularLine> in a <CoordGeom> element. This allows linking an survey
observation to specific <Parcel>.<CoordGeom> based geometry. -->
</xs:complexType>
</xs:element>
The New elements are shown Highlighted.
Sample Record
A sample record for a measured angle could be
< ReducedObservation horizAngle="90.0000" purpose="normal"
setupID="IS-27-SP215054" equipmentUsed="Theodolite EDM" angleType="Measured"
targetSetupID="IS-26-SP215054" targetSetup2ID ="IS-28-SP215054"
coordGeomRefs="CG-22-SP215054" name="17" angleAccuracy=”0.0015”>
Or A sample record for a compiled angle could be
< ReducedObservation horizAngle="90.0000" purpose="normal"
setupID="IS-27-SP215054" equipmentUsed="Theodolite EDM" angleType="Adopted"
adoptedAngleSurvey="SP12345" targetSetupID="IS-26-SP215054" targetSetup2ID
="IS-28-SP215054" coordGeomRefs="CG-22-SP215054" name="17" angleAccuracy=”
0.0015”>
Head of Power
The Head of Power in the original ePlan UML model had a 0..∞ relationship
which would have dictated that it became an element rather that an
attribute. Also the head of Power is a jurisdictionally defined pick list
so will need to be implemented as a type.
The proposed schema shows
<!--SurveyHeader Element-->
<xs:element name="SurveyHeader">
<xs:annotation>
<xs:documentation>We seemed to have doubled up on
the survey purpose here, but the two are quite different - maybe need a
different name</xs:documentation>
</xs:annotation>
<xs:complexType mixed="true">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="Annotation"
minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="AdministrativeArea"
minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="AdministrativeDate"
minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="CoordinateSystem"
minOccurs="0"/>
<xs:element ref="Units" minOccurs="0"/>
<xs:element ref="MapPoint" minOccurs="0"
maxOccurs="unbounded"/>
<xs:element ref="Personnel"
minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="FieldNote"
minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="Feature" minOccurs="0"
maxOccurs="unbounded"/>
<xs:element ref="SurveyorCertificate"
minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="PurposeOfSurvey"
minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="HeadOfPower"
minOccurs="0" maxOccurs="unbounded"/>
</xs:choice>
<xs:attribute name="name"
type="xs:string" use="required"/>
<xs:attribute name="desc"
type="xs:string"/>
<xs:attribute name="purpose"
type="purposeType"/>
<xs:attribute name="startTime" type="xs:
dateTime"/>
<xs:attribute name="endTime"
type="xs:dateTime"/>
<xs:attribute name="surveyor"
type="xs:string"/>
<xs:attribute name="surveyorFirm"
type="xs:string"/>
<xs:attribute name="surveyorReference"
type="xs:string"/>
<xs:attribute
name="surveyorRegistration" type="xs:string"/>
<xs:attribute name="surveyPurpose"
type="xs:string"/>
<xs:attribute name="type"
type="surveyType"/>
<xs:attribute name="class"
type="xs:string"/>
<xs:attribute name="county"
type="xs:string"/>
<xs:attribute
name="applyAtmosphericCorrection" type="xs:boolean"/>
<xs:attribute name="pressure"
type="xs:double"/>
<xs:attribute name="temperature"
type="xs:double"/>
<xs:attribute
name="applySeaLevelCorrection" type="xs:boolean"/>
<xs:attribute name="scaleFactor"
type="xs:double"/>
<xs:attribute
name="seaLevelCorrectionFactor" type="xs:double"/>
<xs:attribute name="combinedFactor"
type="xs:double"/>
<xs:attribute name="jurisdiction"
type="jurisdictionType"/>
<xs:attribute name="submissionDate"
type="xs:date"/>
<xs:attribute name="documentStatus"
type="documentStatusType"/>
<xs:attribute name="surveyFormat"
type="surveyFormatType"/>
<xs:attribute name="surveyStatus"
type="surveyStatusType"/>
<xs:attribute
name="communityTitleSchemeNo" type="xs:int"/>
<xs:attribute
name="communityTitleSchemeName" type="xs:string"/>
<xs:attribute name="fieldNoteFlag"
type="xs:boolean"/>
<xs:attribute name="fieldNoteReference"
type="xs:string"/>
<xs:attribute name="fieldReport"
type="xs:string"/>
</xs:complexType>
</xs:element>
<!-Head Of Power Element-->
<xs:element name="HeadOfPower">
<xs:complexType>
<xs:attribute name="name"
type="headOfPowerType" use="required"/>
</xs:complexType>
</xs:element>
Sample
<SurveyHeader name="SP208311" surveyFormat="Standard"
surveyPurpose="Subdivision" desc="Plan of Lot 636 Cancelling Lot 636 on
SP158026 [and part of USL being Closed Road]" type="compiled"
surveyStatus="Survey Records Only" fieldNoteFlag="false"
submissionDate="2008-05-29" documentStatus="Captured">
<CoordinateSystem
horizontalDatum="Local" verticalDatum="Arbitrary"/>
<Personnel name="Twine Surveys Pty
Ltd(ACN 109 476 422)" role="Signatory" regType="Cadastral Surveyor"
regNumber="2281"/>
<Personnel name="Ivan Mervyn Luscombe"
role="Surveyed By" regType="Cadastral Surveyor" regNumber="697"/>
<SurveyorCertificate name="Form18V2"
certificateType="Form18V2" textCertificate="Twine Surveys Pty Ltd (ACN 109
476 422) hereby certify thatthe corporation, by Ivan Mervyn Luscombe,
cadastral surveyor, for whose work the corporation accepts responsibility,
has made this plan pursuant to the Survey and Mapping Infrastructure Act
2003 and Surveyors Act 2003 and associated Regulations and Standards and
that the plan is accurate, and compiled from
SP156026,CWL3425 in the
Department of Natural Resources and Mines."/>
<AdministrativeArea adminAreaType="Local
Government Area" adminAreaName="TABLELANDS REGIONAL" adminAreaCode="6810"/>
<AdministrativeArea
adminAreaType="Locality" adminAreaName="MILLSTREAM" adminAreaCode="1726"/>
<AdministrativeArea
adminAreaType="County" adminAreaName="CARDWELL" adminAreaCode="CWL"/>
<AdministrativeArea
adminAreaType="Parish" adminAreaName="WOODLEIGH" adminAreaCode="5139"/>
<HeadOfPower name="Surveying and Mapping
Infrastructure Act 2003"/>
<HeadOfPower name="Land Titre Act
1994"/>
</SurveyHeader>
Other related posts:
- » [LandXML] LandXML-1.2 change request and ratification voting status
