Geographic Data Documentation (Metadata) Sample Clauses

Geographic Data Documentation (Metadata). For each digital file delivered containing geographic information (regardless of format), the Contractor shall provide documentation consistent with the GEOFidelis Metadata Guidelines, which follow Federal Geographic Data Committee (FGDC) Content Standards for Digital Geospatial Metadata (CSDGM). Both ‘Mandatory’ and ‘Mandatory as Applicable’ fields shall be completed for each geographic data set, as well as selected ‘Optional’ fields. The documentation shall include, but not be limited to, the following: - The name, description, abstract, and purpose of the data set/data layer. - The source of the data and any related data quality information such as accuracy and time period of content. - Descriptions of the receiver and other equipment used during collection and processing, base stations used for differential corrections, software used for performing differential corrections, estimated horizontal and vertical accuracies obtained, and conversion routines used to translate the data into final geographic data delivery format. - Details of all checks made to existing control points & any discrepancies noted. - Type of data layer (point, line, polygon, etc.). - Field names of all attribute data and a description of each field name. - Definition of all codes used in the data fields. - Ranges of numeric fields and the meaning of these numeric ranges. - The creation date of the map layer and the name of the person who created it. - A point of contact shall be provided to answer technical questions. Metadata generation tools included in the ArcGIS suite of software (or equivalent technology) shall be used in the production of the required metadata in XML format. Regardless of the tools used for metadata creation, the Contractor must insure that the metadata is delivered in XML format and can be easily imported to the Installation’s enterprise geodatabase. Specific guidelines may be found within the GEOFidelis West Metadata Authoring Guide. A copy of the guide may be obtained by contacting: GEOFidelis West Building 0000, Xxxxx Xxxxx Xxxx 0 Xxxx Xxxxxxxxx, CA 92055 (760) 763-1891 NOTE: The metadata Point of Contact should be the Contractor’s Project Manager. The Contractor shall use language and format consistent with existing Installation metadata.)
Sample 1
AutoNDA by SimpleDocs

Related to Geographic Data Documentation (Metadata)

  • Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet

  • Product Documentation You should review the policy documents carefully to ensure they accurately reflect the cover, conditions, limits, and other terms that you require. Particular attention should be paid to policy conditions and warranties as failure to comply with these could invalidate your policy. It is important that you retain and keep safely all documents associated with your policy so that you can refer to them in the event of a claim.

  • Service Documentation The “Service Documentation” includes;

  • Source Documentation Accounting records must be supported by such source documentation as canceled checks, bank statements, invoices, paid bills, donor letters, time and attendance records, activity reports, travel reports, contractual and consultant agreements, and subaward documentation. All supporting documentation should be clearly identified with the Award and general ledger accounts which are to be charged or credited.

  • Statistical Sampling Documentation a. A copy of the printout of the random numbers generated by the “Random Numbers” function of the statistical sampling software used by the IRO.

  • Information Services Traffic 5.1 For purposes of this Section 5, Voice Information Services and Voice Information Services Traffic refer to switched voice traffic, delivered to information service providers who offer recorded voice announcement information or open vocal discussion programs to the general public. Voice Information Services Traffic does not include any form of Internet Traffic. Voice Information Services Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information services Traffic is not subject to Reciprocal Compensation as Local Traffic under the Interconnection Attachment.

  • Documentation License Subject to the terms of this Agreement, Flock hereby grants to Customer a non-exclusive, non-transferable right and license to use the Documentation during the Service Term for Customer’s internal purposes in connection with its use of the Flock Services as contemplated herein.

  • Technical Documentation Prior to commencement of the Tests on Completion, the Contractor shall supply to the Engineer the technical documentation as specified in the Employer’s Requirements. The Works or Section shall not be considered to be completed for the purposes of taking- over under sub-clause 10.1 [Taking Over of the Works and Sections] until the Engineer has received the technical documentation as defined in this sub-clause 5.7, the "history file" including design calculations and certain certification as well as any other documents required to meet the CE Marking requirements.

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Software and Documentation Licensee may make as many copies of the Software necessary for it to use the Software as licensed. Each copy of the Software made by Licensee must contain the same copyright and other notices that appear on the original copy. Licensee will not modify the Documentation. Documentation may: (a) only be used to support Licensee’s use of the Software; (b) not be republished or redistributed to any unauthorized third party; and (c) not be distributed or used to conduct training for which Licensee, or any other party, receives a fee. Licensee will not copy any system schema reference document related to the Software.

Time is Money Join Law Insider Premium to draft better contracts faster.