Specification for Geodata Sample Clauses

Specification for Geodata. This section is about Geospatial data (in short: geodata) and how they are represented in DIP format. Geodata is a combination of the graphical representation of objects in space and their descriptions or attributes. Additionally, geospatial formats include geospatially focused datasets or databases that contain primary information about a geographic location. Furthermore, ancillary and supplementary data – that can be either included or derived using spatial analysis – are considered necessary for rendering, interpretation and re-use of the data. The basis of geodata is generally either vector or raster graphics data which can be stored as a set of files or as a database (if the database supports spatial data types). Vector data represents spatial objects as points, lines or polygons, or a complex combination of them. Descriptive or derived attributes can be stored along with the spatial data in tables (one row per spatial object) or as a separate table. Raster data represents spatial objects as cells in a grid. Those cells can contain different types of values from binary to decimal numbers. Raster data is often split into a number of images covering a larger area. Some geodata is structured in a form that it is self-explanatory. In other cases, especially if geodata was a part of a greater system, we need additional information to properly render it in the way it was used in the original system. For proper interpretation of geodata we also need some other elements that put the coordinates and attribute tables into context. The main additional elements are: Spatial referencing information (Coordinate system); geoprocessing information; and visualization.
AutoNDA by SimpleDocs

Related to Specification for Geodata

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • Product Specifications The Company agrees that all Products sold to Xxxx hereunder shall conform to the respective specifications set forth on Schedule A or to such other specifications as are from time to time agreed upon by the Parties.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Health plan specification The Employer will require health plans participating in the Group Insurance Program to develop and implement health promotion and health education programs for State employees and their dependents.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Specifications That part of the Contract Documents consisting of written requirements for materials, equipment, systems, standards, and workmanship as applied to the Work, and certain administrative requirements and procedural matters applicable thereto. The term "Specifications" shall also include all written matter in the Project Manual or on the drawings and any Addenda or Change Orders thereto.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!