STRAIGHT CONNECTOR 7 QUALITY CHECKLIST ADMINISTRATIVE BOUNDARY COD |

PROBLEMS REQUIRE A STRAIGHTFORWARD DERIVATION SUBSTITUTION OF NUMBERS
(FORMAT SURAT USULAN) (KOP SURAT) STRAIGHT ARROW CONNECTOR 2
041 STRAIGHT CONNECTOR 2 CRNA GORA ADRESA BULEVAR REVOLUCIJE

1) THE STRAIGHTLINE GRAPH WITH GRADIENT OF 3 HAS
11 UỶ BAN NHÂN DÂN TỈNH BẮC GIANG STRAIGHT
127 UPI ZAHTJEV POPUNITI ČITKO STRAIGHT CONNECTOR 2 CRNA

Quality Checklist - Administrative Boundary COD

STRAIGHT CONNECTOR 7 QUALITY CHECKLIST ADMINISTRATIVE BOUNDARY COD | Quality Checklist Administrative Boundary COD | 2




Quality Checklist

Administrative Boundary COD



  1. Spatial relationship and topology

  • The administrative boundaries are closed polygons.


    1. All administrative boundaries are represented as closed polygons


  • The administrative levels are nested.


    1. The polygons of one admin level fall into one and only one polygon at the next largest level. Boundary edges of the polygon layers are consistent.

  • There are no missing polygons.


  1. All admin units at a given level are represented (no missing polygons)


  • If there is a multiple distinct polygon, it is represented as a single record.


  1. A single administrative unit that consists of multiple distinct polygons (for example a coastal area + islands) is represented as a single record with multipart geometry.


  • The topology of the polygons is clean.


  1. The polygons of the same administrative boundary level are topologically clean (no overlaps, gaps, voids or superfluous lines). A visual check can give an immediate impression of errors. See the Geodata Manual for instructions on topological cleaning in ArcMap.



  1. Projection

  • The projection is defined, correct and consistent.


  1. The projection is defined and is correct and consistent among different administrative boundary unit layers. Instructions on how to define the projection are in the Geodata Manual.



  1. Data characteristics and attributes

  • The national boundary is Admin level 0. The subsequent subdivisions are numbered / named consistently.


  1. The national boundary is Admin level 0. The first subdivision is Admin level 1. The second subdivision is Admin level 2, etc. Option: the files can be named in any way that is consistent and clear concerning the administrative boundary unit levels, or the file naming convention can be used.


  • Name and p-code of administrative boundary units are included at each level.


  1. Essential fields to be included at each administrative boundary unit level are the name of the admin unit and its unique p-code. Names in non-western scripts (such as Arabic) should be reflected in another name field in western encoding. The administrative boundary unit names and p-codes must be able to be considered ‘official’ for the humanitarian response.


  • The p-code uses a national system code.


  1. The p-code format must use any available national systems. Otherwise it can be generated using the p-code guidance and must be consistent throughout the administrative boundary unit levels.


  • The name and p-code fields of higher levels are included


  1. The names of higher-level admin units to which a given feature belongs should be included and must be identical to the ones in the higher-level admin units. P-codes of higher-level admin units should be included where available, as names sometimes are not unique.


  • Only essential fields are included.

  1. Only essential fields are included (no population, agricultural production, or other extraneous information are included). See the Geodata Manual for more information about essential, marginal, and external attribute field. Option: an area field can be included as long as the units are calculated in square meters or square km and the field name makes this clear. Shapelength fields are rarely relevant for administrative boundary unit polygons.


  • The Field names are clear.


  1. Field names should be as clear as possible. For example ‘DISTRCT’ is preferable to ‘D_NAME’. ‘PCODE’ is preferable to ‘ID’. If they are not clear, they must be documented in the metadata. Field names should be consistent for the same attributes (ie. p-codes and administrative unit names) throughout the administrative unit levels.


  • Attribute names should be in proper case, not all caps.


  1. Attribute names should be in proper case, not all caps. Attribute names do not need to be unique.


  • A Reference name field is included if names of administrative units contain apostrophes or special characters.

  1. If any of the names have accented characters (é, ò, etc.), apostrophes or are in a non-western script, a Reference name field should be included that contains a version of the name without accented characters or apostrophes. . Reference names do not need to be unique. Spaces and hyphens are allowed. The reference name is expressed in proper case. For example, the administrative unit name ‘Sixt-Fer-à-Cheval’ would become ‘Sixt-Fer-a-Cheval’.



  1. Metadata

  • Metadata is developed if the dataset is not self-explanatory.

  1. It is possible to construct administrative boundary datasets such that metadata is not required for a user to understand it.  If this is not given, then some level of metadata is required. Metadata should also explain terminology used in field names. Metadata options can be seen in the Geodata Manual.



  1. Dataset format and names

  • The Administrative Boundary datasets are at least posted as shapefiles.

  1. The Administrative Boundary COD should be posted at least as shapefile or GML. Posting them as ArcGIS geodatabases is possible. An Excel version of the tabular data formatted for easy use by report officers and others is highly recommended. Other formats such as KML can be included if desired.


  • File names follow the file naming convention.

  1. The file names for the datasets should be indicative of the content. File names should be harmonized following the file naming convention in the File and Dataset Management Manual.



  1. Comments


  1. Any comments that you would like to make a note of (for example on the data source, dataset updates etc.)




STRAIGHT CONNECTOR 7 QUALITY CHECKLIST ADMINISTRATIVE BOUNDARY COD |

Quality Checklist - Administrative Boundary COD


138 LATVIJAS REPUBLIKAS DAUGAVPILS PILSĒTAS DOME RSTRAIGHT CONNECTOR 1
14 LATVIJAS REPUBLIKAS DAUGAVPILS PILSĒTAS DOME RSTRAIGHT CONNECTOR 1
15 JUNE 2018 LEGAL & GENERAL INVESTMENT MANAGEMENT LSTRAIGHT


Tags: administrative boundary, - administrative, boundary, quality, checklist, connector, straight, administrative