YLUPC
QualityControl – Yukon Planning Atlas

Quality Control

Table of Contents

  1. PlanYukon Regional Planning Database Best Practices Wiki
    1. Background
    2. Purpose
    3. Framework
    4. Roles
    5. Acknowledgment
  2. Getting Started as an Administrator
    1. Introduction
    2. Helpful Software
      1. Text editor
      2. Subversion
        1. Troubleshooting
      3. MS4W
        1. Trouble-Shooting
    3. Trac
    4. WinSCP
    5. pgAdmin III
  3. Data File Management
    1. Valid Spatial Data Sources
      1. Vector Files
      2. Raster Files
      3. Non-local Data
    2. Accepted Data Projection
    3. Data File Naming Conventions
    4. Data File Contents
    5. Data File Storage
    6. Database Architecture
      1. Specifications
      2. Tables
        1. groups
        2. layers
        3. layers_perm
        4. spatial_ref_sys
        5. themes
        6. themes_perm
        7. users
        8. widgets
        9. widgets_perm
    7. Government of Yukon CSW Catalog WMS Service
      1. GetCapabilities
      2. Supported Projections
      3. Native Projection
      4. Layer Names
      5. Scale Ranges
  4. Data Styling
    1. Background on MapServer .map files
    2. Theme Files
    3. Template Files
    4. Layer Files
    5. .Lay Guidelines
      1. Naming
      2. Groups
      3. Layer TYPEs
      4. Metadata
      5. Field Formatting
    6. Using Classes
    7. Using Styles
    8. Labeling
      1. Available Fonts
      2. Label Size
      3. Label Scale
      4. Label Force
      5. Label Partials
      6. Label Minfeaturesize
      7. Label Buffer
      8. Label Priority
    9. Symbols
    10. Projection
      1. EPSG Usage
      2. PROJ.4 Usage
    11. Using Scales
      1. MINSCALE and MAXSCALE Deprecated
      2. Atlas Scale Ranges
  5. Metadata Management
    1. Implemented Standards
    2. Layer Metadata
      1. Atlas Keywords
    3. Theme Metadata
    4. Accessing Metadata through the Atlas
    5. Accessing OGC Metadata through the WMS Service
      1. GetCapabilities Request
    6. Management Tools
      1. ArcCatalog?
        1. About
        2. Functionality
        3. Assessment
      2. CatMDEdit
        1. About
        2. Functionality
        3. Assessment
      3. gvSIG
        1. About
        2. Functionality
        3. Assessment
  6. Data Processing Work Flow
    1. Step 1: Preparing the Spatial Data
      1. Guidelines
      2. Getting the Required Tools
      3. Documentation For Command Tools
      4. Useful Commands
        1. Reproject a Vector File
        2. Merge 2 Vector Files
        3. Keep Only Specific Attribute Values
        4. Keep Only Specific Fields
        5. Prep Raster Files
    2. Step 2: Create a .lay file
      1. .lay Templates
        1. Vector File Template
        2. Raster File Template
        3. WMS/OGC Template
      2. Generate .lay Metadata
      3. .lay Guidelines
    3. Step 3: Submit for Publication
    4. Step 4: Publishing a Layer
    5. Step 5: Add Layer to Existing Theme File
    6. Step 6: Verify Layer Processing
    7. Refresh Layer Data
  7. Quality Control
    1. Layer Quality Assurance Checklist
      1. Published Layer QA Checklist Forms
    2. Data Optimization Checklist
    3. Publishing Atlas Data
      1. WMS Mapfile Location
      2. Publish Local Data to WMS
      3. MapServer Required Metadata
      4. WMS GetCapabilities Warnings
      5. GeoConnections Discovery Portal Registration
  8. Recommended Data Management Tools
    1.  MXD2WMS
    2.  FGS
    3.  MapServer for Windows
    4.  QuantumGIS
    5.  uDig

Layer Quality Assurance Checklist

A form has been created for recording QA procedures.Make the Checklist the description for a new ticket as follows: 

[[Include(QualityChecklist)]]

The following checklist should be applied to preparation of data for the Atlas:

DATA SUBMISSION
IDRequirementTeam Member initialsDate MM/DD/YY
1data is in the accepted Atlas projection (if not, see Useful Commands)
2data is properly optimized (shptree or gdaladdo)
3.lay metadata is complete (using the  Metadata Generator)
4.lay metadata is free of typo graphical errors
5data has been uploaded to the Atlas server
6the .lay file changes have been committed to svn
7Ticket transferred to Atlas Admin for approval (identify access constraints in comments)

The following checklist should be applied to publication of data for the Atlas:

DATA PUBLICATION
IDRequirementTeam Member initialsDate MM/DD/YY
8execute an svn up on the atlas.planyukon.ca server
9complete record in the layers database table has been created for this .lay file
10add the .lay file to a test.map and verify that a map image is created for the data with the  shp2img utility
11 add the published layer to a Theme if desired
12verified the layer has been processed through the  layer_list online tool
13if the layer is part of a published theme, verify that no warnings exist in the WMS  GetCapabilities request
14 Confirm layer and Theme are present and functioning properly in the Atlas interface

Published Layer QA Checklist Forms

Data Optimization Checklist

The following guidelines should be followed to ensure that Atlas data is displayed to the user as fast as possible:

  1. Is the format of the data either ESRI Shapefiles for vectors or GeoTIFFs for rasters?
  2. Is the data indexed?
  3. Are excessive labels causing a slower draw time?
  4. For vector files, have unused fields/columns been removed?
  5. Does your layer use an excessive amount of expressions, especially logical expressions?
  6. Where you are using many classes in a layer, is it possible to separate each class into a separate data file?
  7. Have you removed any unused symbols and fonts from the symbolset and fontsets?
  8. If you are referring to an EPSG file for projections, have you moved the common EPSG codes to the top of the file?

Publishing Atlas Data

The following guidelines exist to manage the Atlas data served to the public through the WMS Standard.

WMS Mapfile Location

All WMS .map files should be placed in the /themes/wms/ folder. These describe wms data being used by the Atlas, not published by it.

Publish Local Data to WMS

Local data may be served up through the database-driven data manager and mapserver to the Atlas without being served as a WMS. To do this, the data .lay must be INCLUDEd in wms-public.map. Try a GetCapabilities request and search for the new data.

MapServer Required Metadata

For a list of required metadata please see the Metadata Management pages.

WMS GetCapabilities Warnings

All warnings must be removed from the Atlas'  WMS GetCapabilities

  • if you get the following warning for a RASTER layer: 
           <!-- WARNING: Optional LatLonBoundingBox could not be established for this layer.  Consider setting LAYER.EXTENT or wms_extent metadata. Also check that your data exists in the DATA statement -->
    you will have to add ows_extent metadata for the layer (which is the 'minx miny maxx maxy' bounds, obtained through the gdalinfo utility if it is a raster file, or through the GetCapabilities of the WMS server).

GeoConnections Discovery Portal Registration

The Atlas WMS service must be registered and maintained in the Discovery Portal as a CGDI Web Service (example:  http://geodiscover.cgdi.ca/gdp/search?action=entrySummary&entryType=service&entryId=7191&entryLang=en)

During registration, it is important to specify appropriate themes in that portal entry so users can find Atlas data when they search by theme (these themes should be similar to the WMS service's keywordlist metadata)