Kodiak Island GIS Day. GIS Data Considerations Standards, Projections, Alaska Data Sources. Nathalie Smith ESRI Northwest

Transcription

1 Kodiak Island GIS Day GIS Data Considerations Standards, Projections, Alaska Data Sources Nathalie Smith ESRI Northwest 1

2 Key questions before starting What is the data I m working with or building designed for? What is the area I m collecting data for? For local datasets, use projected coordinate systems i.e., typical Alaska (statewide) coordinate system is Alaska Albers Equal Area Conic For global/small scale use geographic coordinate systems How accurate does my collected data need to be? What data characteristics are most important in the end product? 2

3 How well do you know your data? All GIS data is designed for a specific scale All decisions regarding storage, accuracy, etc. are influenced by the intended scale Metadata associated with your source data is invaluable If 2 datasets don t overlay, can you tell which one is wrong? 1. Considerations for Coordinate Systems 2. Considerations for Standards 3

4 Coordinates and Projections 4

5 Understanding coordinate systems What coordinate systems are used by the data? What coordinate system will the end product use? Choice of coordinate system is important Units Datum Projection 5

6 Choosing the right coordinate system What does your boss think? What are other government agencies/partners using? For what purposes are the data going to be used? Minimize projecting data on the fly Impacts performance 6

7 Unknown coordinate systems ALWAYS define the coordinate system Good professional practice help your successor Units are unknown Map scale is incorrect Geodatabase tools can t use default values 7

8 What do I do if I don t know my data s coordinate system? Check the data provider or source Check any existing metadata Similar data types What coordinate systems are used in the area? Try using ArcMap to figure it out See Article ID #: HowTo: Identify an unknown coordinate system using ArcMap Live Training Seminar (free) Working with Map Projections and Coordinate Systems in ArcGIS 8

9 Familiarize yourself with common coordinate systems Know what coordsys are used in your area of interest Learn what the layer extents should be Kodiak, Alaska NAD 1983 X / longitude Y / latitude Geographic UTM zone 6N 178, m 6,418, m State Plane (AK zone 5) 594, m 423, m 9

10 More information Don't forget the Knowledge Base! , 29129, 24893, 29035, ESRI forums for user-to-user help Virtual Campus Live Training Seminar and Course Database of coordinate systems & datums Guidance Note 7 10

11 Books, etc. Snyder. Map Projections: A Working Manual Flacke & Kraus. Coordinate systems in ArcGIS Elithorp & Findorff. Geodesy for Geomatics and GIS Professionals Snyder & Voxland. An Album of Map Projections. USGS PP Iliffe. Datums and Map Projections 11

12 ESRI Support for Standards in ArcGIS 12

13 Abstracting Geographic Knowledge 1. GeoVisualization 2. Decision Support 3. Serve to others Encapsulating Real World Knowledge Data Management Maps GIS Models Metadata Data Models Geodata Sets Geodatabase an Information System for Geography 13

14 Interoperability exchanging and using geographic knowledge the ability of two or more systems or components to exchange information and to use the information that has been exchanged * Semantic interoperability? Technical interoperability * IEEE 14

15 Overcoming barriers Four types of interoperability Technical Machine to machine connections Poor software module interaction Proprietary APIs Private formats Semantic Misunderstanding concepts, terms Special disciplinary vocabularies = Human Lack of cooperation Poor training Legal /Policy Loss of digital rights, ownership Lack of responsibility, 15

16 GIS Standardization functional areas 1. Basic Geographic Structures (semantic interoperability) Geometry, topology, coordinate reference systems 2. Content Description (semantic interoperability) Standardized Data Models, Feature Catalog Modeling languages, Application schemas Metadata 3. Data Management (semantic and technical) Database management 4. Data Formats (technical interoperability) Structure, Syntax, language, API 5. Visualization (semantic and technical) Symbology, cartography, display 6. GeoWeb Services (technical interoperability) Web Catalog, Web Services, SOA UC 2007 Tech GIS Day Sessions

17 Using standard s functional areas to provide geographic knowledge 1. Basic Geographic Structure Topology Vectors 2. Content Description Using standardized modeling languages and rules for application schemas 3. Data Management 4. Data Format 5. Visualization 6. Web services Street Parcel Name Networks Using standardized spatial schemas Schema for Rules Relationships Definitions Behavior Smith Building Producing user views 17

18 Different disciplines view/understand the world very differently Denali National Park Tourist attraction National park Biological reserve Disaster mitigation area Geological formation Earthquake study area etc Standardizing Content Description 18

19 Community standardized schemas to define rules, relationships, definitions, behavior 19

