Mission Statement and Goals
Mission Statement
The North Dakota GIS Initiative mission statement was developed by representatives of the GIS Technical Committee in December 2001:
The State of North Dakota's GIS Hub will provide the essential infrastructure to share core geographic datasets through an accessible data warehouse among Stakeholders with browsing ability to the general public. The Hub will leverage the State's existing data, infrastructure and expertise to implement the core elements of this enterprise solution.
This mission statement supports the business needs that were developed in January 2002 by representatives of the GIS Technical Committe. In order of priority, with the highest being the first, the business needs are:
- » Need improved access to GIS data from other agencies
- » Need to provide access to GIS data for more users
- » Need to improve the distribution of data between agencies
- » Need to improve the distribution of information to the public
- » Need to acquire data from other agencies in a more timely fashion
- » Need to reduce and avoid the cost of data storage
- » Need to reduce the costs of data maintenance
- » Need to reduce the cost per user for GIS
- » Need to develop security model for sensitive GIS data
- » Need tools to find and assess datasets
- » Need to provide a common framework to host spatially-enabled web applications
- » Need to improve GIS data consistency
Goals
The mission statement and the business needs provide the foundation for the goals listed below that have been identified by the GIS Technical Committee.
2003-2005 Biennium
» Obtain lower cost storage
» Merge Geological Survey clearinghouse with the Hub
» Data-specific agency goals:
- updated DOQQs
- 1:24k hydrology
- consistent DEMs, perhaps 10m DEMs
- HUCs
- NWI
- city aerial photos
- updated roads
- imagery, e.g., Landsat, original land use
- updated utilities
» Complete a geodetic survey layer
» Promote view of geographic information as critical information asset which should be protected in case of power failure, fire, flood, investigate back-up services (such as off-site storage, redundancy, etc.). Define critical applications. One such application could drive the need for an infrastructure that all other applications would have to utilize
» Service Level Objectives - a current level of service along with what can be expected. Include data storage types, database, and web services
» Develop customized training
» Outreach GIS: Assist in the communication of GIS activities and standards at tribal, county, city, and higher education levels. Develop a contact list, consider use of forums. Assist in GIS in K-12
» Set up the WMS and WFS ArcIMS connectors (for OpenGIS, utilization by USGS and Houston Engineering). However this cannot be done at the expense of the agencies
» Set up the Z3950 ArcIMS connector for OpenGIS applications, used for cataloging information
» Develop maintenance schedule of existing framework data. Be aware of agency's plans for updates to assist in our prioritization
» Improved ADA of Hub Explorer
» Grow the GIS Day event
1-3 Year (2003-2006)
» Data:
- Identification of existing or missing National Spatial Data Infrastructure framework layers (i.e., geodetic control, orthoimagery, elevation, transportation, hydrography, governmental boundaries and cadastral information.) These can be then be categorized into the users (e.g., education, economic development, tourism, emergency management) of this data to help us prioritize those layers not yet developed and the resources required to develop these. For each of these layers, identify the cost of updating these and define MOUs with interested counties, cities, Tribal, etc. to develop and maintain these layers.
- State-wide centerlines: <1m, attributed for addressing and routing, workflow set up where counties maintain the data and the NDDOT compiles the data.
- 6" color ortho rectified for prioritized metro areas
- NWI coverage for the entire state
- additional .5 TB of storage required for this goal
» Greater/easier access to Hub by remote agency field office, e.g., better connections from GNF, P&R, Health Dept. field offices. Develop 3-5 additional Hub applications
» Provide tools to allow all interested GIS parties to publish metadata onto the ND Hub Metadata Explorer. We would have to provide the metadata tools, conversion utilities, etc.
» Drop support for ArcView 3.x (e.g., _line suffix, being aware of ramifications of having to remove the _poly). Consider using a projection on the Hub, develop our own state projection. This would assist in tools like ArcPad, and improve grid size/precision, area, length. Creates other issues, e.g., which projection to use, create our own, etc.
» Standards: for data sharing, accuracy standards, more understandable metadata standard. Use a data model
» Manage: separate SDE instances, control versions, licensing
» Provide the tools to allow extracting the data on a state-wide basis, or within an existing clipping polygon, e.g., a county boundary
» Establish clearinghouse of activities - e.g., an Imagery I-Team..so that we know and can share on plans to acquire data
» Hub editing environment - ArcSDE and ArcIMS, including disconnected editing
3-5 Year (2006-2008)
» Data:
- State-wide updated DOQQs at 1:12,000 or better
- 6" color ortho rectified for an additional 5 prioritized metro areas
- Additional 1 TB of storage required for these data sets
- Additional funding for updating Framework layers and adding new ones such as, weather, fire, cadastral, planimetrics such as building footprints, etc.)
» 3-5 additional Hub applications
» Redundancy, mirroring of data at alternate sites
» County use of hub, including access, data submittal, etc.
5-7 Year (2008-2010)
» Data:
- State-wide updated DOQQs at 1:12,000 or better
- Updated 6" imagery for all cities about 15,000 - maintenance schedule
- Additional .5 TB of storage required
- Additional funding for updating and adding new Framework layers
» GIS FTE - application development - other? Needs justification!
Top
Back
Print Friendly Version