-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdataset-template.xml
1212 lines (1211 loc) · 69.8 KB
/
dataset-template.xml
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
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?>
<!--*************************************************************************************************
*** Example ISO 19139 Geospatial Dataset Metadata based on the USGIN v1.1 Profile
*** by USGIN Standards and Protocols Drafting Team
*** U.S. Geoscience Information System (USGIN) - http://lab.usgin.org
*** Contributors: Wolfgang Grunberg, Stephen M Richard
*** 01/20/2010
***
*** DISCLAIMER: this is not an authoritative metadata example but an aide to get started.
*** Scope notes are mostly from NAP or ISO documentation; refer to
*** the USGIN profile document for more specific and reliable guidelines.
***
*** Validated against http://www.isotc211.org/2005/gmd (ISO 19115, CSW 2.0.2 AP ISO 1.0).
*** Follows the USGIN ISO 19139 Dataset Metadata Profile v1.1.
*** a derivative of the North American Profile (NAP)
***
*** NOTES:
*** - Codelists:
*** Most ISO metadata profiles and applications use ISO codelists or codelists that use ISO's codelist names. NAP does not use ISO codelist names. USGIN recommends using ISO over NAP codelists to ensure interoperability. Remember, the codeList attribute points to a Uniform Resource Identifier (URI) which defines an item's identity. It can be a URN or a URL.
*** - napm schema extension:
*** http://www.cits.rncan.gc.ca/html/brodeurj/.protege/.napMetadata/napMetadataWebsite/napMetadataTools/napXsd/napm is the namespace for NAP extensions in xmlns:napm. Its schema is located at http://www.cits.rncan.gc.ca/html/brodeurj/.protege/.napMetadata/tools/napXsd/napm/napm.xsd. However, that schema does not resolve properly because it also refernces a local copy of gmd. USGIN does not follow this NAP requirement because it constitutes a barier to interoperability.
*** - Language code:
*** NAP demands <ISO639-2/T three letter language code - lower case><;><blank space><ISO3166-1 three letter country code - upper case>. However, NAP's requirement is not interoperable and USGIN prefers ISO's <ISO639-2/T three letter language code - lower case> formatting.
***
*** KEY: (NAP-USGIN) - M/C/O/X (Mandatory, Conditional, Optional, Not Used)
***
**********************************************************************************************-->
<!-- USGIN ISO 19139 geospatial dataset metadata record -->
<gmd:MD_Metadata
xmlns:gmd="http://www.isotc211.org/2005/gmd"
xmlns:gco="http://www.isotc211.org/2005/gco"
xmlns:gml="http://www.opengis.net/gml"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.isotc211.org/2005/gmd http://schemas.opengis.net/csw/2.0.2/profiles/apiso/1.0.0/apiso.xsd">
<!-- (M-M) Metadata file identifier - A unique File Identifier (GUID) - USGIN recommends using a valid Universally Unique Identifier (UUID) -->
<gmd:fileIdentifier>
<gco:CharacterString>00C02E67-F1ED-473D-A240-068CCB041A73</gco:CharacterString>
</gmd:fileIdentifier>
<!-- (M-M) Metadata language - NAP demands <ISO639-2/T three letter language code - lower case><;><blank space><ISO3166-1 three letter country code - upper case>. However, NAP's requirement is not interoperable and USGIN prefers ISO's <ISO639-2/T three letter language code - lower case> formatting. -->
<!-- NAP Example -->
<!--
<gmd:language>
<gco:CharacterString>eng; USA</gco:CharacterString>
</gmd:language>
-->
<!-- ISO Example -->
<gmd:language>
<gco:CharacterString>eng</gco:CharacterString>
</gmd:language>
<!-- (M-M) Metadata character set - NAP specifies default is "utf8", codelist = napMD_CharacterSetCode. USGIN requires that a character set code is defined to facilitate CSW servers (deegree, GeoNetwork, etc.). -->
<gmd:characterSet>
<!-- MD_CharacterSetCode names: {ucs2, ucs4, utf7, utf8, utf16, 8859part1, 8859part2, 8859part3, 8859part4, 8859part5, 8859part6, 8859part7, 8859part8, 8859part9, 8859part10, 8859part11, 8859part13, 8859part14, 8859part15, 8859part16, jis, shiftJIS, eucJP, usAscii, ebcdic, eucKR, big5, GB2312}. -->
<!-- NAP example -->
<!--
<gmd:MD_CharacterSetCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_95"
codeListValue="RI_458">utf8</gmd:MD_CharacterSetCode>
-->
<!-- ISO example -->
<gmd:MD_CharacterSetCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_CharacterSetCode"
codeListValue="utf8">UTF-8</gmd:MD_CharacterSetCode>
</gmd:characterSet>
<!-- (M-M) Resource type - Define if this record is a: dataset (default), service, feature, software, etc. -->
<gmd:hierarchyLevel>
<!-- MD_ScopeCode code names: {attribute, attributeType, collectionHardware, collectionSession, dataset, series, nonGeographicDataset, dimensionGroup, feature, featureType, propertyType, fieldSession, software, service, model, tile}. -->
<!-- NAP example -->
<!--
<gmd:MD_ScopeCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_108"
codeListValue="RI_622">dataset</gmd:MD_ScopeCode>
-->
<!-- ISO example -->
<gmd:MD_ScopeCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_ScopeCode"
codeListValue="dataset">dataset</gmd:MD_ScopeCode>
</gmd:hierarchyLevel>
<!-- (O-M) Resource hierarchy level name - ISO 19115 assumes that the metadata hierarchy level name defaults to “dataset” if it is not documented. NAP does not use it, recognizing that it is redundant. USGIN makes this property mandatory to identify the USGIN resource type (see USGIN Profile, "Resources of Interest"). Default USGIN hierarchyLevelName.CharacterString is “Dataset.” Encode hierarchy by including hierarchyLevelName elements for all broader resource categories. E.g. default should also include a hierarchyLevelName=”Collection” element. For services USGIN hierarchyLevelName.CharacterString is “Service”. As use cases develop that provide rationale for definition of sub-categories of service, the resource category list will be expanded. -->
<gmd:hierarchyLevelName>
<gco:CharacterString>Dataset</gco:CharacterString>
</gmd:hierarchyLevelName>
<!-- (M-M) Metadata point of contact - Point of contact for the metadata record, e.g. for users to report errors, updates to metadata, etc. -->
<gmd:contact>
<gmd:CI_ResponsibleParty>
<!-- (M-M) (individualName + organisationName + positionName) > 0 -->
<gmd:individualName>
<gco:CharacterString>Stephen Richard</gco:CharacterString>
</gmd:individualName>
<gmd:organisationName>
<gco:CharacterString>Arizona Geological Survey</gco:CharacterString>
</gmd:organisationName>
<gmd:positionName>
<gco:CharacterString>Metadata Czar</gco:CharacterString>
</gmd:positionName>
<gmd:contactInfo>
<gmd:CI_Contact>
<!-- Phone -->
<gmd:phone>
<gmd:CI_Telephone>
<gmd:voice>
<gco:CharacterString>520.770.3500</gco:CharacterString>
</gmd:voice>
<gmd:facsimile>
<gco:CharacterString>520.770.3505</gco:CharacterString>
</gmd:facsimile>
</gmd:CI_Telephone>
</gmd:phone>
<!-- Address -->
<gmd:address>
<gmd:CI_Address>
<gmd:deliveryPoint>
<gco:CharacterString>416 W. Congress St., Suite 100</gco:CharacterString>
</gmd:deliveryPoint>
<gmd:city>
<gco:CharacterString>Tucson</gco:CharacterString>
</gmd:city>
<gmd:administrativeArea>
<gco:CharacterString>Arizona</gco:CharacterString>
</gmd:administrativeArea>
<gmd:postalCode>
<gco:CharacterString>85701-1381</gco:CharacterString>
</gmd:postalCode>
<gmd:country>
<gco:CharacterString>USA</gco:CharacterString>
</gmd:country>
<!-- (O-M) Metadata point of contact e-mail address - mandatory in USGIN -->
<gmd:electronicMailAddress>
<gco:CharacterString>[email protected]</gco:CharacterString>
</gmd:electronicMailAddress>
</gmd:CI_Address>
</gmd:address>
<!-- (O-O) online resources - this is the online resource to contact the metadata person-->
<gmd:onlineResource>
<gmd:CI_OnlineResource>
<gmd:linkage>
<gmd:URL>http://www.azgs.az.gov</gmd:URL>
</gmd:linkage>
<gmd:protocol>
<gco:CharacterString>http</gco:CharacterString>
</gmd:protocol>
<gmd:description>
<gco:CharacterString>Arizona Geological Survey Web Site</gco:CharacterString>
</gmd:description>
</gmd:CI_OnlineResource>
</gmd:onlineResource>
<!-- (O-O) hours of service -->
<gmd:hoursOfService>
<gco:CharacterString>8 AM to 5 PM Mountain Standard time (no daylight savings)</gco:CharacterString>
</gmd:hoursOfService>
<!-- (O-O) contact instructions -->
<gmd:contactInstructions>
<gco:CharacterString>Contact Steve Rauzi [[email protected]] or call Oil and Gas Commission Staff at Arizona Geological Survey, 520-770-3500.</gco:CharacterString>
</gmd:contactInstructions>
</gmd:CI_Contact>
</gmd:contactInfo>
<!-- (M-M) ISO 19139 Mandatory: contact role -->
<gmd:role>
<!-- CI_RoleCode names: {resourceProvider, custodian, owner, user, distributor, originator, pointOfContact, principalInvestigator, processor, publisher, author} - NAP expands with {collaborator, editor, mediator, rightsHolder}. -->
<!-- NAP example -->
<!--
<gmd:CI_RoleCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_90"
codeListValue="RI_414">pointOfContact</gmd:CI_RoleCode>
-->
<!-- ISO example -->
<gmd:CI_RoleCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#CI_RoleCode"
codeListValue="pointOfContact">point of contact</gmd:CI_RoleCode>
</gmd:role>
</gmd:CI_ResponsibleParty>
</gmd:contact>
<!-- (X-O) Metadata should include a URL that locates a thumbnail logo for organizations related to the metadata origination, the organization hosting the catalog that returned the metadata, the organization that originated the data, and the organization hosting online services that provide access to the data. -->
<gmd:contact>
<gmd:CI_ResponsibleParty>
<gmd:organisationName>
<gco:CharacterString>Arizona Geological Survey</gco:CharacterString>
</gmd:organisationName>
<gmd:contactInfo>
<gmd:CI_Contact>
<gmd:onlineResource>
<gmd:CI_OnlineResource>
<!-- Icon image file (e.g. tif, png, jpg, gif) for the metadata originator. This Icon will be displayed in search results to credit the metadata originator. -->
<gmd:linkage>
<gmd:URL>http://www.azgs.az.gov/logo/metadata/azgs.png</gmd:URL>
</gmd:linkage>
<!-- (X-C) For URL’s that indicate icon thumbnails, the CI_OnlineResource/name should be ‘icon’. -->
<gmd:name>
<gco:CharacterString>icon</gco:CharacterString>
</gmd:name>
</gmd:CI_OnlineResource>
</gmd:onlineResource>
</gmd:CI_Contact>
</gmd:contactInfo>
<gmd:role>
<!-- CI_RoleCode names: {resourceProvider, custodian, owner, user, distributor, originator, pointOfContact, principalInvestigator, processor, publisher, author} - NAP expands with {collaborator, editor, mediator, rightsHolder}. -->
<!-- NAP example -->
<!--
<gmd:CI_RoleCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_90"
codeListValue="RI_413">originator</gmd:CI_RoleCode>
-->
<!-- ISO example -->
<gmd:CI_RoleCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#CI_RoleCode"
codeListValue="originator">originator</gmd:CI_RoleCode>
</gmd:role>
</gmd:CI_ResponsibleParty>
</gmd:contact>
<!-- (M-M) Metadata date stamp - USGIN profile requires use of dateStamp/gco:DateTime (Note this contrasts with INSPIRE mandate to use dateStamp/gco:Date). This is the date and time when the metadata record was created or updated (following NAP). -->
<gmd:dateStamp>
<!-- Requires an extended ISO 8601 formatted combined UTC date and time string (2009-11-17T10:00:00) -->
<gco:DateTime>2009-11-17T10:00:00</gco:DateTime>
</gmd:dateStamp>
<!-- (M-M) metadata standard - NAP specifies "NAP - Metadata". USGIN profile conformant metadata is indicated by using “ISO-NAP-USGIN" -->
<gmd:metadataStandardName>
<gco:CharacterString>ISO-USGIN</gco:CharacterString>
</gmd:metadataStandardName>
<!-- (O-M) USGIN profile version -->
<gmd:metadataStandardVersion>
<gco:CharacterString>1.2</gco:CharacterString>
</gmd:metadataStandardVersion>
<!-- (O-C) Dataset Identifier - For USGIN, this is a string that uniquely identifies the described resource. If the resource has an identifier, it should be included here; if the resource will be referenced from other metadata, it must have an identifier here. If the dataset is coupled to a service, the value of the MD_Metadata/dataSetURI attribute is the unique resource identifier used by srv:coupledResource to link the service with the dataset. For the USGIN profile, the MD_Distribution/transferOptions/MD_DigitalTransferOptions/ online/CI_OnlineResource is used to specify URLs for access to the resource. -->
<gmd:dataSetURI>
<!-- Uniform Resource Identifier (URI) -->
<gco:CharacterString>http://azgs.az.gov/resource/00C02E67-F1ED-473D-A240-068CCB041A73</gco:CharacterString>
</gmd:dataSetURI>
<!-- (C-C) Other Languages - If description in more than one language is provided, this property should indicate what those languages are. The primary language used for metadata description is identified with MD_Metadata/language and characterSet and any additional languages are identified by MD_Metadata/locale/PT_locale elements, in which the language is provided according to ISO 639-2/T three-letter terminology codes in lowercase, and an optional country is provided according to ISO 3166-1 three-letter codes in uppercase, and mandatory characterEncoding. -->
<!-- This locale element example implies that all character string elements are available in English (from the MD_Metadata/language element), and in French. -->
<!--
<gmd:locale>
<gmd:PT_Locale id="FR">
<gmd:languageCode>
<gmd:LanguageCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#LanguageCode"
codeListValue="fra">Français</gmd:LanguageCode>
</gmd:languageCode>
<gmd:characterEncoding>
--><!-- ISO example --><!--
<gmd:MD_CharacterSetCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_CharacterSetCode"
codeListValue="utf8">UTF-8</gmd:MD_CharacterSetCode>
</gmd:characterEncoding>
</gmd:PT_Locale>
</gmd:locale>
-->
<!-- (O-O) Resource spatial representation - Spatial representation information for the dataset (resource). Best practice is to include metadata for spatial representation if the described resource is a georeferenced dataset. -->
<gmd:spatialRepresentationInfo>
<gmd:MD_VectorSpatialRepresentation>
<gmd:topologyLevel>
<!-- MD_TopologyLevelCode names: {geometryOnly, topology1D, planarGraph, fullPlanarGraph, surfaceGraph, fullSurfaceGraph, topology3D, fullTopology3D, abstract} -->
<!-- NAP Example -->
<!--
<gmd:MD_TopologyLevelCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_111"
codeListValue="RI_510">geometryOnly</gmd:MD_TopologyLevelCode>
-->
<!-- ISO Example -->
<gmd:MD_TopologyLevelCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_TopologyLevelCode"
codeListValue="geometryOnly">geometry only</gmd:MD_TopologyLevelCode>
</gmd:topologyLevel>
<!-- (C-C) Identification of the objects used to represent features in the dataset - -->
<gmd:geometricObjects>
<gmd:MD_GeometricObjects>
<gmd:geometricObjectType>
<!-- MD_GeometricObjectTypeCode names: {complex, composite, curve, point, solid, surface} -->
<!-- NAP Example -->
<!--
<gmd:MD_GeometricObjectTypeCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_99"
codeListValue="RI_510">surface</gmd:MD_GeometricObjectTypeCode>
-->
<!-- ISO Example -->
<gmd:MD_GeometricObjectTypeCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_GeometricObjectTypeCode"
codeListValue="surface">surface</gmd:MD_GeometricObjectTypeCode>
</gmd:geometricObjectType>
</gmd:MD_GeometricObjects>
</gmd:geometricObjects>
</gmd:MD_VectorSpatialRepresentation>
</gmd:spatialRepresentationInfo>
<!-- (O-O) Resource’s spatial reference system - Description of the spatial and/or temporal reference systems used in the dataset. NAP specifies
{identificationInfo/spatialRepresentationType/MD_SpatialRepresentationTypeCode = "vector") or (../MD_SpatialRepresentationTypeCode = ""grid"") or (../MD_SpatialRepresentationTypeCode = ""tin"") implies count referenceSystemInfo >= 1) } -->
<gmd:referenceSystemInfo>
<gmd:MD_ReferenceSystem>
<!-- ISO 19115:2003 Corrigendum 1:2006 removes CRS and projection parameter information, and uses ISO 19111 instead -->
<gmd:referenceSystemIdentifier>
<gmd:RS_Identifier>
<!-- (C-C) Reference System identifier code - For USGIN the code should be a value from the EPSG Geodetic Parameter Dataset register (http://www.epsg-registry.org/) in the form "EPSG:nnnn" where nnnn is the EPSG code number for the CRS. -->
<gmd:code>
<gco:CharacterString>EPSG:5701</gco:CharacterString>
</gmd:code>
<gmd:codeSpace>
<gco:CharacterString>urn:ogc:def:crs</gco:CharacterString>
</gmd:codeSpace>
</gmd:RS_Identifier>
</gmd:referenceSystemIdentifier>
</gmd:MD_ReferenceSystem>
</gmd:referenceSystemInfo>
<!-- (X-X) Metadata extension information - not used in USGIN -->
<!--
<gmd:metadataExtensionInfo/>
-->
<!-- **************** -->
<!-- (M-M) Resource identification information - At least one of MD_DataIdentification (dataset, dataset series) or SV_ServiceIdentification (service) is required. -->
<gmd:identificationInfo>
<!-- Resource Dataset or Dataset Series Identification -->
<gmd:MD_DataIdentification>
<gmd:citation>
<!-- (M-M) Resource citation - For USGIN purposes, this should be viewed as information to identify the intellectual origin of the content in the described resource, along the lines of a citation in a scientific journal. Required content for a CI_Citation element are title, date, and responsibleParty -->
<gmd:CI_Citation>
<!-- (M-M) Resource title - USGIN recommends using titles that inform the human reader about the dataset’s content as well as its context. -->
<gmd:title>
<gco:CharacterString>Scanned Borehole Compensated Sonic Log for 0391, Kerr-McGee08 Navajo</gco:CharacterString>
</gmd:title>
<!-- (O-O) Alternate title -->
<!--
<gmd:alternateTitle>
<gco:CharacterString>some alternate title</gco:CharacterString>
</gmd:alternateTitle>
-->
<!-- (M-M) Resource reference date - Best practice is to include at least the date of publication or creation of the resource. The date of the resource reported in the citation corresponds to the resource’s last update version according to its update frequency. CI_Date content includes a date and dateType. Date for USGIN profile uses xs:date data type, defined thus “date uses the date/timeSevenPropertyModel, with hour, minute, and second required to be absent. timezoneOffset• remains optional” (http://www.w3.org/TR/xmlschema11-2). -->
<gmd:date>
<gmd:CI_Date>
<gmd:date>
<!-- Requires an extended ISO 8601 formatted combined UTC date and time string (2001-12-17T09:30:47) -->
<gco:DateTime>2001-12-17T09:30:47</gco:DateTime>
</gmd:date>
<gmd:dateType>
<!-- CI_DateTypeCode names: {creation, publication, revision} _ NAP expands with {notAvailable, inForce, adopted, deprecated, superseded}.-->
<!-- NAP Example -->
<!--
<gmd:CI_DateTypeCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_87"
codeListValue="RI_367">publication</gmd:CI_DateTypeCode>
-->
<!-- ISO Example -->
<gmd:CI_DateTypeCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode"
codeListValue="publication">publication</gmd:CI_DateTypeCode>
</gmd:dateType>
</gmd:CI_Date>
</gmd:date>
<!-- (C-C) Unique resource identifier - NAP makes MD_Identifier mandatory for dataset and dataset series.
For USGIN purposes, this element content value should be only considered an identifier for the citation, without any assumption that it will use http protocol. The identifier may be resolvable to a URL, if a protocol prefix specifies an identifier scheme that is resolvable (e.g. http, urn…), but this is not necessary for a valid document, and should not be assumed when processing metadata documents.
For USGIN, IF the Citation has an identifier that is different from the identifier for the described resource (MD_Metadata/dataSetURI), it must be included here. RS_Identifier may substitute for MD_Identifier in the ISO19139 schema, but the USGIN profile requires use of MD_Identifer. If additional codespace and version content is associated with the identifier, it should be encoded as MD_Identifier/authority/ CI_Citation/ alternateTitle and MD_Identifier/ authority/ CI_Citation/ edition -->
<!--
<gmd:identifier>
<gmd:MD_Identifier>
<gmd:code>
--><!-- 13 digit ISBN example --><!--
<gco:CharacterString>urn:isbn:000-0-000-00000-0</gco:CharacterString>
</gmd:code>
</gmd:MD_Identifier>
</gmd:identifier>
-->
<!-- (M-M) Resource responsible party - USGIN requires at least one CI_ResponsibleParty following the NAP rule. Best practice is to include point of contact information for the resource in MD_DataIdentification/pointOfContact/CI_ResponsibleParty. -->
<gmd:citedResponsibleParty>
<gmd:CI_ResponsibleParty>
<!-- (C-C) (individualName + organisationName + positionName) > 0 -->
<gmd:individualName>
<gco:CharacterString>Steve Rauzi</gco:CharacterString>
</gmd:individualName>
<gmd:organisationName>
<gco:CharacterString>Arizona Geological Survey</gco:CharacterString>
</gmd:organisationName>
<gmd:positionName>
<gco:CharacterString>Oil and Gas Administrator</gco:CharacterString>
</gmd:positionName>
<!-- (O-C) Contact Information - (phone + deliveryPoint + electronicMailAddress ) > 0. -->
<gmd:contactInfo>
<gmd:CI_Contact>
<gmd:phone>
<gmd:CI_Telephone>
<gmd:voice>
<gco:CharacterString>520-770-3500</gco:CharacterString>
</gmd:voice>
<gmd:facsimile>
<gco:CharacterString>520-770-3505</gco:CharacterString>
</gmd:facsimile>
</gmd:CI_Telephone>
</gmd:phone>
<gmd:address>
<gmd:CI_Address>
<gmd:deliveryPoint>
<gco:CharacterString>416 W. Congress St., Suite 100</gco:CharacterString>
</gmd:deliveryPoint>
<gmd:city>
<gco:CharacterString>Tucson</gco:CharacterString>
</gmd:city>
<gmd:administrativeArea>
<gco:CharacterString>Arizona</gco:CharacterString>
</gmd:administrativeArea>
<gmd:postalCode>
<gco:CharacterString>85701</gco:CharacterString>
</gmd:postalCode>
<gmd:country>
<gco:CharacterString>USA</gco:CharacterString>
</gmd:country>
<gmd:electronicMailAddress>
<gco:CharacterString>[email protected]</gco:CharacterString>
</gmd:electronicMailAddress>
</gmd:CI_Address>
</gmd:address>
</gmd:CI_Contact>
</gmd:contactInfo>
<!-- (M-M) ISO 19139 Mandatory: contact role - Guidance on use of role codes would be helpful for consistency, but has not been developed as yet.. -->
<gmd:role>
<!-- CI_RoleCode names: {resourceProvider, custodian, owner, user, distributor, originator, pointOfContact, principalInvestigator, processor, publisher, author} - NAP expands with {collaborator, editor, mediator, rightsHolder}. -->
<!-- NAP example -->
<!--
<gmd:CI_RoleCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_90"
codeListValue="RI_414">pointOfContact</gmd:CI_RoleCode>
-->
<!-- ISO example -->
<gmd:CI_RoleCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#CI_RoleCode"
codeListValue="pointOfContact">point of contact</gmd:CI_RoleCode>
</gmd:role>
</gmd:CI_ResponsibleParty>
</gmd:citedResponsibleParty>
<!-- (O-C) Dataset Presentation Form - USGIN mandates required if there is a significant difference between the resource’s presentation format and distribution format. -->
<!--
<gmd:presentationForm>
--><!-- CI_PresentationFormCode names: {documentDigital, documentHardcopy, imageDigital, image-Hardcopy, mapDigital, mapHardcopy, modelDigital, model-Hardcopy, profileDigital, profileHardcopy, tableDigital, tableHardcopy, videoDigital, videoHardcopy, audioDigital} - NAP expands with {audioHardcopy, multimediaDigital, multimediaHardcopy, diagramDigital, diagramHardcopy}.-->
<!-- NAP Example -->
<!--
<gmd:CI_PresentationFormCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_89"
codeListValue="RI_391">mapDigital</gmd:CI_PresentationFormCode>
-->
<!-- ISO Example -->
<!--
<gmd:CI_PresentationFormCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#CI_PresentationFormCode"
codeListValue="mapDigital">digital map</gmd:CI_PresentationFormCode>
</gmd:presentationForm>
-->
<!-- (O-O) Resource series - Information about the series or collection of which the cited resource is a part. Follow NAP rule (name + issueIdentification) > 0. -->
<!--
<gmd:series>
<gmd:CI_Series>
<gmd:name>
--><!-- Name of the publication series or aggregate dataset of which the referenced dataset is a part. --><!--
<gco:CharacterString>Borehole Collection</gco:CharacterString>
</gmd:name>
<gmd:issueIdentification>
--><!-- Identification of the series’ issue information. --><!--
<gco:CharacterString>Volume 10</gco:CharacterString>
</gmd:issueIdentification>
<gmd:page>
--><!-- Identification of the articles’ page number(s). --><!--
<gco:CharacterString>100-110</gco:CharacterString>
</gmd:page>
</gmd:CI_Series>
</gmd:series>
-->
<!-- (O-O) Resource other citation details -->
<!--
<gmd:otherCitationDetails/>
-->
<!-- (O-C) Resource collective title - Title of the combined resource that the cited resource is part of, for example the cited resource may be a paper in an anthology, in which case the anthology title would be the collective title. Required if the cited resource is part of such a collective work. -->
<!--
<gmd:collectiveTitle/>
-->
</gmd:CI_Citation>
</gmd:citation>
<!-- (M-M) Resource Abstract - A free text summary of the content, significance, purpose, scope, etc. of the resource. Exactly one value. -->
<gmd:abstract>
<gco:CharacterString>Digital files containing Tiff images of scanned logs. Scanned using Neutra scanner hardware.</gco:CharacterString>
</gmd:abstract>
<!-- (O-O) Resource purpose - Summary of the intentions for which the dataset was developed. Purpose includes objectives for creating the dataset and what the dataset is to support. -->
<!--
<gmd:purpose/>
-->
<!-- (M-M) Resource Status - -->
<gmd:status>
<!-- MD_ProgressCode names: {completed, historicalArchive, obsolete, onGoing, planned, required, underDevelopment} - NAP expands with {proposed}. Obsolete is synonymous with deprecated. -->
<!-- NAP Example -->
<!--
<gmd:MD_ProgressCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_106"
codeListValue="RI_593">completed</gmd:MD_ProgressCode>
-->
<!-- ISO Example -->
<gmd:MD_ProgressCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_ProgressCode"
codeListValue="completed">completed</gmd:MD_ProgressCode>
</gmd:status>
<!-- (O-C) Resource point of contact - CI_ResponsibleParty element here would contain information for point of contact to access the resource. This information is mandatory for physical resources such as core, cuttings, samples, manuscripts. -->
<gmd:pointOfContact>
<gmd:CI_ResponsibleParty>
<!-- (M-M) (individualName + organisationName + positionName) > 0 -->
<gmd:individualName>
<gco:CharacterString>Steve Rauzi</gco:CharacterString>
</gmd:individualName>
<gmd:organisationName>
<gco:CharacterString>Arizona Geological Survey</gco:CharacterString>
</gmd:organisationName>
<gmd:positionName>
<gco:CharacterString>Oil and Gas Administrator</gco:CharacterString>
</gmd:positionName>
<!-- (O-C) Contact Information - If a resource point of contact is required then (phone + deliveryPoint + electronicMailAddress) > 0. -->
<gmd:contactInfo>
<gmd:CI_Contact>
<gmd:phone>
<gmd:CI_Telephone>
<gmd:voice>
<gco:CharacterString>520-770-3500</gco:CharacterString>
</gmd:voice>
<gmd:facsimile>
<gco:CharacterString>520-770-3505</gco:CharacterString>
</gmd:facsimile>
</gmd:CI_Telephone>
</gmd:phone>
<gmd:address>
<gmd:CI_Address>
<gmd:deliveryPoint>
<gco:CharacterString>416 W. Congress St., Suite 100</gco:CharacterString>
</gmd:deliveryPoint>
<gmd:city>
<gco:CharacterString>Tucson</gco:CharacterString>
</gmd:city>
<gmd:administrativeArea>
<gco:CharacterString>Arizona</gco:CharacterString>
</gmd:administrativeArea>
<gmd:postalCode>
<gco:CharacterString>85701</gco:CharacterString>
</gmd:postalCode>
<gmd:country>
<gco:CharacterString>USA</gco:CharacterString>
</gmd:country>
<gmd:electronicMailAddress>
<gco:CharacterString>[email protected]</gco:CharacterString>
</gmd:electronicMailAddress>
</gmd:CI_Address>
</gmd:address>
</gmd:CI_Contact>
</gmd:contactInfo>
<!-- (M-M) ISO 19139 Mandatory: contact role - Guidance on use of role codes would be helpful for consistency, but has not been developed as yet. -->
<gmd:role>
<!-- CI_RoleCode names: {resourceProvider, custodian, owner, user, distributor, originator, pointOfContact, principalInvestigator, processor, publisher, author} - NAP expands with {collaborator, editor, mediator, rightsHolder}. -->
<!-- NAP example -->
<!--
<gmd:CI_RoleCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_90"
codeListValue="RI_414">pointOfContact</gmd:CI_RoleCode>
-->
<!-- ISO example -->
<gmd:CI_RoleCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#CI_RoleCode"
codeListValue="pointOfContact">point of contact</gmd:CI_RoleCode>
</gmd:role>
</gmd:CI_ResponsibleParty>
</gmd:pointOfContact>
<!-- (O-O) Resource Maintenance - This element provides information about the maintenance schedule or history of the resource (or some subset/part of the resource specified by the scope and scope description) described by the metadata record. 0 to many MD_MaintenanceInformation elements may be included. -->
<gmd:resourceMaintenance>
<gmd:MD_MaintenanceInformation>
<gmd:maintenanceAndUpdateFrequency>
<!-- MD_MaintenanceFrequencyCode names: {continual, daily, weekly, fortnightly, monthly, quarterly, biannually, annually, asNeeded, irregular, not-Planned, unknown} - NAP expands with {semimonthly}. -->
<!-- NAP Example -->
<!--
<gmd:MD_MaintenanceFrequencyCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_102"
codeListValue="RI_540">asNeeded</gmd:MD_MaintenanceFrequencyCode>
-->
<!-- ISO Example -->
<gmd:MD_MaintenanceFrequencyCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_MaintenanceFrequencyCode"
codeListValue="asNeeded">as needed</gmd:MD_MaintenanceFrequencyCode>
</gmd:maintenanceAndUpdateFrequency>
</gmd:MD_MaintenanceInformation>
</gmd:resourceMaintenance>
<!-- (O-O) Graphic overview of resource - USGIN best practice is to provide xlink:href URL to file if it is available online, as an attribute of the MD_BrowseGraphic element. If MD_BrowseGraphic is included, MD_BrowseGraphic/filename character string is mandatory. Recommended practice is to use the Anchor extension of CharacterString xml element from ISO19139, which provides a url as an attribute and a text string as a label for the link. -->
<gmd:graphicOverview>
<gmd:MD_BrowseGraphic>
<gmd:fileName>
<gco:CharacterString>http://azgs.az.gov/resource/00C02E67-F1ED-473D-A240-068CCB041A73/preview.jpg</gco:CharacterString>
</gmd:fileName>
<gmd:fileDescription>
<gco:CharacterString>preview map</gco:CharacterString>
</gmd:fileDescription>
<!-- Use napMD_FileFormatCode code list (http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_115). List names are {bil, bmp, bsq, bzip2, cdr, cgm, cover, csv, dbf, dgn, doc, dwg, dxf, e00, ecw, eps, ers, gdb, geotiff, gif, gml, grid, gzip, html, jpg, mdb, mif, pbm, pdf, png, ps, rtf, sdc, shp, sid, svg, tab, tar, tiff, txt, xhtml, xls, xml, xwd, zip, wpd} See Codelists section for discussion of encoding of codelist values. Note that to use this napm namespace extension in a valid xml document, the namespace declaration xmlns:napm=http://www.cits.rncan.gc.ca/html/brodeurj/.protege/.napMetadata/napMetadataWebsite/napMetadataTools/napXsd/napm must be included in the root element of the document. -->
<!-- The current napm.xsd schema conflicts with gmd because it refernces a local copy of the OGC gmd schema at http://www.cits.rncan.gc.ca/html/brodeurj/.protege/.napMetadata/tools/napXsd/gmd/ Until this is resolved, the gmd:fileType attributes can be omitted. However, USGIN requires the use of napMD_FileFormatCode names. -->
<!-- NAP Example -->
<!--
<gmd:fileType
xsi:type="napm:napMD_FileFormatCode_PropertyType"
codeList="http://www.fgdc.gov/nap/metadata/register/registerItemClasses.html#IC_115"
codeListValue="RI_711">
<gco:CharacterString>jpg</gco:CharacterString>
</gmd:fileType>
-->
<!-- ISO Example -->
<gmd:fileType>
<gco:CharacterString>jpg</gco:CharacterString>
</gmd:fileType>
</gmd:MD_BrowseGraphic>
</gmd:graphicOverview>
<!-- (X-X) Resource Format - This element is not used by NAP or USGIN; this information is encoded in MD_Metadata/distributionInfo/MD_Distribution/ in USGIN metadata. -->
<!--
<gmd:resourceForma/>
-->
<!-- (O-O) Resource keywords - Best Practice for USGIN profile metadata is to supply keywords to facilitate the discovery of metadata records relevant to the user. USGIN requires that MD_Keyword/keyword contain a CharacterString. USGIN best practice is to include keywords in English -->
<!-- Theme keywords -->
<gmd:descriptiveKeywords>
<gmd:MD_Keywords>
<gmd:keyword>
<gco:CharacterString>Scanned Gamma Ray Neutron</gco:CharacterString>
</gmd:keyword>
<gmd:keyword>
<gco:CharacterString>NMAL</gco:CharacterString>
</gmd:keyword>
<gmd:keyword>
<gco:CharacterString>borehole</gco:CharacterString>
</gmd:keyword>
<!-- Keyword Type - allowed values from MD_KeywordTypeCode names: {discipline, place, stratum, temporal, theme} - NAP expands with {product, subTopicCategory}. -->
<gmd:type>
<!-- NAP Example -->
<!--
<gmd:MD_KeywordTypeCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_101"
codeListValue="RI_528">theme</gmd:MD_KeywordTypeCode>
-->
<!-- ISO Example -->
<gmd:MD_KeywordTypeCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode"
codeListValue="theme">theme</gmd:MD_KeywordTypeCode>
</gmd:type>
</gmd:MD_Keywords>
</gmd:descriptiveKeywords>
<!-- Temporal keywords -->
<gmd:descriptiveKeywords>
<gmd:MD_Keywords>
<gmd:keyword>
<gco:CharacterString>Frasian</gco:CharacterString>
</gmd:keyword>
<gmd:keyword>
<gco:CharacterString>Upper Devonian</gco:CharacterString>
</gmd:keyword>
<gmd:keyword>
<gco:CharacterString>Devonian</gco:CharacterString>
</gmd:keyword>
<gmd:keyword>
<gco:CharacterString>Paleozoic</gco:CharacterString>
</gmd:keyword>
<!-- Keyword Type - allowed values from MD_KeywordTypeCode names: {discipline, place, stratum, temporal, theme} - NAP expands with {product, subTopicCategory}. -->
<gmd:type>
<!-- NAP Example -->
<!--
<gmd:MD_KeywordTypeCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_101"
codeListValue="RI_527">temporal</gmd:MD_KeywordTypeCode>
-->
<!-- ISO Example -->
<gmd:MD_KeywordTypeCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode"
codeListValue="temporal">temporal</gmd:MD_KeywordTypeCode>
</gmd:type>
</gmd:MD_Keywords>
</gmd:descriptiveKeywords>
<!-- Place keywords -->
<gmd:descriptiveKeywords>
<gmd:MD_Keywords>
<gmd:keyword>
<gco:CharacterString>Arizona</gco:CharacterString>
</gmd:keyword>
<gmd:keyword>
<gco:CharacterString>T41N R27E S22 NE NE</gco:CharacterString>
</gmd:keyword>
<!-- Keyword Type - allowed values from MD_KeywordTypeCode names: {discipline, place, stratum, temporal, theme} - NAP expands with {product, subTopicCategory}. -->
<gmd:type>
<!-- NAP Example -->
<!--
<gmd:MD_KeywordTypeCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_101"
codeListValue="RI_525">place</gmd:MD_KeywordTypeCode>
-->
<!-- ISO Example -->
<gmd:MD_KeywordTypeCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode"
codeListValue="place">place</gmd:MD_KeywordTypeCode>
</gmd:type>
</gmd:MD_Keywords>
</gmd:descriptiveKeywords>
<!-- (O-O) Condition applying to access and use of resource - Follow NAP for specification of resourceConstraints. This attribute provides information for access control to the described resource itself. In some situations, the metadataConstraints may allow a user to learn of the existence of a resource that they may not actually be able to access without further clearance. Constraints may be represented by MD_Constraint, MD_LegalConstraint, or MD_SecurityConstraint. -->
<gmd:resourceConstraints>
<gmd:MD_LegalConstraints>
<gmd:useLimitation>
<gco:CharacterString>none</gco:CharacterString>
</gmd:useLimitation>
</gmd:MD_LegalConstraints>
</gmd:resourceConstraints>
<!-- (O-O) Aggregation information - The citation for or name of an aggregate dataset, the type of aggregate dataset, and optionally the activity which produced the dataset. -->
<gmd:aggregationInfo>
<!-- MD_AggregateInformation requires either aggregateDataSetName/CI_Citation or aggregateDataSetIdentifier/MD_Identifier. -->
<gmd:MD_AggregateInformation>
<!-- Related dataset name -->
<gmd:aggregateDataSetName>
<gmd:CI_Citation>
<gmd:title>
<gco:CharacterString>Related Resource's Title</gco:CharacterString>
</gmd:title>
<gmd:date>
<gmd:CI_Date>
<gmd:date>
<gco:DateTime>2001-12-17T09:30:47</gco:DateTime>
</gmd:date>
<gmd:dateType>
<!-- NAP Example -->
<!--
<gmd:CI_DateTypeCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_87"
codeListValue="RI_367">publication</gmd:CI_DateTypeCode>
-->
<!-- ISO Example -->
<gmd:CI_DateTypeCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode"
codeListValue="publication">publication</gmd:CI_DateTypeCode>
</gmd:dateType>
</gmd:CI_Date>
</gmd:date>
</gmd:CI_Citation>
</gmd:aggregateDataSetName>
<!-- Data Set Identifier -->
<gmd:aggregateDataSetIdentifier>
<gmd:MD_Identifier>
<gmd:code>
<gco:CharacterString>00000000-0000-0000-0000-000000000000</gco:CharacterString>
</gmd:code>
</gmd:MD_Identifier>
</gmd:aggregateDataSetIdentifier>
<!-- (M-M) Association Type is mandatory.. -->
<gmd:associationType>
<!-- Use DS_AssociationTypeCode names: {crossReference, largerWorkCitation, partOfSeamlessDatabase, source, stereoMate} - NAP expands with {isComposedOf}. -->
<!-- NAP Example -->
<!--
<gmd:DS_AssociationTypeCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_92"
codeListValue="RI_428">crossReference</gmd:DS_AssociationTypeCode>
-->
<!-- ISO Example -->
<gmd:DS_AssociationTypeCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#DS_AssociationTypeCode"
codeListValue="crossReference">cross reference</gmd:DS_AssociationTypeCode>
</gmd:associationType>
</gmd:MD_AggregateInformation>
</gmd:aggregationInfo>
<!-- (O-O) Spatial Representation Type - napMD_SpatialRepresentationTypeCode names {vector, grid, textTable, tin, stereoModel, video} -->
<!--
<gmd:spatialRepresentationType/>
-->
<!-- (C-C) Resource spatial resolution - USGIN requires use of equivalentScale/../denominator to express spatial resolution, in order to be more easily interoperable. -->
<gmd:spatialResolution>
<gmd:MD_Resolution>
<gmd:equivalentScale>
<gmd:MD_RepresentativeFraction>
<gmd:denominator>
<gco:Integer>100000</gco:Integer>
</gmd:denominator>
</gmd:MD_RepresentativeFraction>
</gmd:equivalentScale>
</gmd:MD_Resolution>
</gmd:spatialResolution>
<!-- (M-M) Resource language - Multiple instances of this element indicate that the linguistic content of the resource is available in multiple languages -->
<gmd:language>
<!-- (M-M) Metadata language - use the ISO639-2/T three letter language code in lower case. -->
<gco:CharacterString>eng</gco:CharacterString>
</gmd:language>
<!-- (C-C) Topic category - NAP specifies that topicCategory code shall be provided when hierarchyLevel is set to "dataset" or “dataset series”. Most USGIN resources will have topicCategory=”geoscientificInformation”, which is the default value for this profile. More specific topic categorization should be done using keywords. NAP declares not applicable to services. -->
<gmd:topicCategory>
<!-- MD_TopicCategoryCode names: {farming, biota, boundaries, climatologyMeterologyAtmosphere, economy, elevation, environment, geoscientificInformation, health, imageryBaseMapsEarthCover, intelligenceMilitary, inlandWater, location, oceans, planningCadastre, society, structure, transportation, utilitiesCommunication} -->
<gmd:MD_TopicCategoryCode>geoscientificInformation</gmd:MD_TopicCategoryCode>
</gmd:topicCategory>
<!-- (C-C) Resource content extent - Defines the spatial (horizontal and vertical) and temporal region to which the content of the resource applies. For USGIN, the spatial extent is a rectangle that bounds the geographic extent to which resource content applies. NAP specifies required when hierarchyLevel is set to ‘dataset’. USGIN specifies (description + geographicElement + temporalElement) > 0. -->
<gmd:extent>
<gmd:EX_Extent>
<!-- (C-C) Resource Content extent description - Free text that describes the spatial and temporal extent of the dataset. USGIN specifies that description is mandatory if a geographicElement or temporalElement is not provided. Note that if geographic place names are used to express the geographic extent, USGIN profile specifies that these should be encoded using keyword with keyword type code = ‘place.’ Geographic names may be duplicated in the EX_Extent/description. -->
<gmd:description>
<gco:CharacterString>Some spatio-temporal description.</gco:CharacterString>
</gmd:description>
<!-- (O-C) Resource content extent bounding box -USGIN profile requires that if an EX_Extent/geographicElement is supplied, it include a geographic bounding box with bounding latitude and longitude expressed using WGS 84 decimal degrees. The corner coordinates for the geographic bounding box must not coincide in one point, because this may result in fatal errors with some CSW implementations. Point locations must thus be represented as tiny rectangles. USGIN recommended practice is to place the actual point location in the lower left corner of the rectangle. -->
<gmd:geographicElement>
<gmd:EX_GeographicBoundingBox>
<gmd:extentTypeCode>
<gco:Boolean>1</gco:Boolean>
</gmd:extentTypeCode>
<gmd:westBoundLongitude>
<gco:Decimal>-109.911001</gco:Decimal>
</gmd:westBoundLongitude>
<gmd:eastBoundLongitude>
<gco:Decimal>-109.910999</gco:Decimal>
</gmd:eastBoundLongitude>
<gmd:southBoundLatitude>
<gco:Decimal>34.772899</gco:Decimal>
</gmd:southBoundLatitude>
<gmd:northBoundLatitude>
<gco:Decimal>34.772901</gco:Decimal>
</gmd:northBoundLatitude>
</gmd:EX_GeographicBoundingBox>
</gmd:geographicElement>
<!-- (C-X) Resource content extent geographic description - Not used by USGIN profile, use keyword with type code = ‘place’ (with thesaurus if necessary). -->
<!--
<gmd:geographicElement>
<gmd:EX_GeographicDescription/>
</gmd:geographicElement>
-->
<!-- (C-X) Resource content extent bounding polygon - Not used by USGIN profile. To improve interoperability, USGIN mandates the use of Geographic Bounding Box instead of bounding polygon. “An element which describes inclusions or exclusions in a resource. The enclosed boundary of the dataset expressed in x-y coordinates.” NAP mandates this element if no other Geographic Bounding Box, Geographic Description, Temporal Element, or Vertical Element are provided. -->
<!--
<gmd:geographicElement>
<gmd:EX_BoundingPolygon/>
</gmd:geographicElement>
-->
</gmd:EX_Extent>
</gmd:extent>
<!-- (O-O) Resource temporal extent - -->
<gmd:extent>
<gmd:EX_Extent>
<gmd:temporalElement>
<gmd:EX_TemporalExtent>
<gmd:extent>
<!-- Default ISO time frame example -->
<!--
<gml:TimePeriod gml:id="IdModern">
<gml:name>Y2KX</gml:name>
--><!-- USGIN requires the beginPosition and endPosition's frame property to be defined. The default value is #ISO-8601. --><!--
<gml:beginPosition frame="#ISO-8601">2010-01-00T00:00:00</gml:beginPosition>
<gml:endPosition frame="#ISO-8601">2010-12-31T24:00:00</gml:endPosition>
</gml:TimePeriod>
-->
<!-- Geologic time frame example -->
<gml:TimePeriod gml:id="IdJurassic">
<gml:name>Jurassic</gml:name>
<!-- USGIN requires the beginPosition and endPosition's frame property to be defined. The default value is #ISO-8601. -->
<gml:beginPosition frame="urn:cgi:trs:CGI:StandardGeologicTimeMa">203</gml:beginPosition>
<gml:endPosition frame="urn:cgi:trs:CGI:StandardGeologicTimeMa ">135</gml:endPosition>
</gml:TimePeriod>
</gmd:extent>
</gmd:EX_TemporalExtent>
</gmd:temporalElement>
</gmd:EX_Extent>
</gmd:extent>
<!-- (O-X) Resource spatio-temporal extent - Not used. Although use of EX_SpatialTemporalExtent is allowed by ISO19139 and NAP, USGIN mandates encoding space time location with EX_TemporalExtent and EX_GeographicBoundingBox. -->
<!--
<gmd:extent>
<gmd:EX_Extent>
<gmd:temporalElement>
<gmd:EX_SpatialTemporalExtent/>
</gmd:temporalElement>
</gmd:EX_Extent>
</gmd:extent>
-->
<!-- (O-O) Resource vertical extent -->
<gmd:extent>
<gmd:EX_Extent>
<gmd:verticalElement>
<gmd:EX_VerticalExtent>
<gmd:minimumValue>
<gco:Real>-100</gco:Real>
</gmd:minimumValue>
<gmd:maximumValue>
<gco:Real>200</gco:Real>
</gmd:maximumValue>
<!-- Use EPSG register of geodetic parameters such as at http://www.epsg-registry.org/. The default VerticalCRS is World mean sea level (MSL): urn:ogc:def:crs:EPSG::5714 -->
<gmd:verticalCRS xlink:href="urn:ogc:def:crs:EPSG::5714 "/>
</gmd:EX_VerticalExtent>
</gmd:verticalElement>
</gmd:EX_Extent>
</gmd:extent>
</gmd:MD_DataIdentification>
</gmd:identificationInfo>
<!-- **************** -->
<!-- (O-O) Content information - Characteristics describing the feature cataloguecatalog, coverage, or image data. USGIN currently makes no recommendation for use of contentInfo; follow NAP recommendations (see INCITS 453). -->
<!--
<gmd:contentInfo/>
-->
<!-- (O-O) Resource distribution information - This element provides information to inform users how to obtain or access the described resource. NOTE: there are several ways elements can be nested within MD_Distribution -->
<gmd:distributionInfo>
<gmd:MD_Distribution>
<!-- (O-O) Resource distribution format - Information on the format or physical manifestation of the resource. If the resource is a physical resource, like a book, rock sample, paper document, the distributionFormat/MD_Format/name is mandatory, and must be from the USGIN distribution format codelist. -->
<!--
<gmd:distributionFormat/>
-->
<!-- (O-C) Resource distributor information - USGIN differs from NAP in this case (but not with ISO19115) by allowing multiple distributors, and binding between distributors, transfer options, and formats. -->
<gmd:distributor>
<!-- For USGIN profile, each distributor/MD_Distributor is a binding between one or more transfer options and the distributor formats that are available through that/those transfer options (MD_DigitalTransferOptions/onLine/CI_OnlineResource in particular). If different formats are available from the same distributor, or have different transfer options, these should be represented as different distributor/MD_Distributor instances. See the USGIN Profile section ‘Use of MD_Distribution and MD_Distributor’ for instructions on use of these elements. -->
<gmd:MD_Distributor>
<gmd:distributorContact>
<!-- (C-C) Distribution responsible party - For CI_ResponsibleParty, count of (individualName + organisationName + positionName) > 0 -->
<gmd:CI_ResponsibleParty>
<gmd:organisationName>
<gco:CharacterString>Arizona Geological Survey</gco:CharacterString>
</gmd:organisationName>
<!-- (C-C) If CI_ResponsibleParty exists, the role element is required -->
<gmd:role>
<!-- Use CI_RoleCode names {resourceProvider, custodian, owner, user, distributor, originator, pointOfContact, principalInvestigator, processor, publisher, author} - NAP expands with {collaborator, editor, mediator, rightsHolder}. -->
<!-- NAP Example -->
<!--
<gmd:CI_RoleCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_90"
codeListValue="RI_412">distributor</gmd:CI_RoleCode>
-->
<!-- ISO Example -->
<gmd:CI_RoleCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#CI_RoleCode"
codeListValue="distributor">distributor</gmd:CI_RoleCode>
</gmd:role>
</gmd:CI_ResponsibleParty>
</gmd:distributorContact>
<!-- (O-O) Resource distributor order process - Information on the availability of the service which includes at least one of fees, available date and time, ordering instructions, or turnaround. -->
<gmd:distributionOrderProcess>
<gmd:MD_StandardOrderProcess>
<gmd:fees>
<gco:CharacterString>variable fees</gco:CharacterString>
</gmd:fees>
<gmd:orderingInstructions>
<gco:CharacterString>ordering instructions</gco:CharacterString>
</gmd:orderingInstructions>
<gmd:turnaround>
<gco:CharacterString>one to two weeks.</gco:CharacterString>
</gmd:turnaround>
</gmd:MD_StandardOrderProcess>
</gmd:distributionOrderProcess>
<!-- (O-C) Resource distributor format - USGIN profile specifies that the distributionInfo/MD_Distribution/distributionFormat may be included in the document (its schema valid...), but distribution format information must be duplicated in a distributionInfo/distributor/MD_Distributor/distributorFormat element or the content can be lost -->
<gmd:distributorFormat>
<gmd:MD_Format>
<!-- Use USGIN distribution format code values. See the "Online resource format names" section of the USGIN Profile -->
<gmd:name>
<gco:CharacterString>Adobe:Acrobat/pdf</gco:CharacterString>
</gmd:name>
<gmd:version>
<gco:CharacterString>8.0</gco:CharacterString>
</gmd:version>
</gmd:MD_Format>
</gmd:distributorFormat>
<!-- Resource distributor transfer options - Provides information about the technical means and media used by the distributor. -->
<gmd:distributorTransferOptions>
<gmd:MD_DigitalTransferOptions>
<gmd:onLine>
<gmd:CI_OnlineResource>
<!-- (M-M) Resource distributor on-line distribution linkage - Digital transfer options are “technical means and media by which a dataset is obtained from the distributor.” NAP requires CI_OnlineResource/linkage and CI_OnlineResource/protocol in CI_OnlineResource. -->
<gmd:linkage>
<!-- The linkage element should contain the complete URL to access the resource directly. CI_Online-Resource requires a Linkage element that is a gmd:URL. -->
<gmd:URL>http://azgs.az.gov/resource/00C02E67-F1ED-473D-A240-068CCB041A73/borehole_report.pdf</gmd:URL>
</gmd:linkage>
<gmd:protocol>
<!-- The protocol element defines a valid internet protocol used to access the resource. NAP recommended best practice is that the protocol should be taken from an official controlled list such as the Official Internet Protocol Standards published on the Web at http://www.rfc-editor.org/rfcxx00.html or the Internet Assigned Numbers Authority (IANA) at http://www.iana.org/numbers.html. ‘ftp’ or ‘http’ are common values. -->
<gco:CharacterString>http</gco:CharacterString>
</gmd:protocol>
<!-- (C-C) Resource distributor online distribution application profile - applicationProfile is required if the CI_OnlineResource/linkage does not connect to a web page, and another software application is needed to use the indicated file resource. The applicationProfile character string should specify the software using the following recommended syntax: “vendor:application name/application version”, e.g. “Microsoft:Word/2007”, or “ESRI:ArcGIS/9.3” -->
<gmd:applicationProfile>
<gco:CharacterString>Adobe:Acrobat/8.0</gco:CharacterString>
</gmd:applicationProfile>
<gmd:name>
<!-- The CI_OnlineResource/name element may duplicate the file name if the URL is a link to a file, but it is recommended to provide a user-friendly label for the file that could be presented in a user interface. -->
<gco:CharacterString>borehole_report.pdf</gco:CharacterString>
</gmd:name>
<gmd:description>
<gco:CharacterString>Downloadable PDF document</gco:CharacterString>
</gmd:description>
<!-- (O-C) Resource distributor online distribution function - CI_OnlineResource/function is required by USGIN to indicate how linkage is to be used. If the resource is accessible as a web service, the metadata for the service should be separate metadata record with the dataset(s) exposed through the service identified in the service metadata record as coupledResources. -->
<gmd:function>
<!-- CI_OnlineFunctionCode names: {download, information, offlineAccess, order, search} - NAP expands with {upload, webService, emailService, browsing, fileAccess, webMapService}. -->
<!-- NAP Example -->
<!--
<gmd:CI_OnLineFunctionCode
codeList="http://www.fgdc.gov/nap/metadata/register/codelists.html#IC_88"
codeListValue="RI_375">download</gmd:CI_OnLineFunctionCode>
-->
<!-- ISO Example -->
<gmd:CI_OnLineFunctionCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#CI_OnLineFunctionCode"
codeListValue="download">download</gmd:CI_OnLineFunctionCode>
</gmd:function>
</gmd:CI_OnlineResource>
</gmd:onLine>
</gmd:MD_DigitalTransferOptions>
</gmd:distributorTransferOptions>
</gmd:MD_Distributor>
</gmd:distributor>
<!-- (C-C) Resource distribution transfer options - MD_DigitalTransferOptions provides information on digital distribution of resource. See USGIN Profile ‘Use of MD_Distribution and MD_Distributor’ for instructions on use of this element. Details on encoding for MD_DigitalTransferOptions are above in the distributorTransferOptions elements description. -->
<!--
<gmd:transferOptions/>
-->
</gmd:MD_Distribution>
</gmd:distributionInfo>
<!-- (C-C) Data quality Information - NAP requires either dataQualityInfo/DQ_DataQuality/report or dataQualityInfo/ DQ_DataQuality/lineage if dataQualityInfo/DQ_DataQuality/scope/DQ_Scope/level = 'dataset'. -->
<gmd:dataQualityInfo>
<gmd:DQ_DataQuality>
<!-- (C-C) Data quality scope - Mandatory if DQ_DataQuality is not null. Specifies the extent of characteristics for which data quality information is reported. -->
<gmd:scope>
<gmd:DQ_Scope>
<gmd:level>
<!-- MD_ScopeCode names: {attribute, attributeType, collectionHardware, collectionSession, dataset, series, nonGeographicDataset, dimensionGroup, feature, featureType, propertyType, fieldSession, software, service, model, tile}. -->
<!-- NAP Example -->
<!--
<gmd:MD_ScopeCode