GeoSpatial Data Creation     It is highly recommended that prior to creating data, you enrol in a few of the corporate GIS courses (such as Introduction to ArcGIS and Creating and Editing of Spatial Data) to get hands on experience with data creation standards.

Format

• Storing data in an ESRI Feature Class within a Personal Geodatabase is the first Choice. However, although less desirable, ESRI Shapefiles are still an acceptable alternative for storing data.
• Geodatabase and feature class design should take into account current as well as future needs to minimize the modifications.
• Attribute Field names should be logical but as concise as possible with no spaces .
• Where possible, attribute domains (picklists of valid values) should be utilized to maintain data integrity.

Spatial Reference

• Refers to the coordinate system, spatial domain (the allowable coordinate range for x,y coordinates, m- (measure) values, and z- (elevation) values) and precision (the number of system units per one unit of measure) of the feature class.
• A pre-defined spatial reference for York Region has been created and is stored in SDW under the name "YorkRegionSpatialDomain".
• Coordinate System : NAD 1983 UTM Zone 17.
• Spatial Domain: Min X = 500000, Max X = 21974836.45, Min Y = 4770000, Max Y = 26244836.45
• Precision = 100

Topology

• Wherever possible topologically integrated editing should be applied to ensure that rules such as those listed below may be enforced:

• At a minimum, Map Topology, which can be applied to feature classes and shapefiles should be implemented during editing.

Metadata

• Metadata should be created for all data and must be created for data stored in the corporate GIS data warehouse (please see Metadata Standards for more detail).

Corporate Value

• It should be determine if the data being created has corporate value and whether it should/could be stored in the corporate GIS data warehouse (i.e. are their others that would be interested in viewing your data).