Database Format Sample Clauses

Database Format. The following table details the data format requirements for the SSAP database. DiscrpAgID Discrepancy Agency ID YES TEXT 100 MIXED Agency that last updated the record. Valid values are: Bastrop, Blanco, Xxxxxx, Xxxxxxxx, Fayette, Xxxx, Xxx, Xxxxx, Xxxxxx, Xxxxxxxxxx DateUpdate Date Updated YES DATE N/A N/A Date of last update using ISO 8601 format Effective Effective Date NO DATE N/A N/A Date the new record information goes into effect in ISO 8601 format NGUID NENA Globally Unique ID YES TEXT 254 MIXED Globally Unique ID for each road segment. Ex. urn:emergency:uid:gis:SSAP:{AD873541- F41C-409E-A0BE- 1B0C583902A4}:xxxxx.xxx Country Country YES TEXT 2 UPPER The value must be: US State State YES TEXT 2 UPPER The value must be: TX County County YES TEXT 100 MIXED Fully spelled county name. Valid values are: Bastrop, Blanco, Xxxxxx, Xxxxxxxx, Fayette, Xxxx, Xxx, Xxxxx, Xxxxxx, Xxxxxxxxxx AddCode Additional Xxxx CONDITIONAL TEXT 6 N/A A code that specifies a geographic area AddDataURI Additional Data URI CONDITIONAL TEXT 254 N/A URI for additional data associated with the address point Inc_Muni Incorporated Municipality YES TEXT 100 MIXED Name of municipality, if none populate with “Unincorporated” Uninc_Comm Unincorporated Community NO TEXT 100 MIXED The unincorporated community, either within an incorporated municipality or in a unincorporated portion of a county, or both Nbrhd_Comm Neighborhood Community NO TEXT 100 MIXED Name of neighborhood or subdivision where the address is located AddNum_Pre Address Number Prefix CONDITIONAL TEXT 15 N/A Part of an address leading the numeric address Add_Number Address Number YES LONG N/A N/A Numeric identifier of a location along a thoroughfare AddNum_Suf Address Number Suffix CONDITIONAL TEXT 15 N/A Part of an address following the address number, e.g., ½, B St_PreMod Street Name Pre Modifier CONDITIONAL TEXT 15 MIXED Word or phrase separate from type and direction that precedes St_Pre_Dir, e.g., Access, Alternate, Business, Connector, Extension, Scenic, Spur, Ramp Underpass, Overpass St_PreDir Street Name Pre Directional CONDITIONAL TEXT 10 MIXED Leading directional prefix. Valid values are:North, South, East, West, Northwest, Northeast, Southwest, Southeast. MUST be fully spelled out.
Sample 1Sample 2
AutoNDA by SimpleDocs
Database Format. The following table details the data format requirements for the ESB database. DiscrpAgID Discrepancy Agency ID YES TEXT 100 MIXED Agency that last updated the record. Valid values are: Bastrop, Blanco, Xxxxxx, Xxxxxxxx, Fayette, Xxxx, Xxx, Xxxxx, Xxxxxx, Xxxxxxxxxx DateUpdate Date Updated YES DATE 26 N/A Date of last update using ISO 8601 format Expire Expiration Date EMPTY TEXT 26 N/A Unique tandem routing code CAPCOG will populate Effective Effective Date NO TEXT 26 N/A The date and time when the information in the record is no longer considered valid. NGUID NENA Globally Unique ID YES TEXT 254 N/A Globally Unique ID for each road segment. Ex. urn:emergency:uid:gis:[xxx]:{AD873541-F41C- 409E-A0BE-1B0C583902A4}:xxxxx.xxx [xxx] must be replaced with Pol, Fire, or Ems for the corresponding Feature Layer. State State YES TEXT 2 UPPER The value must be: TX Agency_ID Agency Identifier YES TEXT 100 MIXED A Domain Name System (DNS) domain name which is used to uniquely identify an agency. Ex. xxxxxxxxxxx.xxx ServiceURI Service URI YES TEXT 254 N/A URN/URL for routing. Example: sip:xxx@xxxxxxxx0.xxxxxx.tx.us ServiceURN Service URN YES TEXT 50 N/A The URN for the Emergency Service or other Well-Known Service* ServiceNum Service Number YES TEXT 15 N/A The numbers that would be dialed on a 12-digit keypad to reach the emergency service appropriate for the location. Ex: 911 AVcard_URI AV Card URI CONDITIONAL TEXT 254 MIXED URI for the vCARD of contact information DsplayName Dsiplay Name YES TEXT 60 UPPER Name of the service provider that offers services within the area of an Emergency Service Boundary This dataset represents municipal boundaries in the CAPCOG region.
Sample 1Sample 2
Database Format. The following table details the data format requirements for the RCL database. DiscrpAgID Discrepancy Agency ID YES TEXT 100 MIXED Agency that last updated the record. Valid values are: Bastrop, Blanco, Xxxxxx, Xxxxxxxx, Fayette, Xxxx, Xxx, Xxxxx, Xxxxxx, Xxxxxxxxxx DateUpdate Date Updated YES DATE N/A N/A Date of last update using ISO 8601 format Effective Effective Date NO DATE N/A N/A Date the new record information goes into effect in ISO 8601 format NGUID NENA Globally Unique ID YES TEXT 254 MIXED Globally Unique ID for each road segment. Ex. urn:emergency:uid:gis:RCL:{AD873541-F41C- 409E-A0BE-1B0C583902A4}:xxxxx.xxx AdNumPre_L Left Address Number Prefix CONDITIONAL TEXT 15 MIXED Part of an address preceding the numeric address on Left AdNumPre_R Right Address Number Prefix CONDITIONAL TEXT 15 MIXED Part of an address preceding the numeric address on Right COUNTRY Country YES TEXT 2 UPPER The value must be: US FromAddr_L Left FROM Address YES LONG N/A N/A Left address number at the FROM node ToAddr_L Left TO Address YES LONG N/A N/A Left address number at the TO node FromAddr_R Right FROM Address YES LONG N/A N/A Right address number at the FROM node ToAddr_R Right TO Address YES LONG N/A N/A Right address number at the TO node Parity_L Parity Left YES TEXT 1 MIXED Valid values are: E = Even, O = Odd, B = Both, Z = Zero (if the range is 0 to 0) Parity_R Parity Right YES TEXT 1 MIXED Valid values are: E = Even, O = Odd, B = Both, Z = Zero (if the range is 0 to 0) St_PreMod Street Name Pre Modifier CONDITIONAL TEXT 15 MIXED Word or phrase separate from type and direction that precedes St_PreDirI e.g., Access, Alternate, Business, Connector, Extension, Scenic, Spur, Ramp Underpass, Overpass St_PreDir Street Name Pre Directional CONDITIONAL TEXT 10 MIXED Spelled out leading directional prefix. Valid values are: North, South, East, West, Northwest, Northeast, Southwest, Southeast. St_PreTyp Street Name Pre Type CONDITIONAL TEXT 50 MIXED Spelled out word or phrase that precedes and identifies a type of thoroughfare. Must be fully spelled out, e.g., “Farm to Market Road” instead of “FM”. Restricted values found in NENA Registry of Street Name Pre Types and Street Name Post Types (see the Reference Documents section at the end of this document). St_PreSep Street Name Pre Type Separator CONDITIONAL TEXT 20 MIXED A preposition or prepositional phrase between St_PreTyp and St_Name, e.g., “of the” in “Avenue of the Stars”. Restricted to values found in NENA Regis...
Sample 1Sample 2
Database Format. The following table details the data format requirements for the ESZ database. SOURCE Source YES TEXT 75 UPPER Agency that last updated the record. Valid values are: BASTROP, BLANCO, XXXXXX, XXXXXXXX, XXXXXXX, XXXX, XXX, XXXXX, XXXXXX, XXXXXXXXXX. PROVIDER Provider EMPTY TEXT 75 UPPER The name of the regional 911 authority CAPCOG will populate LAST_MOD Last Modification YES DATE N/A UPPER Date of last update using ISO 8601 format EFF_DATE Effective Date No DATE N/A UPPER Date the new record information goes into effect in ISO 8601 format ES_UNQID Emergency Service Unique ID EMPTY TEXT 100 UPPER ID for each emergency service polygon - CAPCOG will populate POLICE Police YES TEXT 60 UPPER Name of police service provider FIRE Fire YES TEXT 60 UPPER Name of fire service provider MEDICAL Medical YES TEXT 60 UPPER Name of medical service provider COUNTRY Country YES TEXT 2 UPPER The value must be: US STATE State YES TEXT 2 UPPER The value must be: TX COUNTY County YES TEXT 40 UPPER County name fully spelled out. Valid values are: BASTROP, BLANCO, XXXXXX, XXXXXXXX, XXXXXXX, XXXX, XXX, XXXXX, XXXXXX, XXXXXXXXXX. URI URI YES TEXT 254 UPPER URN/URL for routing. Example: sip:xxx@xxxxxxxx0.xxxxxx.tx.us URN URN NO TEXT 50 UPPER The URN for the Emergency Service or other Well-Known Service (Example: “urn:service:sos” for a PSAP or “urn:service:sos.ambulance” for an ambulance service ) ESN ESN YES TEXT 5 UPPER ESN of the responding agency preceded by ‘0’ if number of digits are fewer than 5. TANDEM Tandem YES TEXT 3 UPPER 911 Selected Router Code TANDEM2 Tandem 2 CONDITIONAL TEXT 3 UPPER 911 Selected Router Code ESSID ESSID EMPTY TEXT 2 UPPER Unique tandem routing code CAPCOG will populate ESNGUID ESN GUID EMPTY TEXT 8 UPPER Concatenation of ESN and ESSID separated by a single backslash “/” CAPCOG will concatenate AVCARDURI AV Card ID CONDITIONAL TEXT 254 UPPER URI for the vCARD of contact information This dataset consists of Emergency Service Boundary layers that define the geographic area for the primary providers of response services in the CAPCOG region.
Sample 1Sample 2
Database Format. The following table details the data format requirements for the Municipal Boundary database. DiscrpAgID Discrepancy Agency ID YES TEXT 100 MIXED Agency that last updated the record. Valid values are: Bastrop, Blanco, Xxxxxx, Xxxxxxxx, Fayette, Xxxx, Xxx, Xxxxx, Xxxxxx, Xxxxxxxxxx. DateUpdate Date Updated YES DATE N/A N/A Date of last update using ISO 8601 format Effective Effective Date NO DATE N/A N/A Date the new record information goes into effect in ISO 8601 format NGUID NENA Globally Unique ID YES TEXT 254 MIXED Globally Unique ID for each road segment. Ex. urn:emergency:uid:gis:A3:{AD873541-F41C-409E- A0BE-1B0C583902A4}:xxxxx.xxx Country Country YES TEXT 2 UPPER The value must be: US State State YES TEXT 2 UPPER The value must be: TX County County YES TEXT 40 MIXED County name fully spelled out. Valid values are: Bastrop, Blanco, Xxxxxx, Xxxxxxxx, Fayette, Xxxx, Xxx, Xxxxx, Xxxxxx, Xxxxxxxxxx AddCode Additional Code NO TEXT 6 N/A A code that specifies a geographic area Inc_Muni Incorporated Municipality (A3) YES TEXT 100 MIXED Name of municipality e.g., “Austin”
Sample 1Sample 2
Database Format. The following table details the data format requirements for the SSAP database. 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. 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
AutoNDA by SimpleDocs
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. Table 7-1. ALI Database Format
Sample 1

