Adobe 12020596 User Guide - Page 59

Persistence of 3D Measurements and Markups

Page 59 highlights

Adobe Acrobat SDK Adobe® Supplement to the ISO 32000 Multimedia Features (Chapter 9 in PDF Reference) 9.5.6 Persistence of 3D Measurements and Markups 59 Add the next section after Section 9.5.5. 9.5.6 Persistence of 3D Measurements and Markups Beginning with extension level 3, users can add 3D measurement data to an instance of a 3D artwork. This measurement data is stored in a 3D measurement/markup dictionary. 3D measurements are associated with 3D views, and each 3D view can contain zero or more 3D measurement dictionaries. After a measurement is associated with view, it is visible only when that view is selected or active. As different views are displayed, the measurements associated with that view are made visible and previously displayed measurements become invisible. 3D measurements can either be simple 3D markups used to add information to the geometric data shown in a view, or have an associated comment, in which case they have all the associated functionality of a comment. A 3D measurement can be promoted or demoted to or from comment status. There are three key aspects to defining persistent 3D measurements: ● A mechanism to define the units associated with the geometric data being measured. A 3DU entry in TABLE 9.33 Additional entries specific to a 3D annotation, page 55, has as its value a 3D units dictionary, which stores the units data for this 3D annotation. [See "The 3D Units Dictionary" on page 59 for more information.] ● The association between 3D measurements and 3D view is realized through the MA entry in a 3D view dictionary ("TABLE 9.39 Entries in a 3D view dictionary" on page 57). The value of this entry is an array of 3D measurement/markup dictionaries, where each dictionary represents an instance of a 3D measurement to be displayed in the context of this view. For more information about 3D measurement dictionaries, see "3D Measurement/Markup Dictionary" on page 62. ● When a 3D measurement is promoted to a comment, a projection annotation ("Projection Annotations" on page 39) is created to manage the comment and its appearance in the comments list. An indirect reference to this projection annotation is placed in the 3D measurement dictionary. [See "3D Measurements and Projection Annotations" on page 75.] The 3D Units Dictionary The data associated with a 3D artwork annotation may be defined in an arbitrary 3D coordinate system. For viewing purposes, the application defines a camera to map these coordinates onto a view surface. (3D coordinate systems are discussed in Section 9.5.4 of the PDF Reference.) For measurement purposes, distances are computed in this arbitrary coordinate system and assigned physical meaning by entries in the 3D units dictionary. These sets of optional units should be defined: ● Creation time units: Units known at the time the 3D artwork annotation is created. ● User override units: Units defined by the user after the annotation was created ● Display units: Units that the user would like used when displaying distances for all newly created measurements. The first two definitions assign physical meaning to measured distances, and the third defines how the distances are presented. When a 3D annotation is created, the application may have information from external sources that allows it to determine the units of the data being imported. Later the user may want to either override that definition or control what units data is displayed in. In addition to defining the units, a scaling operation is defined that maps one set of units to another. For the creation time and user override units, the mapping states that "m model data units = n real units". For

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140

Adobe Acrobat SDK
Multimedia Features (Chapter 9 in PDF Reference)
Adobe® Supplement to the ISO 32000
9.5.6 Persistence of 3D Measurements and Markups
59
Add the next section after Section 9.5.5.
9.5.6 Persistence of 3D Measurements and Markups
Beginning with extension level 3, users can add 3D measurement data to an instance of a 3D artwork. This
measurement data is stored in a 3D measurement/markup dictionary. 3D measurements are associated
with 3D views, and each 3D view can contain zero or more 3D measurement dictionaries.
After a measurement is associated with view, it is visible only when that view is selected or active. As
different views are displayed, the measurements associated with that view are made visible and previously
displayed measurements become invisible.
3D measurements can either be simple 3D markups used to add information to the geometric data shown
in a view, or have an associated comment, in which case they have all the associated functionality of a
comment. A 3D measurement can be promoted or demoted to or from comment status.
There are three key aspects to defining persistent 3D measurements:
A mechanism to define the units associated with the geometric data being measured. A
3DU
entry in
TABLE
9.33
Additional entries specific to a 3D annotation
,
page 55
, has as its value a 3D units dictionary,
which stores the units data for this 3D annotation. [See
The 3D Units Dictionary
” on page 59
for more
information.]
The association between 3D measurements and 3D view is realized through the
MA
entry in a 3D view
dictionary (
TABLE
9.39
Entries in a 3D view dictionary
” on page 57
). The value of this entry is an array
of
3D measurement/markup dictionaries
, where each dictionary represents an instance of a 3D
measurement to be displayed in the context of this view. For more information about 3D measurement
dictionaries, see
3D Measurement/Markup Dictionary
” on page 62
.
When a 3D measurement is promoted to a comment, a
projection annotation
(
Projection Annotations
on page 39
) is created to manage the comment and its appearance in the comments list. An indirect
reference to this projection annotation is placed in the 3D measurement dictionary. [See
3D
Measurements and Projection Annotations
” on page 75
.]
The 3D Units Dictionary
The data associated with a 3D artwork annotation may be defined in an arbitrary 3D coordinate system.
For viewing purposes, the application defines a camera to map these coordinates onto a view surface. (3D
coordinate systems are discussed in Section 9.5.4 of the
PDF Reference
.) For measurement purposes,
distances are computed in this arbitrary coordinate system and assigned physical meaning by entries in
the
3D units dictionary
. These sets of optional units should be defined:
Creation time units:
Units known at the time the 3D artwork annotation is created.
User override units:
Units defined by the user after the annotation was created
Display units:
Units that the user would like used when displaying distances for all newly created
measurements.
The first two definitions assign physical meaning to measured distances, and the third defines how the
distances are presented. When a 3D annotation is created, the application may have information from
external sources that allows it to determine the units of the data being imported. Later the user may want
to either override that definition or control what units data is displayed in.
In addition to defining the units, a scaling operation is defined that maps one set of units to another. For
the creation time and user override units, the mapping states that “m model data units = n real units”. For