Database Format Sample Clauses

Database Format. The following table details the data format requirements for the RCL database. Table 2-1. RCL Database Format FIELD NAME M/C/O TYPE WIDTH DESCRIPTION/ VALID ENTRIES SOURCE M TEXT 75 Agency that last updated the record, i.e. XXXXXXX, XXXXXX PROVIDER M TEXT 75 The name of the regional 911 authority CAPCOG will populate LAST_MOD M DATE 26 Date of last update using ISO 8601 format EFF_DATE O DATE 26 Date the new record information goes into effect in ISO 8601 format SEGMENTID O LONG DEFAULT Unique segment ID CAPCOG will populate prior to uploading to PSAP. May also serve as a placeholder field to populate SITEUNGID field RCL_UNIQID M TEXT 100 Globally Unique ID for each road segment. Ex. 000XXX@xx.xxxxxx.xx.xx COUNTRY M TEXT 2 Country name represented by two capital letters L_STATE M TEXT 2 Left state name by two letters defined by USPS publication 28 R_STATE M TEXT 2 Right state name by two letters defined by USPS publication 28 L_COUNTY M TEXT 40 Fully spelled county name on the left side of the road R_COUNTY M TEXT 40 Fully spelled county name on the right side of the road L_MUNI M TEXT 100 Name of municipality on Left, if none populate with “UNINCORPORATED” R_MUNI M TEXT 100 Name of municipality on Right, if none populate with “UNINCORPORATED” L_MUNI_DIV C TEXT 100 Name of municipality division on Left, i.e. ”XXXX 5 FRIENDSHIP DISTRICT” FIELD NAME M/C/O TYPE WIDTH DESCRIPTION/ VALID ENTRIES R_MUNI_DIV C TEXT 100 Name of municipality division on Right i.e. “XXXX 5 FRIENDSHIP DISTRICT” L_NBRHOOD O TEXT 100 Name of neighborhood or subdivision on Left R_NBRHOOD O TEXT 100 Name of neighborhood or subdivision on Right L_RNG_PRE C TEXT 15 Part of an address preceding the numeric address on Left R_RNG_PRE C TEXT 15 Part of an address preceding the numeric address on Right LF_ADDR M LONG DEFAULT Left address number at the FROM node LT_ADDR M LONG DEFAULT Left address number at the TO node RF_ADDR M LONG DEFAULT Right address number at the FROM node RT_ADDR M LONG DEFAULT Right address number at the TO node L_PARITY M TEXT 1 E, O, B, Z for Even, Odd, Both, or Zero (if the range is 0 to 0) R_PARITY M TEXT 1 E, O, B, Z for Even, Odd, Both, or Zero (if the range is 0 to 0) L_POST_COM C TEXT 40 City name for the ZIP of an address, as given in the USPS on Left R_POST_COM C TEXT 40 City name for the ZIP of an address, as given in the USPS on Right L_ZIP C TEXT 5 5-digit numeric postal code area on Left R_ZIP C TEXT 5 5-digit numeric postal code area on Right L_ESN M TEXT ...
Sample 1
AutoNDA by SimpleDocs
Database Format. The following table details the data format requirements for the SSAP database. Table 3-1. SSAP Database Format FIELD NAME M/C/O TYPE WIDTH DESCRIPTION/ VALID ENTRIES SOURCE M TEXT 75 Agency that last updated the record, i.e. HAYS, XXXXXXXXXX PROVIDER M TEXT 75 The name of the regional 911 authority CAPCOG will populate LAST_MOD M DATE 26 Date of last update using ISO 8601 format EFF_DATE O DATE 26 Date the new record information goes into effect in ISO 8601 format SITE_ID O LONG DEFAULT Unique site ID CAPCOG will populate prior to uploading to PSAP. May also serve as a placeholder field to populate SITEUNGID field SITEUNQID M TEXT 100 Globally unique ID for each address site or structure. Ex. 0000XX@xx.xxx.xx.us COUNTRY M TEXT 2 Country name represented by two capital letters STATE M TEXT 2 State name by two letters defined by USPS publication 28 COUNTY M TEXT 40 County name or equivalent fully spelled out MUNICIPAL M TEXT 100 Name of municipality, if none populate with “UNINCORPORATED”
Sample 1
Database Format. The following table details the data format requirements for the ESB database. Table 5-1. ESB Database Format FIELD NAME M/C/O TYPE WIDTH DESCRIPTION/ VALID ENTRIES DISCRPAGID M TEXT 75 Agency that last updated the record, i.e. BASTROP, BURNET DATEUPDATE M DATE 26 Date of last update using ISO 8601 format EXPIRE O TEXT 26 Unique tandem routing code CAPCOG will populate EFFECTIVE O TEXT 26 The date and time when the information in the record is no longer considered valid. ES_NGUID M TEXT 254 Globally unique ID for each emergency service boundary polygon – Ex. 000XXX@xxxxxx.xx.xx.xx STATE M TEXT 2 State name by two letters defined by USPS publication 28 AGENCYID M TEXT 100 A Domain Name System (DNS) domain name which is used to uniquely identify an agency. Ex. xxxxxxxxxxx.xxx SERVICEURI M TEXT 254 URN/URL for routing. Example: sip:xxx@xxxxxxxx0.xxxxxx.tx.us SERVICEURN M TEXT 50 The URN for the Emergency Service or other Well- Known Service* SERVICENUM M TEXT 15 The numbers that would be dialed on a 12-digit keypad to reach the emergency service appropriate for the location. Ex: 911 AVCARDURI C TEXT 254 URI for the vCARD of contact information DISPLAYNAME M TEXT 60 Name of the service provider that offers services within the area of an Emergency Service Boundary
Sample 1
Database Format. The following table details the data format requirements for the Municipal Boundary database. Table 6-1. Municipal Boundary Database Format FIELD NAME M/C/O TYPE WIDTH DESCRIPTION/ VALID ENTRIES SOURCE M TEXT 75 Agency that last updated the record, i.e. XXXXXXXX, LLANO PROVIDER M TEXT 75 The name of the regional 911 authority CAPCOG will populate LAST_MOD M DATE 26 Date of last update using ISO 8601 format EFF_DATE O DATE 26 Date the new record information goes into effect in ISO 8601format POLY_ID O LONG DEFAULT Numeric Polygon ID CAPCOG will populate prior to uploading to PSAP. May also serve as a placeholder field to populate MUNIUNQID field MUNIUNQID M TEXT 100 Globally Unique ID for each municipality - . Ex. 0000XXXX@xxxxxxxxxxx.xxx COUNTRY M TEXT 2 Country name represented by two capital letters STATE M TEXT 2 State Name (eg: TX) COUNTY M TEXT 40 County name fully spelled out MUNI_NM M TEXT 100 Name of municipality i.e. “AUSTIN”
Sample 1
Database Format. The following fields in the ALI database are used by the Data Hub and EGDMS quality control systems to match the address point and road centerline feature classes to ensure a call routes and plots correctly.
Sample 1

