-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathGeologicReservoirs.xsd
443 lines (443 loc) · 29.1 KB
/
GeologicReservoirs.xsd
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
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
<xs:schema xmlns:aasg="http://stategeothermaldata.org/uri-gin/aasg/xmlschema/GeologicReservoir/1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml" xmlns:gmlsf="http://www.opengis.net/gmlsf" targetNamespace="http://stategeothermaldata.org/uri-gin/aasg/xmlschema/GeologicReservoir/1.0" elementFormDefault="qualified" version="01.05">
<xs:import namespace="http://www.opengis.net/gml" schemaLocation="http://schemas.opengis.net/gml/3.1.1/base/gml.xsd"/>
<xs:import namespace="http://www.opengis.net/gmlsf" schemaLocation="http://schemas.opengis.net/gml/3.1.1/profiles/gmlsfProfile/1.0.0/gmlsfLevels.xsd"/>
<xs:annotation>
<!-- This XSD document, including XML schema, indicates the content useful to characterize a subsurface reservoir for geothermal potential. The content model was created to provide a template for reservoir data gathered by the Texas BEG to be hosted by the NGDS. Provide a format that is clear and comprehensive so that it may be understood by fellow researchers in future studies. Also provide a standardized data template to allow for easy updating by multiple stakeholders and participants.-->
<!--Updated to version 1.0 from input from Play Fairway Analysis projects. Version 0.2.2 changed 'date' data types to 'dateTime'. Annotated version 0.2.1. This XSD document was created on 2013-06-03 by Christy Caudill, AZGS. Field Description annotations standardized 2013-08-22 by Esty Pape, AZGS.-->
<xs:appinfo source="http://schemas.opengis.net/gml/3.1.1/profiles/gmlsfProfile/1.0.0/gmlsfLevels.xsd">
<gmlsf:ComplianceLevel>0</gmlsf:ComplianceLevel>
<gmlsf:GMLProfileSchema>
http://schemas.opengis.net/gml/3.1.1/profiles/gmlsfProfile/1.0.0/gmlsf.xsd </gmlsf:GMLProfileSchema>
</xs:appinfo>
</xs:annotation>
<xs:element name="GeologicReservoir" type="aasg:GeologicReservoirType" substitutionGroup="gml:_Feature"/>
<xs:complexType name="GeologicReservoirType">
<xs:complexContent>
<xs:extension base="gml:AbstractFeatureType">
<xs:sequence>
<xs:element name="OBJECTID" type="xs:int" minOccurs="0">
<xs:annotation>
<xs:documentation>Integer record count, added by ArcGIS servers during service deployment; not required but cannot be removed when deploying from ArcGIS feature class. Not user maintained, so this element appears in XML implementation but not in the WellHeaderTemplate.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ReservoirURI">
<xs:annotation>
<xs:documentation>Unique identifier that specifies the feature represented (geologic reservoir). Each geologic reservoir should have a unique identifier. Ideally, the identifier is an http URI that will dereference to a known, useful representation of the feature. This identifier will be used to cross reference the feature to other information related to this feature.</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="255"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="ReservoirName" type="xs:string">
<xs:annotation>
<xs:documentation>Common or human-readable name by which the feature (Reservoir) is known. Recommend using only web-safe characters (a-z A-Z 0-9 _-.) in the name. Be consistent in the naming convention used within any given dataset. In this context, "Reservoir" is understood to mean "a volume of rock from which heat can be extracted."</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Label" type="xs:string">
<xs:annotation>
<xs:documentation>Short text string for labeling the feature on maps. Can be the same as feature name. A label may be an OtherLocationName, OtherID or the Name or some combination.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="OtherID" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Alternative identifier(s) for site information. Indicate the authority from which the OtherID is derived with a short (lower case) prefix delimited by a colon ':' If identifiers from multiple different authorities are available, delimit these identifiers with the pipe '|' character. For example, if a well were known to the Arizona Geological Survey (AZGS) by the id number 1337, the identifier string would be azgs:1337. Any such prefixes used to scope identifiers should be explained in the dataset metadata.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="OtherName" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Other human-intelligible labels for feature such as secondary name or common name, other spellings. Indicate the authority from which the OtherName is derived with a short (lower case) prefix delimited by a colon ':' If identifiers from multiple different authorities are available, delimit these identifiers with the pipe character '|'. For example, if a well were known to the Arizona Geological Survey (AZGS) by the id number 1337, the identifier string would be azgs:1337. Any such prefixes used to scope identifiers should be explained in the dataset metadata.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Description" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Free text field for any additional observations or other information regarding the feature (size, weight, quality, lithology, locality, etc).</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="County" type="xs:string">
<xs:annotation>
<xs:documentation>Required. County name. If unknown or not applicable use 'missing'. If offshore, specify 'offshore' in this field.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="State" type="xs:string">
<xs:annotation>
<xs:documentation>Required. State name without abbreviations. If unknown or not applicable use 'missing'. For offshore locations, specify the governing or nearest state and list the county as 'offshore'.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="LocationName" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Names of geographic features associated with the site that will be useful as search criteria to locate the information for this site. If identifiers from multiple different authorities are available, delimit these identifiers with the pipe character '|'.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="LatDegree" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Latitude coordinate for the surface location of the feature; values should be provided with at least 4 significant digits for sufficient precision (7 decimal places is recommended by the USGS (OFR 02-463, p. 6). Use decimal degrees.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="LongDegree" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Longitude coordinate for the surface location of the feature; values should be provided with at least 4 significant digits for sufficient precision (7 decimal places is recommended by the USGS (OFR 02-463, p. 6). Use decimal degrees.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="SRS" type="xs:string">
<xs:annotation>
<xs:documentation>The spatial reference system. It is recommended that an EPSG code be used to identify the SRS used to specify the location. If an EPSG code is used, identify it as such with the prefix 'EPSG:' EPSG:4326 is the identifier for WGS84, and should be the text in this field. EPSG stands for European Petroleum Survey Group. EPSSG codes can be dereferenced by putting the code in this URL (replace 4326) http://spatialreference.org/ref/epsg/4326/.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="LocationUncertaintyStatement" type="xs:string">
<xs:annotation>
<xs:documentation>Information on how the original location was determined, e.g.: 1:250,000 map, gps unit, Google Earth, PLSS Conversion, Spatial Datum Conversion, e.g., NAD27 to WGS84.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TemperatureMax_C" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Upper boundary of measured temperature range in reservoir, in decimal format.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TemperatureMin_C" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Lower boundary of measured temperature range in reservoir, in decimal format.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="DepthToTop_m" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Depth to top of reservoir.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="DepthToBottom_m" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Depth to bottom of reservoir.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="AverageReservoirDepth_m" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>An average depth for the 'producing zone' of the reservoir. For hydrocarbon reservoirs, this might be computed as a mean average of all total vertical depths (TVD) within the reservoir.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="AverageReservoirDepthUncertainty" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>An expression of the confidence in the AverageReservoirDepth_m value. Best practice to include units and assumptions for calculating uncertainty within AverageReservoirDepthMethodology.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="AverageReservoirDepthMethodology" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>The method for calculating AverageReservoirDepth_m is stated here. Required if AverageReservoirDepth_m is provided.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="DominantFormationName" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Formation of primary interest within the reservoir/fairway boundaries identified.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="OtherFormationName" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Other named geologic units that are of interest to the study; separate names with pipe ('|') character.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TargetRockName" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Rock type of interest in reservoir.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="OtherLithologyName" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Other rock types that are constituents of the reservoir; separate names with pipe ('|') character.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="MajorFields" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Major Field names within the region of study or fairway.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Area_m2" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Area of reservoir extent. Description text for record should provide some indication of how this was estimated.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Width_m" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Maximum dimension of reservoir perpendicular to the length.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Length_m" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Maximum horizontal dimension of the reservoir.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TargetRockVolume_m3" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Volume of target rock (sand, shale, etc.) between specified isolines within data area.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="BlockVolume_m3" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Volume of sediment contained between specified isolines within data area.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="IsolineTypeAndUnits" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Describes the properties of the Isoline including units (e.g. Isotherm in degrees C, isopachs in meters, etc.). Required if TargetRockVolume_m3 and BlockVolume_m3 are provided.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="IsolineRangeMin" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Describes the minimum value of the range for the Isolines. For example, if IsolineType is "isotherm", provide the minimum temperature. Required if TargetRockVolume_m3 and BlockVolume_m3 are provided.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="IsolineRangeMax" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Describes the maximum value of the range for the Isolines. For example, if IsolineType is "isotherm", provide the maximum temperature. Required if TargetRockVolume_m3 and BlockVolume_m3 are provided.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="PercentTargetRock" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Target Rock (Sand, shale, etc.) volume divided by block volume. </xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="AverageNetTargetRockThickness_m" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Average net target rock thickness within the reservoir/fairway boundaries identified as calculated from well log interpretation.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="AverageNetTargetRockThicknessUncertainty" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>An expression of the confidence in the AverageNetTargetRockThickness value. Best practice to include units and assumptions for calculating uncertainty within AverageReservoirDepthMethodology.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="AverageNetTargetRockThicknessMethodology" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>The method for well log interpretation in calculating AverageNetTargetRockThickness_m is stated here. Required if AverageNetTargetRockThickness_m is provided.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="WellCount" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Number of wells contained by reservoir in question. Required if AverageWellDepth_m was provided. </xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="FaultCount" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Number of faults contained by field in question.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Faulted" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Indicate if the reservoir was bounded, or limited in size, by vertical faults. 'Yes' or 'No' may be appropriate indications.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="FaultType" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Indicate general type of fault: Growth, Normal, Thrust.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="FaultHydraulicCharacter" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Provide insight into whether there is fluid flow from greater depths along faults or if they are creating a trap/seal.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="FirstProductionDate" type="xs:dateTime" minOccurs="0">
<xs:annotation>
<xs:documentation>Date for the record (of first production). Day, month and year must be specified; Excel will display using ISO 8601 date and time (yyyy-mm-ddT:hh:mm) format. If only the year is known, enter month and day as 'Jan. 1', (or '1/1/', or '1-1-', or 'January 1,'). All dates will be converted to yyyy-mm-ddThh:mm.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="LastProductionDate" type="xs:dateTime" minOccurs="0">
<xs:annotation>
<xs:documentation>Date for the record (of last production). Day, month and year must be specified; Excel will display using ISO 8601 date and time (yyyy-mm-ddT:hh:mm) format. If only the year is known, enter month and day as 'Jan. 1', (or '1/1/', or '1-1-', or 'January 1,'). All dates will be converted to yyyy-mm-ddThh:mm.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="YearsInProduction" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Number of years of active production.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="MonthlyProduction_bbl" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Used to estimate current pressure and most recent production history across the field.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ProductionReportDate" type="xs:dateTime" minOccurs="0">
<xs:annotation>
<xs:documentation>Date for monthly production value. Day, month and year must be specified; Excel will display using ISO 8601 date and time (yyyy-mm-ddT:hh:mm) format. If only the year is known, enter month and day as 'Jan. 1', (or '1/1/', or '1-1-', or 'January 1,'). All dates will be converted to yyyy-mm-ddThh:mm.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="AverageMonthlyWaterProduction_bbl" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Average monthly water production for every well in the field.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="MinimumMonthlyWaterProduction_bbl" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Minimum monthly water production from a well in the field.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="MaximumMonthlyWaterProduction_bbl" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Maximum monthly water production from a well in the field.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="WaterInjection_bbl" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Amount of water injected into a formation for disposal purposes or enhanced recovery.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="WaterSaturation_pct" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Water Saturation(%).</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="WaterTDS_mgl" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Total Dissolved Solids. Milligrams per liter.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="AverageFieldWidePressure_MPa" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Corrected pressure, use standardized drawdown curve to approximate contemporary reservoir pressure values. In megapascals.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="AverageFieldWideGradient_degCm" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Using corrected BHTs from wells in within the field. Degrees Fahrenheit per meter.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="AverageSurfaceTemperature_degC" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>If gradient is provided, specify the average surface temperature.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="AverageSurfaceTemperatureSource" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Source of the average surface temperature.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="PorosityMax_pct" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Maximum porosity values obtained from public data sources.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="PorosityMin_pct" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Minimum porosity values obtained from public data sources.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="PorosityAverage_pct" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>The Average Porosity available from public data sources. The method for calculating an average should be stated in PorosityAverageMethod. Where only one porosity value is obtained from public data sources, the minimum, maximum, and average will be identical.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="PorosityAverageUncertainty" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>An expression of the confidence in the PorosityAverage_pct value. Best practice to include units and assumptions for calculating uncertainty within PorosityAverageMethod.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="PorosityAverageMethod" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>The method for calculating PorosityAverage_pct is stated here. Required if PorosityAverage_pct is provided.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="PermeabilityMax_m2" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Maximum permeability based on Literature values for the field or calculated permeability using production tests. Units square meters (m2).</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="PermeabilityMin_m2" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Minimum permeability based on Literature values for the field or calculated permeability using production tests. Units square meters (m2).</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="PermeabilityAverage_m2" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>The Average Permeability available from public data sources. The method for calculating an average should be stated in PermeabilityAverageMethod. Where only one permeability value is obtained from public data sources, the minimum, maximum, and average will be identical.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="PermeabilityAverageUncertainty" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>An expression of the confidence in the PermeabilityAverage_m2 value. Best practice to include units and assumptions for calculating uncertainty within PermeabilityAverageMethod.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="PermeabilityAverageMethod" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>The method for calculating PermeabilityAverage_m2 is stated here. Required if PermeabilityAverage_m2 is provided.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ReservoirFavorability" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Calculated expression of the reservoir's favorability for geothermal applications. Examples of suitable parameters include flow rate, productivity, etc. Chosen parameter description and units need to be provided in methodology field. Uncertainty and methodology are required if ReservoirFavorability is provided. </xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ReservoirFavorabilityUncertainty" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>An expression of the confidence in the ReservoirFavorability value. Best practice to include units and assumptions for calculating uncertainty within ReservoirFavorabilityMethodology. .</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ReservoirFavorabilityMethodology" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>The method for calculating ReservoirFavorability is stated here. Required if ReservoirFavorability is provided, to explain units and calculation of ReservoirFavorability. Also provide units and method for calculating ReservoirFavorabilityUncertainty. .</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="CementationMineralogy" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Calcite, Quartz, Iron Oxides, Clay Minerals, etc.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Trap" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Sealing formation or structural orientation to trap hydrocarbons.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Drive" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Geopressure, dissolved gas drive, thermal expansion, etc.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="WaterDensity_mgL" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Indicate the water (or brine, likely) TDS (total dissolved solids). Unit of measure is mg/L.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="CommodityOfInterest" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>The commodity of interest associated with the borehole.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Stimulation" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>A treatment performed to restore or enhance the productivity of a well.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="AveragePerforatedThickness_m" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>Average perforated thickness per well across field.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="RelatedResource" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>This may be one to many http links to resources (logs, pictures or other documents if available online. Should be an http:// address (URL)) related to the observation described in each record. Separate multiple values with the pipe character '|'.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Source" type="xs:string">
<xs:annotation>
<xs:documentation>Mandatory. Short text explanation of source of information defining this feature or record; may be author-date type citation, well log, report, data files etc., but should include some indication of how digital data originated. If unpublished data, provide researcher name, date and research institution for proper citation. Separate multiple citations with pipe '|' character.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="MetadataURI" minOccurs="0">
<xs:annotation>
<xs:documentation>URI identifying (and ideally dereferencing to get) a full formal metadata record for the observation report. A time series of observations may all reference the same metadata record that provides contact information and details on procedure, etc.</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="255"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Shape" type="gml:GeometryPropertyType">
<xs:annotation>
<xs:documentation>Added by GIS for WFS service; this element appears in the xml output, but is generated during service deployment from the latitude and longitude, therefore it doesn't appear in the template.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>