20 ESRI and ANSI Standardized GIS Data Models Field name Data type Allow nulls Default value Geometry Point Contains M values No Contains Z values No Precision Scale Domain Length OBJECTID Object ID SHAPE Geometry Yes HAULJOIN Long integer No 0 VESSELCODE Long integer No 0 CRUISE Long integer No 0 HAUL Long integer No 0 STATION_ID String No 7 SSTEMP Float No 0 0 BOTTOMTEMP Float No 0 0 EFFORT Float No 0 0 DataSourceID String Yes 50 TypeSimple Cardinality One to many Notification None Origin table Name DataSource Primary key DataSourceID Foreign key DataSourceID Forward label Backward label No relationship rules defined. Destination feature class NameHaul Haul DataSource TypeSimple Cardinality One to many Notification None Origin feature class Name Haul Primary key HAULJOIN Foreign key HAULJOIN Forward label Backward label No relationship rules defined. FishCatch Haul Destination table NameFishCatch Field name Data type Allow nulls Field name Default value Data type Allow nulls Domain Default value Precision Scale Length OBJECTID Object ID DESC_ String Yes 35 SOURCE String Yes 35 CONTACT String Yes 20 PREC String Yes 20 CREATE_DATE Long integer Yes 0 LAST_UPDATED Long integer Yes 0 DataSourceID String Yes 50 Domain Precision Scale Length OBJECTID Object ID HAULJOIN Long integer No 0 SPECIESCODE Long integer No 0 LATINNAME String No 28 COMMONNAME String No 21 WEIGHTCPUE Double No 0 0 NUMBERCPUE Double No Created locally, regionally, nationally, globally by community Subject Matter Experts Homeland security Cadastre Local government Agriculture Water Address Agricultural Atmospheric Base Map Biodiversity Census-Admin Boundaries Defense-Intel Energy Utilities Environmental Forestry Geology Groundwater Health Simple feature class Haul Relationship class DataSourceHasHaul Relationship class HaulHasFishCatch Table DataSource Table FishCatch Historic Preservation & Archaeology Homeland Security Hydro IHO Land Parcels Local Government Marine National Cadastre Petroleum Pipeline Telecommunications Transportation Water Utilities Candidate ANSI/INCITS-L1 FGDC Framework Theme models 1. Digital orthoimagery 2. Cadastral data 3. Geodetic control 4. Elevation 5. Hydrography 6. Transportation 7. Government Units

21 GIS abstracts geography into five basic elements Data Models Geodata Sets Encapsulating Real World Knowledge Process and Workflow Models Maps and Globes Metadata... Together They Represent the Building Blocks of Geographic Knowledge 21

22 Metadata Data about Data (official definition) Information that describes a resource (data) so it can be understood Ensures we find and use the right data for the right purpose And used correctly 22

23 Geographic Metadata 2. Content description Data about data Geographic area covered Currency Rules of use Positional accuracy Data dictionary Means of encoding Datum Map projection A Key interoperability technology: Producers explain their product Users learn about products Non standard products can be understood 23

24 Metadata Applications Understanding the right data for the right purpose Locate Find Discover Structured searches vs. unstructured Evaluate Restrictions Quality Reputation Extract Order Download Employ Building block of geographic knowledge Understand Pleasantville Pleasantville Pleasantville 24

25 Web Services 6. Geoweb Services GIS - Evolving to a web service environment Web Services Netw orks GeoWeb GIS Services Providing OGC Web Services Mapping services Viewing services Application Services... Dynamically Integrating Our Common Geospatial Knowledge 25

26 OGC Web Services Web Coverage Service Imagery and gridded data publishing/processing service Web Map Service Geospatial picture publishing/viewing service Global Map Abstract: vector data NOAA Weather htt Abstract: point featur Landsat Abstract: 30m satelli I-295 Catalog Service-Web Metadata publishing/search service Web Feature Service Geospatial feature publishing/streaming service 26

27 Simple feature class Haul Field name Data type Allow nulls OBJECTID Object ID SHAPE Geometry Yes Default value Geometry Point Contains M values No Contains Z values No Precision Scale Domain Length HAULJOIN Long integer No 0 VESSELCODE Long integer No 0 CRUISE Long integer No 0 HAUL Long integer No 0 STATION_ID String No 7 SSTEMP Float No 0 0 BOTTOMTEMP Float No 0 0 EFFORT Float No 0 0 DataSourceID String Yes 50 Relationship class DataSourceHasHaul TypeSimple Forward label Haul Cardinality One to many Backward label DataSource Notification None Origin table Destination feature class Name DataSource NameHaul Primary key DataSourceID Foreign key DataSourceID No relationship rules defined. Relationship class HaulHasFishCatch TypeSimple Forward label FishCatch Cardinality One to many Backward label Haul Notification None Origin feature class Destination table Name Haul NameFishCatch Primary key HAULJOIN Foreign key HAULJOIN No relationship rules defined. Table DataSource Field name Data type Allow nulls Table FishCatch Field name OBJECTID Default value Data type Object ID Allow nulls Domain Default value Precision Scale Length OBJECTID Object ID DESC_ String Yes 35 SOURCE String Yes 35 CONTACT String Yes 20 PREC String Yes 20 CREATE_DATE Long integer Yes 0 LAST_UPDATED Long integer Yes 0 DataSourceID String Yes 50 Domain HAULJOIN Long integer No 0 SPECIESCODE Long integer No 0 Precision Scale Length LATINNAME String No 28 COMMONNAME String No 21 WEIGHTCPUE Double No 0 0 NUMBERCPUE Double No 0 0 ESRI approach to interoperability Supporting Multiple Approaches Web Services Standards Web Services OGC/ISO Basic Structure Standards Content Standards Data Models Metadata (19115/19139) DXF, KML... ArcGIS Desktop Transformation Procedures (ETL) Formats ETL = Extract, Transform & Load Data WMS WFS WCS Schema WFS-T GML Semantic WMS WFS WCS Catalog ArcIMS / ArcGIS Server Management Standards Standards Organizations GIS Education Providing Data and Services Visualization Standards... Providing An Open & Standards-based Environment... And Enabling Successful Collaborative Systems

28 Alaska Data Resources ArcGIS Online (topos for entire state and other base data) GINA (WMS service from UAF) Alaska State Geospatial Data Clearinghouse: Alaska Geospatial Data Clearinghouse: (note: census data is available from this page and several federal links) Dept. of Commerce Community Profile Maps: ftp://ftp.dcbd.dced.state.ak.us/profiles/profile-maps.htm 28

29 Local Government Examples: Fairbanks North Star Borough: Municipality of Anchorage: Kenai Peninsula Borough: Mat-Su Borough: 29