Changes
On May 26, 2021 at 1:33:26 AM UTC, seanh:
-
Updated description of Polar Geospatial Center(PGC) from
The Polar Geospatial Center provides geospatial support, mapping, and GIS/remote sensing solutions to researchers and logistics groups in the polar science community.
toThe Polar Geospatial Center provides geospatial support, mapping, and GIS/remote sensing solutions to researchers and logistics groups in the polar science community.
f | 1 | { | f | 1 | { |
2 | "author": "", | 2 | "author": "", | ||
3 | "author_email": "", | 3 | "author_email": "", | ||
4 | "creator_user_id": "2e9fa41b-0394-4070-98d0-205f79d5738b", | 4 | "creator_user_id": "2e9fa41b-0394-4070-98d0-205f79d5738b", | ||
5 | "extras": [ | 5 | "extras": [ | ||
6 | { | 6 | { | ||
7 | "key": "Country", | 7 | "key": "Country", | ||
8 | "value": "USA" | 8 | "value": "USA" | ||
9 | }, | 9 | }, | ||
10 | { | 10 | { | ||
11 | "key": "Data Management ", | 11 | "key": "Data Management ", | ||
12 | "value": "The NSF brings transparency to its long-standing | 12 | "value": "The NSF brings transparency to its long-standing | ||
13 | policy on dissemination and sharing of research results through the | 13 | policy on dissemination and sharing of research results through the | ||
14 | required inclusion of a data management plan with each project | 14 | required inclusion of a data management plan with each project | ||
15 | :https://www.nsf.gov/pubs/policydocs/pappguide/nsf16001/gpg_2.jsp#dmp. | 15 | :https://www.nsf.gov/pubs/policydocs/pappguide/nsf16001/gpg_2.jsp#dmp. | ||
16 | Plans for the dissemination and sharing of research results will be | 16 | Plans for the dissemination and sharing of research results will be | ||
17 | traceable from the beginning to the end of a project (proposal, | 17 | traceable from the beginning to the end of a project (proposal, | ||
18 | review, and annual/final report). The primary goal of this procedural | 18 | review, and annual/final report). The primary goal of this procedural | ||
19 | change is to assure that products of research help NSF achieve its | 19 | change is to assure that products of research help NSF achieve its | ||
20 | mission to promote the progress of science and engineering. Plans for | 20 | mission to promote the progress of science and engineering. Plans for | ||
21 | data management and sharing of the products of research. Proposals | 21 | data management and sharing of the products of research. Proposals | ||
22 | must include a supplementary document of no more than two pages | 22 | must include a supplementary document of no more than two pages | ||
23 | labeled \u0093Data Management Plan\u0094. This supplement should | 23 | labeled \u0093Data Management Plan\u0094. This supplement should | ||
24 | describe how the proposal will conform to NSF policy on the | 24 | describe how the proposal will conform to NSF policy on the | ||
25 | dissemination and sharing of research results (see AAG Chapter | 25 | dissemination and sharing of research results (see AAG Chapter | ||
26 | VI.D.4), and may include: the types of data, samples, physical | 26 | VI.D.4), and may include: the types of data, samples, physical | ||
27 | collections, software, curriculum materials, and other materials to be | 27 | collections, software, curriculum materials, and other materials to be | ||
28 | produced in the course of the project; the standards to be used for | 28 | produced in the course of the project; the standards to be used for | ||
29 | data and metadata format and content (where existing standards are | 29 | data and metadata format and content (where existing standards are | ||
30 | absent or deemed inadequate, this should be documented along with any | 30 | absent or deemed inadequate, this should be documented along with any | ||
31 | proposed solutions or remedies); policies for access and sharing | 31 | proposed solutions or remedies); policies for access and sharing | ||
32 | including provisions for appropriate protection of privacy, | 32 | including provisions for appropriate protection of privacy, | ||
33 | confidentiality, security, intellectual property, or other rights or | 33 | confidentiality, security, intellectual property, or other rights or | ||
34 | requirements; policies and provisions for re-use, re-distribution, | 34 | requirements; policies and provisions for re-use, re-distribution, | ||
35 | and the production of derivatives; and plans for archiving data, | 35 | and the production of derivatives; and plans for archiving data, | ||
36 | samples, and other research products, and for preservation of access | 36 | samples, and other research products, and for preservation of access | ||
37 | to them. Data management requirements and plans specific to the | 37 | to them. Data management requirements and plans specific to the | ||
38 | Directorate, Office, Division, Program, or other NSF unit, relevant to | 38 | Directorate, Office, Division, Program, or other NSF unit, relevant to | ||
39 | a proposal are available at: | 39 | a proposal are available at: | ||
40 | https://www.nsf.gov/bfa/dias/policy/dmp.jsp. If guidance specific to | 40 | https://www.nsf.gov/bfa/dias/policy/dmp.jsp. If guidance specific to | ||
41 | the program is not available, then the requirements established in | 41 | the program is not available, then the requirements established in | ||
42 | this section apply. Simultaneously submitted collaborative proposals | 42 | this section apply. Simultaneously submitted collaborative proposals | ||
43 | and proposals that include subawards are a single unified project and | 43 | and proposals that include subawards are a single unified project and | ||
44 | should include only one supplemental combined Data Management Plan, | 44 | should include only one supplemental combined Data Management Plan, | ||
45 | regardless of the number of non-lead collaborative proposals or | 45 | regardless of the number of non-lead collaborative proposals or | ||
46 | subawards included. Fastlane will not permit submission of a proposal | 46 | subawards included. Fastlane will not permit submission of a proposal | ||
47 | that is missing a Data Management Plan. Proposals for supplementary | 47 | that is missing a Data Management Plan. Proposals for supplementary | ||
48 | support to an existing award are not required to include a Data | 48 | support to an existing award are not required to include a Data | ||
49 | Management Plan. A valid Data Management Plan may include only the | 49 | Management Plan. A valid Data Management Plan may include only the | ||
50 | statement that no detailed plan is needed, as long as the statement is | 50 | statement that no detailed plan is needed, as long as the statement is | ||
51 | accompanied by a clear justification. Proposers who feel that the plan | 51 | accompanied by a clear justification. Proposers who feel that the plan | ||
52 | cannot fit within the supplement limit of two pages may use part of | 52 | cannot fit within the supplement limit of two pages may use part of | ||
53 | the 15-page Project Description for additional data management | 53 | the 15-page Project Description for additional data management | ||
54 | information. Proposers are advised that the Data Management Plan may | 54 | information. Proposers are advised that the Data Management Plan may | ||
55 | not be used to circumvent the 15-page Project Description limitation. | 55 | not be used to circumvent the 15-page Project Description limitation. | ||
56 | The Data Management Plan will be reviewed as an integral part of the | 56 | The Data Management Plan will be reviewed as an integral part of the | ||
57 | proposal, coming under Intellectual Merit or Broader Impacts or both, | 57 | proposal, coming under Intellectual Merit or Broader Impacts or both, | ||
58 | as appropriate for the scientific community of relevance." | 58 | as appropriate for the scientific community of relevance." | ||
59 | }, | 59 | }, | ||
60 | { | 60 | { | ||
61 | "key": "Data Policy", | 61 | "key": "Data Policy", | ||
62 | "value": "National Science Foundation\u00a0(PGC\u2019s primary | 62 | "value": "National Science Foundation\u00a0(PGC\u2019s primary | ||
63 | funding source)\u00a0policy\u00a0requires researchers to acknowledge | 63 | funding source)\u00a0policy\u00a0requires researchers to acknowledge | ||
64 | NSF\u00a0support in all publications, web pages, and media | 64 | NSF\u00a0support in all publications, web pages, and media | ||
65 | interviews.By accepting PGC\u2019s services, including access to data | 65 | interviews.By accepting PGC\u2019s services, including access to data | ||
66 | via the PGC website, users agree to cite PGC and its sponsorship by | 66 | via the PGC website, users agree to cite PGC and its sponsorship by | ||
67 | the NSF. The original source of any third-party data supplied by PGC | 67 | the NSF. The original source of any third-party data supplied by PGC | ||
68 | must also be properly attributed. Acknowledgement of PGC\u2019s | 68 | must also be properly attributed. Acknowledgement of PGC\u2019s | ||
69 | assistance provides PGC with valuable feedback and a measure of its | 69 | assistance provides PGC with valuable feedback and a measure of its | ||
70 | success in the scientific community. The National Science Foundation | 70 | success in the scientific community. The National Science Foundation | ||
71 | Office of Polar Programs (NSF OPP) requires that metadata, full data | 71 | Office of Polar Programs (NSF OPP) requires that metadata, full data | ||
72 | sets, and derived data products be deposited in a long-lived and | 72 | sets, and derived data products be deposited in a long-lived and | ||
73 | publicly accessible archive. Specific requirements for various OPP | 73 | publicly accessible archive. Specific requirements for various OPP | ||
74 | programs can be found in the NSF Dear Colleague Letter #16055. The | 74 | programs can be found in the NSF Dear Colleague Letter #16055. The | ||
75 | Arctic Data Center was created with funding from NSF to assist with | 75 | Arctic Data Center was created with funding from NSF to assist with | ||
76 | compliance of these requirements by providing that long-lived and | 76 | compliance of these requirements by providing that long-lived and | ||
77 | publicly accessible archive for Arctic Sciences Section (ARC) data and | 77 | publicly accessible archive for Arctic Sciences Section (ARC) data and | ||
78 | metadata. At a minimum, metadata describing ARC-supported data | 78 | metadata. At a minimum, metadata describing ARC-supported data | ||
79 | packages must be submitted to the Arctic Data Center. The Arctic Data | 79 | packages must be submitted to the Arctic Data Center. The Arctic Data | ||
80 | Center primarily stores metadata in structured, XML-based files. | 80 | Center primarily stores metadata in structured, XML-based files. | ||
81 | Transformation of plain text documentation into a structured metadata | 81 | Transformation of plain text documentation into a structured metadata | ||
82 | format for archiving is done automatically when submitting through the | 82 | format for archiving is done automatically when submitting through the | ||
83 | Arctic Data Center website. Prior to submitting documentation to the | 83 | Arctic Data Center website. Prior to submitting documentation to the | ||
84 | Arctic Data Center, we advise projects to create complete, plain text | 84 | Arctic Data Center, we advise projects to create complete, plain text | ||
85 | metadata records. Ideally, plans to create and store metadata records | 85 | metadata records. Ideally, plans to create and store metadata records | ||
86 | should be made during the initial stages of project development (i.e., | 86 | should be made during the initial stages of project development (i.e., | ||
87 | within the data management plan of the project proposal)." | 87 | within the data management plan of the project proposal)." | ||
88 | }, | 88 | }, | ||
89 | { | 89 | { | ||
90 | "key": "Data Sharing Principle", | 90 | "key": "Data Sharing Principle", | ||
91 | "value": "PGC has an archive of many\u00a0open data | 91 | "value": "PGC has an archive of many\u00a0open data | ||
92 | products\u00a0such as digital elevation models, historic and | 92 | products\u00a0such as digital elevation models, historic and | ||
93 | contemporary polar maps, and historic aerial photography. Open data is | 93 | contemporary polar maps, and historic aerial photography. Open data is | ||
94 | available at no cost. Licensed data, namely commercial satellite | 94 | available at no cost. Licensed data, namely commercial satellite | ||
95 | imagery, is available to PGC core users only." | 95 | imagery, is available to PGC core users only." | ||
96 | } | 96 | } | ||
97 | ], | 97 | ], | ||
98 | "groups": [ | 98 | "groups": [ | ||
99 | { | 99 | { | ||
100 | "description": "Inventory of Database for Earth Three Poles", | 100 | "description": "Inventory of Database for Earth Three Poles", | ||
101 | "display_name": "An Inventory of Database for Earth Three | 101 | "display_name": "An Inventory of Database for Earth Three | ||
102 | Poles", | 102 | Poles", | ||
103 | "id": "543d60c4-2ba5-4474-b3d2-47a5cd109ce8", | 103 | "id": "543d60c4-2ba5-4474-b3d2-47a5cd109ce8", | ||
104 | "image_display_url": | 104 | "image_display_url": | ||
105 | .142.79/uploads/group/2021-05-18-053212.318529inventurydatabase1.jpg", | 105 | .142.79/uploads/group/2021-05-18-053212.318529inventurydatabase1.jpg", | ||
106 | "name": "inventury-of-database-for-earth-three-poles", | 106 | "name": "inventury-of-database-for-earth-three-poles", | ||
107 | "title": "An Inventory of Database for Earth Three Poles" | 107 | "title": "An Inventory of Database for Earth Three Poles" | ||
108 | } | 108 | } | ||
109 | ], | 109 | ], | ||
110 | "id": "28b027b7-1328-40d3-8d62-8b6e26aadb9f", | 110 | "id": "28b027b7-1328-40d3-8d62-8b6e26aadb9f", | ||
111 | "isopen": true, | 111 | "isopen": true, | ||
112 | "license_id": "cc-by", | 112 | "license_id": "cc-by", | ||
113 | "license_title": "Creative Commons Attribution", | 113 | "license_title": "Creative Commons Attribution", | ||
114 | "license_url": "http://www.opendefinition.org/licenses/cc-by", | 114 | "license_url": "http://www.opendefinition.org/licenses/cc-by", | ||
115 | "maintainer": "", | 115 | "maintainer": "", | ||
116 | "maintainer_email": "", | 116 | "maintainer_email": "", | ||
117 | "metadata_created": "2020-10-14T01:32:23.638975", | 117 | "metadata_created": "2020-10-14T01:32:23.638975", | ||
n | 118 | "metadata_modified": "2021-05-21T11:02:02.289855", | n | 118 | "metadata_modified": "2021-05-26T01:33:26.141072", |
119 | "name": "polar-geospatial-center-pgc", | 119 | "name": "polar-geospatial-center-pgc", | ||
120 | "notes": "The Polar Geospatial Center provides geospatial support, | 120 | "notes": "The Polar Geospatial Center provides geospatial support, | ||
121 | mapping, and GIS/remote sensing solutions to researchers and logistics | 121 | mapping, and GIS/remote sensing solutions to researchers and logistics | ||
t | 122 | groups in the polar science community.", | t | 122 | groups in the polar science community. ", |
123 | "num_resources": 1, | 123 | "num_resources": 1, | ||
124 | "num_tags": 0, | 124 | "num_tags": 0, | ||
125 | "organization": { | 125 | "organization": { | ||
126 | "approval_status": "approved", | 126 | "approval_status": "approved", | ||
127 | "created": "2020-04-30T11:11:08.802657", | 127 | "created": "2020-04-30T11:11:08.802657", | ||
128 | "description": "Aerospace Information Research Institute (AIR) | 128 | "description": "Aerospace Information Research Institute (AIR) | ||
129 | under the Chinese Academy of Sciences (CAS) was established in July | 129 | under the Chinese Academy of Sciences (CAS) was established in July | ||
130 | 2017, following the approval for consolidation of three CAS | 130 | 2017, following the approval for consolidation of three CAS | ||
131 | institutes: the Institute of Electronics (IECAS), the Institute of | 131 | institutes: the Institute of Electronics (IECAS), the Institute of | ||
132 | Remote Sensing and Digital Earth (RADI), and the Academy of | 132 | Remote Sensing and Digital Earth (RADI), and the Academy of | ||
133 | Opto-Electronics (AOE) at CAS President Board Meeting. The merger is | 133 | Opto-Electronics (AOE) at CAS President Board Meeting. The merger is | ||
134 | the outcome of CAS efforts towards reformation of its R&D system to | 134 | the outcome of CAS efforts towards reformation of its R&D system to | ||
135 | meet future R&D challenges and to better meet the national demands.", | 135 | meet future R&D challenges and to better meet the national demands.", | ||
136 | "id": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | 136 | "id": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | ||
137 | "image_url": "2021-05-18-080509.992585AIRlogo.png", | 137 | "image_url": "2021-05-18-080509.992585AIRlogo.png", | ||
138 | "is_organization": true, | 138 | "is_organization": true, | ||
139 | "name": "air", | 139 | "name": "air", | ||
140 | "state": "active", | 140 | "state": "active", | ||
141 | "title": "Aerospace Information Research Institute, CAS", | 141 | "title": "Aerospace Information Research Institute, CAS", | ||
142 | "type": "organization" | 142 | "type": "organization" | ||
143 | }, | 143 | }, | ||
144 | "owner_org": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | 144 | "owner_org": "c25dce84-97be-4153-8b90-d38f9ab73e5f", | ||
145 | "private": false, | 145 | "private": false, | ||
146 | "relationships_as_object": [], | 146 | "relationships_as_object": [], | ||
147 | "relationships_as_subject": [], | 147 | "relationships_as_subject": [], | ||
148 | "resources": [ | 148 | "resources": [ | ||
149 | { | 149 | { | ||
150 | "cache_last_updated": null, | 150 | "cache_last_updated": null, | ||
151 | "cache_url": null, | 151 | "cache_url": null, | ||
152 | "created": "2020-10-14T01:33:26.021842", | 152 | "created": "2020-10-14T01:33:26.021842", | ||
153 | "datastore_active": false, | 153 | "datastore_active": false, | ||
154 | "description": "", | 154 | "description": "", | ||
155 | "format": "", | 155 | "format": "", | ||
156 | "hash": "", | 156 | "hash": "", | ||
157 | "id": "fdac877d-7652-4057-ad70-c397df384e5b", | 157 | "id": "fdac877d-7652-4057-ad70-c397df384e5b", | ||
158 | "last_modified": null, | 158 | "last_modified": null, | ||
159 | "metadata_modified": "2020-10-14T01:33:26.021842", | 159 | "metadata_modified": "2020-10-14T01:33:26.021842", | ||
160 | "mimetype": null, | 160 | "mimetype": null, | ||
161 | "mimetype_inner": null, | 161 | "mimetype_inner": null, | ||
162 | "name": "Geospatial Support Data Access", | 162 | "name": "Geospatial Support Data Access", | ||
163 | "package_id": "28b027b7-1328-40d3-8d62-8b6e26aadb9f", | 163 | "package_id": "28b027b7-1328-40d3-8d62-8b6e26aadb9f", | ||
164 | "position": 0, | 164 | "position": 0, | ||
165 | "resource_type": null, | 165 | "resource_type": null, | ||
166 | "size": null, | 166 | "size": null, | ||
167 | "state": "active", | 167 | "state": "active", | ||
168 | "url": "https://www.pgc.umn.edu/data/", | 168 | "url": "https://www.pgc.umn.edu/data/", | ||
169 | "url_type": null | 169 | "url_type": null | ||
170 | } | 170 | } | ||
171 | ], | 171 | ], | ||
172 | "state": "active", | 172 | "state": "active", | ||
173 | "tags": [], | 173 | "tags": [], | ||
174 | "title": "Polar Geospatial Center(PGC)", | 174 | "title": "Polar Geospatial Center(PGC)", | ||
175 | "type": "dataset", | 175 | "type": "dataset", | ||
176 | "url": "https://www.pgc.umn.edu/data", | 176 | "url": "https://www.pgc.umn.edu/data", | ||
177 | "version": "" | 177 | "version": "" | ||
178 | } | 178 | } |