Title: Menominee GIS
1Emergency Planning and Gaining Trust Taxing
Issues
Paul Crocker, GISP Menominee Tribal
Enterprises And Paul Cegelski, GISP Menominee
Indian Tribe of Wisconsin June 15, 2009
2Outline - A Case Study at Menominee
- Background
- The Event
- Response
- Lessons Learned
- Integration of the Lessons
3Background
- BS. and MS. in Forestry from MTU, emphasis on GIS
and Remote Sensing - Working with GIS for over 11 years
- GISP certified
- GIS/Inventory Forester for MTE since 2005
- Responsible for maintaining the GIS and Inventory
program for the Menominee forest (220,000
acres) - Paul Cegelski at Menominee Community Development
maintains GIS on the non-forested trust lands
4The Event
- June 7, 2007
- EF3 Tornado, up to 1/2 mile wide, covering 12
miles across the reservation - Primarily affected timber and severed several
main roads including State Highway 47 - Affected two heavily-used lakes (high potential
for death or injury near the lakes)
Photo courtesy WAOW-TV
5(No Transcript)
6Menominee Indian Reservation
Tornado Path
7Response Initial Challenges
- Command Issues (whos responsibility?)
- multiple jurisdictions were affected
- Priorities
- Coordination within and between agencies
- Communication (with the public, within agencies)
- Search and Rescue (was there anyone out there?)
- Timing
- storm occurred after hours
- accuracyperfection is the enemy of good enough
(tricky balance between speed and quality)
8Response The Plan (and the role of GIS)
- Immediate needs (1-7 days after storm)
- road maps for field personnel
- organizational structure
- information gathering and reproduction
- Intermediate needs (1-5 weeks)
- accurate map of tornado path, and estimate of
timber volume within this area - imagery flown by Ayres Associates
- Long-term needs (5 weeks)
- salvage operations
- map updates
9Response
- Implemented the Incident Command System (ICS)
- Initial Assessment GIS and maps to coordinate...
- Overflights, visual estimation and GPS
- Ground recon
- GIS and associated DBs essential for salvage
planning - Job delineation
- Volume estimation
- Documentation
10(No Transcript)
11Response
- Resources on-hand were valuable in improving
coordination between organizations - base layers
- constantly updated road status and refined the
tornado footprint - established Heli-spots to facilitate rapid
evacuation in the event of medical emergency - maps and coordinates were distributed to most
regional EMS organizations
12(No Transcript)
13Lessons Learned
- Having a plan in place before an event occurs is
essential. Plan should include - chain of command (ICS proved vital)
- all of the maps in the world only add to the
chaos in the absence of a systematic approach in
a rapidly changing situation - responsibilities
- data
- communications
- trained personnel
14Lessons Learned
- Organization of GIS resources greatly improves
efficiency - trained personnel
- leverage existing geodatabases
- maximize use of map templates/base maps
- must have clear process for integrating changes
and communicating these back to field personnel
and management - maintain good relationships with possible imagery
vendors and other contractors
15Integration of Lessons at MTE
- Developing a Disaster Management Plan
- Emphasis on Training (e.g. Red Cards, ICS mapping
training/experience) - Maintain current database and mapping resources
(e.g. software, printers, etc) - Be prepared! Be prepared! Be prepared!
16Any quick questions before we move on
Image Courtesy of University of
Wisconsin-Milwaukee
17Outline Gaining Trust Taxing Issues
- Background
- Problems with MIS
- Data! Data! Data!
- Current Issues and Future Plans
- Indian Reservation Roads (IRR) GIS
18Background
- Paul Cegelski, GISP
- GIS Coordinator
- Started at MITW December 2007
- Never worked directly for a government agency
- New to Tribal policies and history
- Learned quickly about parcels owned by Tribe
(Trust) and County (Tax)
19Menominee Reservation/County
20GIS in the County
- Working together
- Menominee Indian Tribe
- Menominee County
- Menominee Tribal Enterprises
- College of Menominee Nation
21Sorry, we are experiencing technical
difficulties. Please stand by
- MIS difficulties
- No idea what ESRI/ArcInfo was used for
- Lost software installation CDs
- No support
- Had other, more pressing issues
- Thought we would continue to just use AutoCAD,
no reason to switch
22Dude, wheres my data?
- Utilizing existing data
- In AutoCAD format
- Data created for engineering purposes in no
coordinate system and origin at 5000,5000 - Sifting through directories and CDs to find
usable data - Constantly getting new data requests
- As GIS becomes more known, getting the can you
do this request
23Parcel Data
- Used AutoCAD file from County GIS dept.
- Slowly cleaning parcels to join to County and
Tribal property DBs - Used AutoCAD text to create address and Parcel ID
- Missing on many Trust parcels
- Text insertion point outside parcel polygon
- Need to make up new parcel IDs
24Parcel Data (pt 2)
- Verifying information
- CAD Annotation
- Link to Assessment data
- Local knowledge
- Working towards completion
- Tax Trust are delineated correctly
- County Tribe property DBs joined
- Real Estate has access and uses data
- ArcReader
- ArcGIS Server
25Parcel Data (pt3)
- Original property lines COGOd
- Somehow the parcels around the Legend Lake area
got moved - Other data created based on location of bad
parcels over the years
26Gaining Trust
- For staff to utilize GIS
- Accurate data
- Easy to use
- Data services that support their daily tasks
- Data stewards
- Getting people who use the data to control their
data - They will want to make sure the data is correct
27Hurdles
- Organizational Cultural vs. Rebuilding Challenge
- Preserve heritage
- Locate archeological sites keep secure
- Help maintain sustained development
- Supporting new ventures
- Providing new tools to solve age-old problems
28What are we doing now?
- Current projects
- Parcels
- Commercial/Recreational buildings
- Verifying/correcting IHS utility data
- Photos of Trust properties
- ArcSDE ArcGIS Server
- Creating an Indian Reservation Roads GIS
29Creating a useable IRR GIS
- Staff used printed IRR database
- Fields chopped off
- Unless you know where every road is, difficult to
find data - Creating dataset
- Merged roads from start to end
- Split by sections
30IRR GIS
- Create unique join fields
- Create new field to concatenate route number and
section number in both DB and GIS layer
31ArcReader IRR GIS
- Now engineers are able to use the IRR data
without having to go through paper inventory,
even use it for planning
32Questions?