Graphic (Spatial) Edits Sample Clauses

Graphic (Spatial) Edits. Each named street needs to be represented in the GIS graphically and include attribution for all database fields listed below. All unnamed streets included in the street centerline layer are required to have the designation “DRVW” entered in the ‘street name (ST_NAME)’ field and have any other relevant attribute information completed, including the ‘CLASS’ field. When a street centerline is created or edited, several sources and methods can be used, including current aerial imagery, georeferenced survey plats, computer-aided design (CAD) files, parcels, mapping-grade GPS units in the field, or other authoritative sources or methods. The positional accuracy of addressed structures should be within +/- 5 feet of the center of the roadbed (the part on which vehicles travel) noting that when roadways are divided (i.e by a median) the roadbeds on each side should have a centerline drawn. In all cases each new street centerline will need to be split, or checked for gaps, at each jurisdiction and ESN line/boundary intersection. Street segment direction must be correct as well. These items and other geometric relationships are referred to as “topology”, and especially important for NG9-1-1 purposes.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Graphic (Spatial) Edits. All addressed site/structures must be represented in the address point layer. When a site/structure point is created or edited, several sources and methods can be used, including aerial imagery, georeferenced survey plats, computer-aided design (CAD) files, parcels, mapping-grade GPS units in the field, or other authoritative sources and methods. When the actual structure location is known, the symbol should represent the general center of the structure. In other cases, please refer to the “NENA Information Document for Development of Site/Structure Address Point GIS Data for 9-1-1” document. In any case, the positional accuracy of structures or designated site locations should be within +/- 25 feet of their true location or intended designation.
Sample 1Sample 2Sample 3See All (4)
Graphic (Spatial) Edits. These areas need to accurately reflect the boundaries of each geographically unique combination of fire, law and EMS responder zones. This layer is created and maintained by overlaying with some combination of street centerlines, municipal (i.e. city limit) boundaries, parcels boundaries, or other data to determine each jurisdiction’s emergency response service areas. As new emergency response services are added to, or change in an area, this boundary file will need to be modified accordingly. Communications must be regularly preserved with all fire, law, and emergency medical responders to obtain the information required to maintain updated ESZ boundaries. These ESZ boundaries should be within +/- 50 feet of their true location with no gaps or overlaps. These items and other geometric relationships are referred to as “topology”, and especially important for NG9-1-1 purposes. In addition, it is very important that all features with identical attribute information are merged into one multipart polygon.
Sample 1Sample 2Sample 3See All (4)
Graphic (Spatial) Edits. When city limits change due to annexations, metes and bounds surveys or other related information must be acquired to update the city limit boundaries. Coordinate geometry (COGO) – is one of the preferred methods for calculating coordinate points from surveys and can be used to update the city limit boundaries in the GIS within + or – 50 feet of their true location with no gaps or overlaps 5.2 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 8601 format POLY_ID M LONG DEFAULT Numeric Polygon ID CAPCOG will populate MUNIUNQID M TEXT 100 Unique ID for each municipality - CAPCOG will populate 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” Attachment B, Part 2: Guidance Document for CAPCOG Next Generation 9-1-1-GIS Data (Version 2, 2020) Guidance Document for CAPCOG Next-Generation 9-1-1 Geographic Information System (GIS) Data Version 2: April 2020 Introduction: As the Transition Workflow Cycle of the Next-Generation 9-1-1 Database Program Interlocal Agreement (XXX) describes, our region is moving closer and closer to deploying a Next-Gen 9-1-1 system that enables emergency calls to route to the correct PSAP based on GIS data. This transition begins the process of moving away from our traditional MSAG-based (tabular database) routing system to one that will be faster, more reliable, and enable multimedia such as pictures and videos to be sent to 9-1-1 call takers. However, in order to move to this new system, several changes need to be made to our workflows and data. Perhaps the biggest change is that we will be utilizing new cloud-based software packages to assist with quality-control (QC). One of these solutions will also ultimately become the mechanism by which 9-1-1 GIS data is supplied to PSAPs, which could ultimately be done at any time throughout the month as opposed to just once. The intention of this document is to serve as a guide for county coordinators in the preparation of this transition, and to provide detailed technical information regarding how to prepare the 9-1-1 GIS data submission....
Sample 1Sample 2
Graphic (Spatial) Edits. All addressed site/structures must be represented in the address point layer. When a site/structure point is created or edited, several sources and methods can be used, including aerial imagery, georeferencedsurvey plats, computer-aided design (CAD) files, parcels, mapping-grade GPS units in the field, or otherauthoritative sources and methods. When the actual structure location is known, the symbol should represent the general center of the structure. In other cases, please refer to the “NENA Information Document for Development of Site/Structure Address Point GIS Data for 9-1-1” document. In any case, the positional accuracy of structures or designated site locations should be within +/- 25 feet of their truelocation or intended designation. The performance standard for the Site Structure Address Point feature class is 98% accuracy. This means that 98% of the database records should be free of critical and significant errors.
Sample 1
Graphic (Spatial) Edits. These areas need to accurately reflect the boundaries of each geographically unique combination of fire, law and EMS responder zones. This layer is created and maintained by overlaying with some combination of street centerlines, municipal (i.e. city limit) boundaries, parcels boundaries, or other data to determine each jurisdiction’s emergency response service areas. As new emergency response services are added to, or change in an area, this boundary file will need to be modified accordingly. Communications must be regularly preserved with all fire, law, and emergency medical responders to obtain the information required to maintain updated ESZ boundaries. These ESZ boundaries should adhere to the specifications of CAPCOG’s QC systems and have no gaps or overlaps within a topology tolerance of +/- 3 feet. Topology and other geometric relationships between feature classes are especially important for NG9-1-1 purposes. In addition, it is very important that all features with identical attribute information are merged into one multipartpolygon.
Sample 1
Graphic (Spatial) Edits. Each of these layers is used by the ECRF to perform a geographic query to determine which Emergency Service Providers are responsible for providing service to a location in the event a selective transfer is desired, to direct an Emergency Incident Data Document to a secondary PSAP for dispatch, or to display the responsible agencies at the PSAP. In addition, Emergency Service Boundaries are used by PSAPs to identify the appropriate entities/first responders to be dispatched. Each Emergency Service Boundary layer may contain one or more polygon boundaries that define the primary emergency services for that geographic area. As new emergency response services are added to, or change in an area, this boundary file will need to be modified accordingly. Communications must be regularly preserved with all fire, law, and emergency medical responders to obtain the information required to maintain updated boundaries. These Emergency Service Boundaries should be within +/- 3 feet of their true location with no gaps or overlaps and can be created by dissolving the Emergency Service Zones polygon data. These items and other geometric relationships are referred to as “topology”, and especially important for NG9-1-1 purposes. In addition, it is very important that all features with identical attribute information are merged into one multipart polygon There MUST be a separate Emergency Service Boundary layer for each type of service. The set of Emergency Service Boundaries MUST include, at a minimum, the following: • Law Enforcement • Fire • Emergency Medical Services (EMS) Other Emergency Service Boundaries MAY include, but are not limited to: • Poison Control • Forest Service • Coast Guard • Animal Control
Sample 1
AutoNDA by SimpleDocs

Related to Graphic (Spatial) Edits

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

  • PATROL VIDEO SYSTEMS 2 1. As part of the law enforcement services to be provided to CITY, COUNTY 3 has provided, or will provide, patrol video systems (hereinafter called “PVS”) 4 that are or will be mounted in patrol vehicles designated by COUNTY for 5 use within CITY service area.

  • Programming Phase 2.2.1.2. Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Distribution Protocol (1) At a time wholly within the discretion of Class Counsel, but on notice to the Settling Defendants, Class Counsel will bring motions seeking orders from the Courts approving the Distribution Protocol. The motions can be brought before the Effective Date, but the orders approving the Distribution Protocol shall be conditional on the Effective Date occurring.

  • Electrical appliance safety The Hirer shall ensure that any electrical appliances brought by them to the premises and used there shall be safe, in good working order, and used in a safe manner in accordance with the Electricity at Work Regulations 1989. Where a residual circuit breaker is provided the hirer must make use of it in the interests of public safety.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Glass Or Safety Glazing Material a. We cover:

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

  • Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.

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