Related to Database Format

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

  • Contract Database Metadata Elements Title: Whitesville Central School District and Whitesville Central School Educational Support Staff Association (2003) Employer Name: Whitesville Central School District Union: Whitesville Central School Educational Support Staff Association Local: Effective Date: 07/01/2003 Expiration Date: 06/30/2006 PERB ID Number: 10699 Unit Size: Number of Pages: 23 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT BETWEEN WHITESVILLE CENTRAL SCHOOL EDUCATIONAL SUPPORT STAFF ASSOCIATION AND THE WHITESVILLE CENTRAL SCHOOL DISTRICT JULY 1, 2003 THROUGH JUNE 30, 2006 TABLE OF CONTENTS ARTICLE TITLE PAGE Preamble 1 I Recognition 1 II Collective Bargaining U n i t 1 III Dues/Agency Fee Ckoffand Payroll Deduction 1 IV Rights of Employees 2 V Rights of Employer ------------- 2 VI Personnel F i l e 2 VII Employee Definitions 3 VIII Permanent Status/Seniority 4 IX Wages 5 X Overtime 7 XI Vacation 7 XII Holidays 8 XIII Sick Leave and Leavesof A b s e n c e 8 XIV Conference, Workshops,Required Courses 10 XV Meal Allowance and M i l e a g e 11 XVI Retirement 11 XVII Insurance 12 XVIII Cafeteria P l a n 14 .XIX Uniform Allowance------------------ 14 XX Hours of W o r k 14 XXI Transfers/Promotions 15 XXII Job Descriptions 15 XXIII Grievance Procedure 15 XIV Copies of the Contract 18 XV Zipper C x x x x x 18 XXVI Legislative Clause 18 XXVII Duration 19 SIGNATURES 19 APPENDIX A Grievance F o r m 20 APPENDIX B Dues Authorization F o r m 21

  • Web Hosting If Customer submits a Service Order(s) for web hosting services, the following terms shall also apply:

  • Software Title and ownership to Existing Software Product(s) delivered by Contractor under the Contract that is normally commercially distributed on a license basis by the Contractor or other independent software vendor proprietary owner (“Existing Licensed Product”), embedded in the Custom Products, shall remain with Contractor or the proprietary owner of other independent software vendor(s) (ISV). Effective upon acceptance, such Product shall be licensed to Authorized User in accordance with the Contractor or ISV owner’s standard license agreement, provided, however, that such standard license, must, at a minimum: (a) grant Authorized User a non-exclusive, perpetual license to use, execute, reproduce, display, perform, adapt (unless Contractor advises Authorized User as part of Contractor’s proposal that adaptation will violate existing agreements or statutes and Contractor demonstrates such to the Authorized User’s satisfaction) and distribute Existing Licensed Product to the Authorized User up to the license capacity stated in the Purchase Order or work order with all license rights necessary to fully effect the general business purpose(s) stated in the Bid or Authorized User’s Purchase Order or work order, including the financing assignment rights set forth in paragraph (c) below; and (b) recognize the State of New York as the licensee where the Authorized User is a state agency, department, board, commission, office or institution. Where these rights are not otherwise covered by the ISV’s owner’s standard license agreement, the Contractor shall be responsible for obtaining these rights at its sole cost and expense. The Authorized User shall reproduce all copyright notices and any other legend of ownership on any copies authorized under this clause. Open source software is developed independently of Contractor and may be governed by a separate license (“open source software”). If the open source software is governed by a separate License and provided under this Contract, Contractor shall provide a copy of that license in the applicable Documentation and the Authorized User's license rights and obligations with respect to that open source software shall be defined by those separate license terms and subject to the conditions, if any, therein. Nothing in this Contract shall restrict, limit, or otherwise affect any rights or obligations the Authorized User may have, or conditions to which the Authorized User may be subject, under such separate open source license terms.

  • Codebook Format The codebook describes an ASCII data set (although the data are also being provided in a SAS transport file). The following codebook items are provided for each variable: Identifier Description Name Variable name (maximum of 8 characters) Description Variable descriptor (maximum 40 characters) Format Number of bytes Type Type of data: numeric (indicated by NUM) or character (indicated by XXXX) Start Beginning column position of variable in record End Ending column position of variable in record

  • Templates The Applicant shall use Templates provided by Alberta Innovates to comply with its Required Reporting Metrics, Reports obligations, and with the Survey requirements. Because the Reports may contain technical or proprietary information about the Project or the Applicant, the Templates will specify when a section will be considered non-confidential. The content of sections that are marked as non-confidential can be disclosed in the public domain. All other sections will be considered confidential, and thus can only be disclosed to the Government of Alberta and to Funding Partners, if any, in confidence, but to no other party.

  • Images If applicable, the CONSULTANT is prohibited from capturing on any visual medium images of any property, logo, student, or employee of the DISTRICT, or any image that represents the DISTRICT without express written consent from the DISTRICT.

  • Formats Formats for records must be satisfactory to FTA and include, but are not limited to, electronic records, including any emails related to the Award, records on paper, and records created in other formats.

  • Metadata Bibliographical, structural & descriptive data of the Licensed Material as defined in Schedule 5.

  • Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.

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