You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>DiPlan-specific configuration parameters belong within the <code>mapConfiguration</code> object and are registered to the key <code>diplan</code>.</p>
31
+
<h3id="diplan" tabindex="-1">diplan</h3>
32
+
<table>
33
+
<thead>
34
+
<tr>
35
+
<th>fieldName</th>
36
+
<th>type</th>
37
+
<th>description</th>
38
+
</tr>
39
+
</thead>
40
+
<tbody>
41
+
<tr>
42
+
<td>mergeToMultiGeometries</td>
43
+
<td>boolean?</td>
44
+
<td>Defaults to <code>false</code>. If <code>true</code>, the exported FeatureCollection in getter <code>revisedDrawExport</code> will have merged geometries; that is, instead of Points, Lines, and Polygons, only MultiPoints, MultiLines, and MultiPolygons will be featured, created by merging the features of their respective geometry. All geometry types that are enabled in the <code>Draw</code> tool may occur. This step is executed before geometry validation and meta service usage.</td>
45
+
</tr>
46
+
<tr>
47
+
<td>metaServices</td>
48
+
<td>metaService[]?</td>
49
+
<td>Specification of a service that contains meta-information regarding geometries. Information from there will be added to features in getter <code>revisedDrawExport</code>.</td>
50
+
</tr>
51
+
<tr>
52
+
<td>validateGeoJson</td>
53
+
<td>boolean?</td>
54
+
<td>Defaults to <code>true</code>. If <code>true</code>, all geometries in getter <code>revisedDrawExport</code> will undergo a validity check before they are exported. To inspect the validity of the offered geometries, inspect the getter <code>simpleGeometryValidity</code> that indicates validity with a <code>boolean</code>.</td>
<td>Id of the vector layer to make use of in the meta service.</td>
72
+
</tr>
73
+
<tr>
74
+
<td>aggregationMode</td>
75
+
<td>enum['unequal', 'all']?</td>
76
+
<td>Defaults to <code>'unequal'</code>. In mode <code>'unequal'</code>, one of each property set is kept; duplicate property sets are dropped. In mode <code>'all'</code>, all property sets are kept without further filtering.</td>
77
+
</tr>
78
+
<tr>
79
+
<td>propertyNames</td>
80
+
<td>string[]?</td>
81
+
<td>Names of the properties to build aggregations from. If left undefined, all found properties will be used.</td>
82
+
</tr>
83
+
</tbody>
84
+
</table>
85
+
<p>From all geometries of the service intersecting our geometries, properties are aggregated.</p>
86
+
<p>Example: Our drawing feature touches these features in the layer with id <code>"metaSourceExampleId"</code>:</p>
<p>The feature will then have the following properties:</p>
109
+
<p>In mode <code>'unequal'</code>:</p>
110
+
<pre><codeclass="language-json">{
111
+
"type": "Feature",
112
+
"geometry": "...",
113
+
"properties": {
114
+
"metaProperties": {
115
+
"metaSourceExampleId": [
116
+
{ "a": 0, "b": 0 },
117
+
{ "a": 0, "b": 1 },
118
+
{ "a": 1, "b": 1 }
119
+
]
120
+
}
121
+
}
122
+
}
123
+
</code></pre>
124
+
<p>In mode <code>'all'</code>:</p>
125
+
<pre><codeclass="language-json">{
126
+
"type": "Feature",
127
+
"geometry": "...",
128
+
"properties": {
129
+
"metaProperties": {
130
+
"metaSourceExampleId": [
131
+
{ "a": 0, "b": 0 },
132
+
{ "a": 0, "b": 1 },
133
+
{ "a": 0, "b": 1 },
134
+
{ "a": 1, "b": 1 }
135
+
]
136
+
}
137
+
}
138
+
}
139
+
</code></pre>
140
+
<h2id="state" tabindex="-1">State</h2>
141
+
<h3id="getters" tabindex="-1">Getters</h3>
142
+
<table>
143
+
<thead>
144
+
<tr>
145
+
<th>fieldName</th>
146
+
<th>type</th>
147
+
<th>description</th>
148
+
</tr>
149
+
</thead>
150
+
<tbody>
151
+
<tr>
152
+
<td>revisedDrawExport</td>
153
+
<td>GeoJSON.FeatureCollection</td>
154
+
<td>The features produced with draw operations can be subscribed to via this getter. The "pure" variants can be fetched from the plugin <code>@polar/plugin-draw</code>, see its documentation. This "revised" variant includes all changes from the configuration of <code>mergeToMultiGeometries</code> and <code>metaServices</code>, i.e. the features may be merged and enriched with additional information for further processing.</td>
155
+
</tr>
156
+
<tr>
157
+
<td>revisionInProgress</td>
158
+
<td>boolean</td>
159
+
<td>Returns <code>true</code> if there are ongoing asynchronous operations. While true, the <code>revisedDrawExport</code> variable shall not be considered finished.</td>
160
+
</tr>
161
+
<tr>
162
+
<td>simpleGeometryValidity</td>
163
+
<td>boolean</td>
164
+
<td>Indicator of whether the OGC Simple Feature Specification (part of <ahref="https://www.ogc.org/de/publications/standard/sfa/">SFA</a>) rules are fulfilled.</td>
165
+
</tr>
166
+
</tbody>
167
+
</table>
168
+
<p>⚠️ Caveat: Please mind that there is currently no merge-logic for properties of features given via using the action <code>'plugin/draw/addFeatures'</code> of <code>@polar/plugin-draw</code>. If <code>mergeToMultiGeometries</code> is set true, an arbitrary set of properties will survive. If <code>metaServices</code> are set, <code>properties.metaProperties</code> will be overridden if they previously existed. It is assumed that incoming data shall only be recognized regarding its geometry and holds no properties.</p>
0 commit comments