Dimensional Measuring Interface
Standard
Standard Improvement Request
|
SIR No. 97-15 DMIS Release 3.0 SIR Type Other Severity Interpretation Request Status Resolved Date Submitted March 6 1997 Date Validated March 6 1997 Date In Process April 11 1997 Date Referred Date Vote Pending Date Closed August 20 1998 Action Clarifications Submitted By Dietmar May Object Workshops, Inc. PO Box 597 Wytheville VA 24382 USA Phone: (540)223-1145 Fax: (540)223-1241 dcmay@object-workshops.com |
Problem Topic
FEAT/PTDATA: Coor'd type for point output
Problem Description
What determines whether CART or POL coords are output for FEAT/PTDATA?
References
None
Related SIRs
None
Suggested Resolution
If the FEAT was defined in POL, then perhaps the point data should be in
POL. Otherwise, a statement modifier would be needed to indicate CART/POL
value.
Suggest that documentation be updated to indicate the circumstances under which FEAT/PTDATA is output in POL.
Support Documentation
None
Resolution
Warning!!
The following statement is only a resolution to a Standard Improvement Request (SIR) and is NOT part of the current DMIS standard, nor is it guaranteed to become part of the next revision of the DMIS standard even if voted and accepted by the DMIS National Standards Committee. This resolution is tentative because it may not be incorporated into the next version of the standard, it could be changed prior to the next release, or it could be changed as the result of the "public review and comment" period required for the next version of the standard. If you choose to use this tentative resolution, you do so at your own risk since at this time it is not part of the DMIS standard.
Added text to standard.
Insert into the standard, in section 3.2.6 before the last paragraph, the following paragraph:
The PTDATA values for a feature nominal are derived at the time of measurement. If a point was specified in POL within a PTMEAS, it will be output in POL during PTDATA, otherwise if in CART it will be output in CART.
Attachments
None
Notes
Added by Curtis Brown, cbrown@kcp.com on 7/7/1998
RESOLUTION INCOMPLETE: Per 4/97 a resolution was to add to the note on OUTPUT on page 337. This would be a new paragraph as follows:
When output of PTDATA is required, the coordinate system type for the individual points, CART or POL, will be determined by the PTMEAS correspoinding to the PTDATA point being output. If no specific PTMEAS statement can be associated with the PTDATA point, the coordinate system type will be the same as the defined feature nominal
HOWEVER, This still may not be good enough as FEAT/GSURF do not have an associated coordinate system type. This probably needs to be taken up at the next SIR subcommittee meeting. Also the subcommittee determined that a minor word, CART or POL could be added to OUTPUT to indicate the desired PTDATA format. An SIR for this enhancement may be entertained at the next meeting.
Added by Mike Holloway, hkm@ornl.gov on 7/30/1998
There are only three cases that I can think of where you cannot associate a PTDATA point to a PTMEAS point. The first is with scanning. Scanning of features other than GSURFs can revert to using the coordinate system of the feature. We could require that the first PTMEAS that defines the scan for a GSURF will define the coordinate system for PTDATA points for that feature.
The other two cases are where the MODE is AUTO or MAN. In the case of AUTO, I don't believe that you can define an automatic measurement sequence for a GSURF. I guess that for a GSURF measured in MAN mode, we could leave it up to the DME to decide, just that the output format listed must be used.
Another feature that we have not considered is FEAT/OBJECT. I believe that the rules for GSURF could be used for OBJECT also.
Added by Interpretation Sub-Committee, gph5@chrysler.com on 8/4/1998
Insert into the standard, in section 3.2.6 before the last paragraph, the following paragraph:
The PTDATA values for a feature nominal are derived at the time of measurement. If a point was specified in POL within a PTMEAS, it will be output in POL during PTDATA, otherwise if in CART it will be output in CART.