Related to Database Format

  • Database File The Servicer will provide the Successor Servicer with a magnetic tape (in a format reasonably acceptable to the Indenture Trustee and the Servicer) containing the database file for each Contract (i) as of the Initial Cutoff Date, (ii) the Subsequent Cutoff Date, (iii) thereafter, as of the last day of the preceding Due Period on each Determination Date prior to a Service Transfer and (iv) on and as of the Business Day before the actual commencement of servicing functions by the Successor Servicer following the occurrence of a Service Transfer.

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

  • Contract Database Metadata Elements Title: Great Neck Union Free School District and Great Neck Paraprofessionals Association (2011) Employer Name: Great Neck Union Free School District Union: Great Neck Paraprofessionals Association Local: Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 5132 Unit Size: Number of Pages: 28 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/ ARTICLE# TITLE PAGE# Preamble 2 Article 1 Association Rights 2 Article 2 Board-Administration-Association Relationship and Procedures 4 Article 3 Exchange of Proposals 6 Article 4 Professionals Duties and Responsibilities of Paraprofessionals 7 Article 5 Work Assignments 8 Article 6 Annual Appointment 10 Article 7 Selection and Promotion 10 Article 8 Evaluations and Standards 11 Article 9 Procedures for Termination of Employment 11 Article 10 Conferences 12 Article 11 Human Resource File 12 Article 12 Professional Growth 13 Article 13 Sick Leave 14 Article 14 Personal Leave 16 Article 15 Other Leaves 17 Article 16 Grievance Procedures 18 Article 17 Legal Assistance 19 Article 18 Conformity to Law 19 Article 19 Health Insurance 20 Article 20 Retirement Plan 20 Article 21 Salary Schedule 21 Article 22 Seniority Policy 23 Article 23 Compensation for Financial Loss 24 Article 24 Duration of Agreement 25 Appendix A Determination of Negotiating Unit 25 Appendix B Payroll Deduction Authorization 26 Appendix C Bus Aides 26 Appendix D Salary Schedules 27

  • Software Inclusions Restrictions

  • Metadata Where the Contractor has or generates metadata as a result of services provided to the Province, where that metadata is personal information, the Contractor will: not use it or disclose it to any other party except where the Agreement otherwise specifies; and remove or destroy individual identifiers, if practicable.

  • 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.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Computer The Contractor shall maintain at its office for its use a computer with, at a minimum, a 1 GHz processor and an internet connection. The Contractor shall maintain individual email accounts for each of its project managers.

  • Web Site Information on registration for and use of the E-Verify program can be obtained via the Internet at the Department of Homeland Security Web site: xxxx://xxx.xxx.xxx/E-Verify.

  • Firmware 7.1 The Supplier must deliver the equipment, Goods or hardware equipped with all the firmware required to use all the Goods or hardware’s functions. Any software embedded in the equipment, Goods or hardware, including the firmware, is provided to the Local Government with a license to use this software, with all license costs and royalties being included in the Fee Schedule (Schedule C). All firmware will be the most recent version available at the time of shipping.

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