Layer title can be named slightly different from layer file name. Layer title is the English title that is included in the layer file. Please note that spacing is allowed for layer title, but, again, no special characters such as double dash (--), ampersand, comma, colon, slash, etc. are allowed anywhere in the layer file.
A layer title consists of several elements: English title, business prefixes (if necessary) and, scale (if necessary).
Examples:
Transfer of Administrative Control;
Water Lines (6M); and
Water Polygon – Outlined (250K).
For polygon layer, there is a need to create a group layer for outlined polygon, color filled/themed polygon, and the type of polygon must be specified for the layer in the layer title.
Polygon group layers—Transparent layer.
Three layers for every polygon layer should be created and grouped together in ArcMap.
Note that the fill transparency is set differently in ArcIMS compared with ArcMap. For example, if the transparency level in ArcIMS is set to 20%, the transparency level should be set to 80% (100% - 20%) in ArcMap.
7 Operational Database Standards
7.1 OverviewOnce a given dataset has been fully migrated to the warehouse, it will require an editable spatial layer in the operational database for continual maintenance. Ongoing maintenance takes place in the Operational Database. Each department within the Yukon Government is responsible for the administration and dissemination of their own data.
The operational environments are hosted by ICT in a shared environment or by the departments. Standards will not be as strict as for the CSW, but guidelines are required for easy management and integration. Also clear procedures are required for transferring of data from the operational databases to the CSW. The recommended environment for operational database is Versioned Geodatabase. A Geodatabase could only be edited by multiple users if it had been versioned. This includes all spatial and non spatial database tables. While this presents few problems for GIS-only databases, it does create some difficulties for business areas that use the same database for GIS and non-GIS applications due to the limitations of using native database relations and constraints.
Versioning strategies have to be well thought-out, and should closely replicate quality assurance/quality control (QC/QA) procedures within the departments.
Please note that at version ArcGIS 9.2, multi-user editing is possible without versioning.
ESRI has added a short transaction editing model for simple feature databases that can be applied on a table-by-table (feature class-by-feature class) basis. In this way, both GIS and non-GIS applications can share access to a common DBMS without adding the overhead of versioning to those applications that do not need it. For small number of users this will simplify the data management and also simplify the synchronization with CSW.
7.2 Current Environments
Currently, there are several production environments housing the spatial and attribute data. There are 2 production SDE servers, SDECSW is the Warehouse production server and SDEOPR is the operational production server. There are also servers to support the web mapping and imagery environments. Please refer to the Infrastructure diagram for a complete schematic of the current CSDI infrastructure.
7.3 Governance of the new Operational Environment This section still needs to be developed
7.4 Synchronization between operational databases and the warehouses The Operational Database is the master repository and the warehouse is synchronized with the Operational Database.
7.4.1 Using a bridge (acquirer)
Refer to Appendix C for a list of acquirers. All acquirers are housed on Flanker (a virtual server) under C:\Acquirers.
For users which are using multi-user Geodatabase operational environment, the
synchronization between the operational datasets and their corresponding datasets will be made using an acquirer (custom bridge), connecting to the source and target datasets using different connections managed by a data mapping process, called geoprocessing.
Acquirers are the means by which data flows from operational layers into the CSW.
Acquirers can either be continuous, reacting to and sending changes to the state of layers on a near real time basis, or they can be bulk, sending all information based upon a scheduled event. Acquirers can also be used to bridge between other Oracle databases.
In this process, the data custodian or data steward in charge of the data administration in the multi-user Geodatabase environment will be able to set one or more features to be transferred (as new or modified features) to its corresponding dataset in the CSW.
There are several ways to implement an acquirer based on the specific requirements (the frequency of the transfer, partial layer structure vs. the entire layer transfer, etc.). A detail requirements/design document needs to be created to define the acquirer.
An example on how to control the replication and synchronization of spatial features into the CSW is by enabling snapshot logs and adding the following columns to each dataset required for synchronization (assuming that both source and destination are simple SDE layers):
SOURCE_FID : Identifies the unique spatial ID assigned by SDE to identify a specific feature in the SDE. With this value, the geo-processing will be ale to identify from which feature the information comes from
SOURCE_VERSION : Identifies the SDE geo database version used in the source FID SOURCE_REPLTIME : Saves the replication date time in which the synchronization process takes effect
SOURCE_USER : Is the user that executed the geo processing
A custom application will check the columns and transfer the data as appropriate.
Manual synchronization
For data not stored in geodatabases
7.4.2 Check-in/Check-out process
Manual process used only when required on a case-by-case basis, especially when the master is housed in the warehouse. Assuming that the CSW is the master repository, a custom application could manage the check-in/check-out process. At a minimum, the
application records information about what layer was checked out, what user checked out the layer and when it was checked out. This minimizes the risk of having multiple users editing the same layer at the same time.
When the user is finished editing data from the check out file, he or she simply checks the layer back in. Now the layer is available for other users to edit and they can see the changes made by the previous user.
Pros:
1. Users will continue to edit in a familiar environment
Cons:
1. Only one user can work on a selected area at one time;
2. An application needs to be built to manage the check-in/check-out process and 3. The layer may be checked out by a user for a long time and prevent other users to
update the coverage.
7.5 Security and User Access
Operational staff, database administrators, business and application support staff, and development consultants (vendors) are participants in the operational database access.
The granting, controlling, and monitoring of access to the corporate information resources contained in the operational database is an important part for consistent management and protection.
The ArcGIS client/server architecture traditionally involves interaction between a user interface running on the client desktop (ArcInfo®, ArcEditor™, ArcView®, ArcGIS Engine) and centralized data source (RDBMS) managed by ArcSDE. The application logic can run on either the ArcSDE/database server or ArcGIS client.
The ArcGIS security can be achieved at four levels; application, operating system, network, and RDBMS controls:
• ArcGIS application controls are mechanisms that are implemented either through ArcGIS out-of-the-box configuration or custom application enhancement
(ArcObjects);
• Operating system controls are mechanisms that are implemented using operating system functionality and are integrated with ArcGIS through either out-of-the-box configuration or custom application enhancement (ArcObjects);
• Network controls are mechanisms that are implemented using standard networking techniques and practices; and
• RDBMS controls are mechanisms that are implemented in the RDBMS and
integrated with ArcGIS through out-of-the-box configuration or custom application enhancement (using ArcObjects).
For the purpose of this document only RDBMS controls are considered:
• Oracle has in-built security protocols that ensure that data stored in the RDBMS are protected against unauthorized access. These involve protocols for creating database users, roles and access to specific databases and tables within the SQL database; and
• The second security layer is provided by ArcSDE inbuilt functionality. ArcSDE tools are available to create database users and grant different roles to authorized users in order to edit, update, query or manipulate the Geodatabase from clients’ applications.
It is possible for multiple users to be editing the same data object (layer). These edits have to register in the database without the possibility of corrupting the database or making it unstable for other users who may not be necessarily carrying out edits to the database. This is where versioning and long transaction strategies come into play.
The following actions must be accomplished before data is loaded into the warehouse:
• An operational data model and a CSW data model must be created in the data model repository;
• Define the mapping between the operational and CSW (this will be used as an input to the Acquirer);
• All datasets must have a security role;
• Creation of database roles must be based on the custodian name;
• Base tables, whose data access is managed through database views; and shall have all direct grants removed.
To ensure that the database updates are transferred to the warehouse as seamless as possible, three factors need to be addressed:
• The new data must be structured to the same specifications as the data it replaces;
• The links to unchanged elements must not be broken; and
• Links to new or modified features should be automated as much as possible to avoid error and maintain data integrity.
From the security point of view her are the main RDBMS type of users:
• Database Administrator - this will be a government staff from ICT or departments that has full control over the database and monitors the access to the operational database. All the other accounts are created by the Database Administrator;
• Data administrator - this will be a government staff from ICT or departments that has full control over the dataset. The Data Administrator will make sure that any changes in the dataset are reflected in data model, CSW and the Acquirer; and
• Direct-connect analytical user (government staff or government sponsored) - this will be a user that uses a GIS tool to access the layer (edit or read only).
7.5.1 ArcSDE Multi user Geodatabase and Oracle Roles
At the operational level the Oracle roles should be developed based on the operational needs. However role naming should follow as close as possible the CSW naming convention.
7.6 Metadata
If the structure of the SDE layer in the operational database is identical with the SDE layer in the warehouse, only one record should be created and reference two source datasets. However, if the SDE layer structure is different from the CSW, a separate record should be created in the Metadata server.
7.7 Spatial Data Standards
It is recommended that the CSW naming standards should be followed as close as
possible. However, being a multi-user Geodatabase the feature dataset can be defined in a more complex way using ArcGIS topology, rules and relationships.
Geodatabase offers support for intelligent features, rules and relationships, allowing users to define topological and associative relationships/rules that determine how database objects interact, how they are edited and how referential integrity is preserved. CSW only supports simple SDE layers, so the Acquirer will have to do the transformation between the complex features and simple features
APPENDIX A Organizational Codes
Organization Code
Organization name
ENV Environment
MIN Mineral Resources
OIL Oil and Gas Management
YGS Yukon Geological Survey
FOR Forest Management
AG Agriculture
LAND Lands
CSI Client Services and Inspection
EMRLIB EMR Library
GEOY Geomatics Yukon
HER Heritage Resources
FIRE Wild land Fire Management
CLP Community Land Planning
TRAN Transportation Engineering
Transportation maintenance
NRC Natural Resources Canada
CIG Claims and Indian Government
YESAB Yukon Environmental and Socio-economic Assessment Board
YG Yukon Government
APPENDIX B: Corporate Spatial Warehouse (CSW) layers
SUBJECT AREA SCHEMA ACCESSIBILITY SDE FEATURE CLASS NAME
Administrative
Boundaries CSW_ADMIN_BOUNDARIES Lands only ADMIN_AREA_DERIVED_SURVEY_POLY
Public ADMIN_AREA_SURVEY_POLY
Public AREA_DEVELOP_BOUNDARY_POLY
Public BORDER_LN_1M_SVW
Public BORDER_SURVEY_LN
Public FN_SETTLEMENT_POLY_1M_SVW
Public FN_SETTLEMENT_POLY_250K_SVW
Public FN_SETTLEMENT_SURVEY_POLY
Public FN_TRADITION_TER_POLY_1M_SVW
Public FN_TRADITION_TER_POLY_250K_SVW
Public GAME_MANAGEMENT_AREA_POLY_250K
Public LAND_CLAIMS_COMMUNITY_POLY
Public LOCAL_ADVISORY_AREA_POLY
Public MINING_DISTRICT_POLY_50K
Public MUNICIPAL_BOUNDARY_POLY
Public NRO_DISTRICT_POLY_1M
Public NRO_SUBDISTRICT_POLY_1M
Public NYPR_LAND_MGMT_UNIT_POLY_250K
Public OILGAS_GRID_AREA_POLY
Public OILGAS_GRID_SECTION_POLY
Public OILGAS_GRID_UNIT_POLY
Public OUTFITTING_POLY_250K
Public PARK_PROTECTED_POLY_1M_SVW
Public PARK_PROTECTED_POLY_250K_SVW
Public PARK_SURVEY_POLY
Public PROTECTED_AREA_SURVEY_LN
Public PROTECTED_AREA_SURVEY_POLY
Public TRAPPING_POLY_250K
Public YESAA_ASSMT_DIST_POLY_250K
Public YESAA_MAPPED_COM_POLY_50K
Public YLUPC_PLANNING_REGION_250K
Public LAND_ZONING
Base Data CSW_BASE Public ADMIN_AREA_SURVEY_POLY
Public CONTOUR_LN_1M_SVW
Public HYDROGRAPHIC_PT_250K
Public TRANSPORTATION_ANNO_250K
Public TRANSPORTATION_ANNO_50K
Public WATERCOURSE_LN_1M_SVW
CSW_INFRASTRUCTURE Public BRIDGE_PT_25K
Transp only BRIDGE_PT_25K_TRANS_ONLY Transp only CULBERT_LN_10K_TRANS_ONLY Public CULVERT_PT_25K
Transp only CULVERT_PT_25K_TRANS_ONLY Public HIGHWAY_KILOMETRE_POST_SVW
Public PIT_PT_25K
Transp only PIT_PT_25K_TRANS_ONLY
Imagery CSW_IMAGERY Public AIRPHOTO_FLIGHT_LINE
Public AIRPHOTO_PT
Public BLUE_MARBLE_500M_SATELLITE_IMG
Public SHADED_RELIEF_300M_RSTR
Public SHADED_RELIEF_500M_RSTR
Public YUKON_MOSAIC?
Land & Natural
Resource Information CSW_BIOPHYSICAL Public ECOREGION_POLY_1M_SVW
CSW_CDC CDC only ELEMENT_OCCURRENCE_POLY
CSW_ENERGY Public GEOTHERMAL_ENERGY_PT
Public HYDRO_ENERGY_PT
Public WIND_ENERGY_PT
CSW_ENVIRONMENT Public WILDLIFE_KEYAREA_VAL_POLY_250K
Public WILDLIFE_KEYAREA_REF_TBL
Public WILDLIFE_KEYAREA_REF_RC
CSW_FIRE Public FIRE_YT_POLY_SVW
Public FIRE_YT_PT_SVW
CSW_FORESTRY Public FOREST_OPENING_POLY
Public LOGGING_ROAD_LN
Public PERMANENT_SAMPLING_PLOT_PT
CSW_GEOLOGY Public BEDROCK_GEOLOGY_POLY_250K_SVW
Public EARTHQUAKE_PT_250K
Public FAULT_LN_250K_SVW
Public FOLD_LN_250K_SVW
Public GEOCHEM_PROVINCE_POLY_250K_SVW
Public GEOPHYS_1ST_VERT_DRV_200M_RSTR
Public GEOPHYS_RTD_200M_RSTR
Public GLACIAL_LIMIT_POLY_1M
Public MINFILE_PT_250K_SVW
Public PHYSIOGRAPHIC_POLY_250K
Public REG_STREAM_2003_PT_250K_SVW
Public REG_STREAM_2003_SB_PT_250K_SVW
Public COMMUNITY_SERV_WEATHER_SITE_PT
Public CSI_SAMPLING_SITE_PT
SITE_PT
Public WATER_SURVEY_CANADA_SITE_PT
Economic Activity CSW_MINING Public ADJOINING_PARCEL_POLY_50K
Public AREA_WITHDRAWN_POLY_50K
Public MINERAL_CLAIM_SURVEY_POLY
Public PLACER_BASELINE_50K
Public PLACER_BASELINE_SURVEY_LN
Public PLACER_CLAIM_GRANTNUM_ANNO_10K
Public PLACER_CLAIM_GRANTNUM_ANNO_30K
Public PLACER_CLAIM_NAME_ANNO_10K
Public PLACER_CLAIM_NAME_ANNO_30K
Public PLACER_CLAIM_POLY_1M
Public PLACER_CLAIM_POLY_50K
Public PLACER_LAKE_CLASS_POLY_50K
Public PLACER_LANDUSE_PERMIT_POLY_50K
Public PLACER_LEASE_POLY_50K
Public PLACER_OPERATION_PT_250K
Public PLACER_STREAM_CLASS_LN_50K
Public PLACER_STREAM_LN_250K_SVW
Public PLACER_WATERSHED_POLY_50K
Public QUARTZ_CLAIM_DIRECTION_LN_50K
Public QUARTZ_CLAIM_GRANTNUM_ANNO_30K
Public QUARTZ_CLAIM_NAME_ANNO_30K
Public QUARTZ_CLAIM_POLY_1M
Public QUARTZ_CLAIM_POLY_50K
Mining only QUARTZ_CLAIM_POST_PT_50K
Public QUARTZ_LANDUSE_PERMIT_POLY_50K
Public QUARTZ_LEASE_POLY_50K
Mining only TENURE_GROUPING_POLY_50K
Public TENURE_HISTORICAL_POLY_50K
CSW_OIL_GAS Public EXPLOR_BASIN_POLY_250K_SVW
Public SEDIMENTARY_EXTENT_POLY_1M_SVW
Public SEISMIC_LN_SVW
Public WELL_PT
Land Tenure CSW_LAND_TENURE Public DEVELOPMENT_HOLD_POLY_SVW
Ag & Lands only DEVELOPMENT_HOLD_POLY
Ag & Lands only INSPECTION_GPS_LN
Ag & Lands only INSPECTION_GPS_POLY
Ag & Lands only INSPECTION_GPS_PT
Public LAND_APPLICATION_DENY_POLY_SVW
Ag & Lands only LAND_APPLICATION_DENY_POLY
Public LAND_APPLICATION_POLY_SVW
Ag & Lands only LAND_APPLICATION_POLY
Public LAND_DISPOSITION_POLY_SVW
Ag & Lands only LAND_DISPOSITION_POLY
Public LAND_PARCEL_REFPLAN_ANNO_5K
Public LOT_FOR_SALE_POLY
Public REFERENCE_PLAN_INDEX_POLY
Ag & Lands only SUITABILITY_KNOWLEDGE_POLY
CSW_AGRICULTURE_TENURE Public AG_APPLICATION_POLY_SVW
Ag & Lands only AG_APPLICATION_POLY
Public AG_DISPOSITION_POLY_SVW
Ag & Lands only AG_DISPOSITION_POLY
Ag & Lands only AG_PARCEL_CLOSED_POLY
CSW_LEGAL_SURVEY Public ANNO_SURVEY
Public ANNO_SURVEY_LLN
CSW_LICENSES_PERMITS Public OILGAS__DISPOSITION_POLY_SVW
Tourism and Culture CSW_HERITAGE Public? DESIGNATED_SITES_PT
Heritage IMS
only? YUKON_HISTORIC_SITES_RES_PT
Faro project CSW_FARO FARO IMS only BUILDING_POLY_8K
FARO IMS only GRID_LN_9K
FARO IMS only GROUNDWATER_SITE_GLL_PT
FARO IMS only INDEX_CONTOUR_LN_8K
FARO IMS only INTERMEDIATE_CONTOUR_LN_8K
FARO IMS only LAKE_POLY_8K
FARO IMS only SURFACE_WATER_SITE_ACCESS_PT
FARO IMS only SURFACE_WATER_SITE_GLL_PT
FARO IMS only TRAIL_LN_8K
Heritage Web
application CSW_HERITAGE
HERITAGE IMS
only YHSI_ALL_PT_SVW
only
HERITAGE IMS
only YHSI_CARMACKS_PT_SVW
HERITAGE IMS
only YHSI_CTFN_PT_SVW
HERITAGE IMS
only YHSI_DAWSON_PT_SVW
HERITAGE IMS
only YHSI_FARO_PT_SVW
*a total of 18 Spatial Views for Heritage web apps
APPENDIX C: Acquirers/Scheduled tasks
LandAcquirer
• Reads data from OPR_LAND_TENURE
• Writes to CSW_LAND_TENURE Migrate_nightly_OPR
• Removes hung connections, updates stats and compresses sdeoprp MiningAcquirer
• Reads data from OPR_MINING
• Writes to CSW_MINING Mining1Mclaim_CSW
• Dissolves boundaries between mining claims for display purposes MiningGrouping_OPR
• Reads from a spatial view in OPR_MINING
• Writes to TENURE_GROUP_POLY_50K in OPR_MINING Nrcan_FTPdownload
• Downloads from NRCAN ftpsite
• Writes to file geodatabases on sdeopr Nrcan_gdb2opr
• Copies data from file geodatabases
• Writes to SDEOPR schemas: ICM_ZONE07, ICM_ZONE08, ICM_ZONE09, ICM_ZONE10
NrcanAcquirer
• Reads data from SDEOPR schemas: ICM_ZONE07, ICM_ZONE08, ICM_ZONE09, ICM_ZONE10
• Writes to CSW_LEGAL_SURVEY, CSW_ADMIN_BOUNDARIES, CSW_MINING
YHSI-pointAcquirer
• Reads data from gysde HTMLDBP
• Writes to CSW_HERITAGE