City Logo, Return to Tucson's Main Page City of Tucson Home Page E-Services City Calendar Visitor Info Business Info Guide to City Services Contact info Menu Bar
GIS Home Page
About GIS
Purpose of the Cooperative
Presentations
Official Address Guide
Geographic Data Library
GIS Infrastructure
GIS Infrastructure
Meeting Minutes
Subcommittees
Off Site Links
Files for Downloading

GIS Cooperative Meeting Notes

City Information Technology Dept. Pueblo Room

Tuesday, March 16, 2004

Present: Steve Whitney, PC DOT; Don Ijams, TPD; Dave Koss, TDOT RE; Ron Platt, TDOT; Blanca Espino, COT DSD; Pablo Garcia, City Clerk; Jack Avis, Marana; Manny Rosas, PAG; Autumn Figueroa, COT CPTF; Tracy Gutheim, PC DSD; Chris Kelleher, TDOT; Steve Smith, TDOT; Joe Urrea, TEP; Bill Murum, COT DSD; Mike Rose, The Planning Center; Marina Yusufova; TDOT; Karol Aragonez, COT CPTF; Jesse Reyes, COT CPTF; Laura Pinnas, TEP; Dee Korick, COT Env. Svcs.; Anita Velasco, COT Comm.; Chuck Beauchamp, COT IT; Chaz Tompkins, PAG; Teri Schultz, TFD; Christine O'Connor, COT IT; Bob Czaja, COT Water; Leticia Bermudez, COT DNR; Joe Gulotta, TFD.

GIS Cooperative Chairman Steve Whitney presiding.

GIS Certification/Registration/Licensure for GIS Professionsals

Steve Whitney presented an overview of efforts to expand the Arizona Professional Land Surveyors (APLS) organization to include Geospatial professions, including GIS, photogrammetry, geodesy, and geomatics, thereby creating a Geospatial Organization (GO) that combines the primary mapping disciplines. Here is a white paper on the subject:

Arizona Professional Land Surveyors (APLS)
Geospatial Professional Proposal


History: In 2002 the APLS Board was reviewing whether an organizational change was warranted. Through direction from the APLS Board, Ron Platt (City of Tucson - GIS Manager) formed the Group of 12. This Group of 12 (actually 13), included members of the surveying community (6), members of both the Surveying and Geographic Information System (GIS) community (3), the GIS (only) Community (3), and one tie-breaker (Ron). The Group reviewed the commonalities and differences among players, discussed issues before all members of the geospatial community, and looked for possibilities to unite these groups in some manner.

In November of 2003, the Group held a facilitated meeting where it doubled in size and found a voice. It was determined through this meeting that a sub-committee to the APLS Board (made up of Surveyors and GIS'ers) would research the potential to redefine APLS for the incorporation of all Geospatial Professionals under this umbrella organization.

Geospatial Subcommittee Tasks:

  • Review the existing APLS Bylaws
  • Make recommendations to for change to the existing APLS Bylaws
  • Promote the change
  • Define Membership Levels

Who are Geospatial Members:

· Surveyors · GIS Professionals · Photogrammetrists · Geodesists · Geomatics Professionals

Why Expand APLS:

  • Dynamic World: The advent of GPS and GIS have changed the face of historic surveying
  • All Geospatial Professionals have a common mission, common tools, and technologies
  • A conduit for the expansion of knowledge / educational opportunities / COMMUNICATION /
  • Organization shall still continue the APLS traditions of promoting education and professional advocacy
  • Enhancement of the current scope of the organization - support legislative agendas with all Geospatial Professionals in mind

The Process for Change - Geospatial Sub-committee

  • Proposed Bylaws revision - (available for review at Azregistrants.com)
  • Definition and incorporation of new membership
  • Sunset clause included - two years (24 Month Trial period)
  • APLS Board Review / General Membership Vote for any approval to this reorganization

What are the Major Changes to the Bylaws:

  • Two Professional Membership Classes - Professional Land Surveyor and Geospatial Professional.
  • Professional Geospatial Membership Class will be reviewed and defined via the Geospatial Subcommittee of the APLS Board. Once class is defined, members will then have opportunity to migrate to the professional level (from associate).
  • Associate Membership - Initially include ALL Geospatial Professionals
  • One Geospatial 'at-large' membership on the APLS Board during the 24 Month trial period

Standing Committee changes:

  • Two New Standing Legislative Committees
  • Registrant and Legislation Issues for Professional Surveyors
  • Certification and Legislation Issues for Geospatial Professionals

Each Committee shall have a minimum representation of 25% comprised from the other professional class.

The emphasis on this whole effort is the opportunities that will exist by combining the forces of our respective professions, specifically in the areas of communication, education, and standards. We are taking a proactive approach to bring issues to the table and find consensus on them as a combined group of professionals. This will be a standing agenda item.

Here are links to the Model Law and to the Model Rules.

GIS Library Additions

New elevation models, ELNED1PE and ELNED1TU, have been added. These two elevation layers were extracted from the 10 meter National Elevation Dataset (NED). ELNED1PE covers Eastern Pima County and ELNED1TU covers the Tucson basin. These are in ESRI Grid format. Metadata is also available.

Electronic Plan Submittal Subcommittee

Laura Pinnas reported that this subcommittee would be meeting shortly. The primary goal of this effort is to define some guidelines for electronic plan submittal, i.e. separate layers for each theme, data dictionary, etc. Here are the latest draft guidelines:

  • The drawing should be in AutoCAD DWG or DGN format.
  • The base drawing should be submitted, not individual sheets. The CAD drawing should include the entire project area.
  • Each CAD layer should be assigned to a unique set of CAD features within the drawing. (For example all lot lines should be on one layer, street centerlines another layer).
  • There must be no mixing of CAD features among the layers, so only one feature type should exist on each layer (for example, do not have points and lines on the same layer.)
  • A CAD layer "Data Dictionary" should be provided explaining the layers or levels used for each feature in the drawing. The Data Dictionary may be a simple text file, Word Document, Excel spreadsheet, or email text and provided with the submitted drawing file.
  • If possible, all features should be exploded and not in blocks.
  • Any special fonts should also be included.
  • The CAD drawing and/or any other related documents should be zipped into a single file.
  • If possible, the development boundary should be tied to a minimum of two Public Land Survey System (PLSS) Monuments and if the area is greater that 160 acres, it should be tied to four or more Public Land Survey Monuments.
  • The submission of Electronic Plan information doesn't preclude or circumvent any agencies development review process or requirements.
  • Email Submittals to: Subdivisions@dot.pima.gov

References:

Pima County DOT - City of Tucson DOT Section Corner Reference Sheets

The Surveying System in Pima County

Emergency Response Subcommittee

This subcommittee first met on March 10, 2004 with good attendance. The major action items that came out of that meeting include:

  • Inventory themes that currently exist on Tucson Fire Department (TFD) paper maps.
  • Inventory databases that TFD currently uses.
  • Look at Tucson Police Department's system, and the potential for test-driving it.
  • Look at proposed TFD laptop specs.
  • Set up a field trip to Phoenix Fire Department to review their system.


Here are the full minutes from that meeting:

TFD Wish List

  • Provide electronic information to emergency responders (live and stored).
  • Electronic information should include:
  • Electronic maps specific to the incident, with the ability to zoom and pan.
  • AVL location of units responding to specific incident. AVL has 13-15 second update rate, and locations are in Lat/Lon.
  • Map layers: streets, hydrants, water zones, sewer, drainage/waterways with flow direction, natural and liquid gas lines, electric lines (above and below ground), building footprints, site photos, access routes, equipment/facility locations, pre-plans (need simple way for fire personnel to inventory/map facilities and package the data for system integration.
  • Logistics for sensitive layers will need to be developed. Potential sensitive layers include natural gas, electric, liquid gas, water, and sewer networks. More exists and will be identified.
  • Opportunity exists to further rectify addressing problems via increased integration with E911 systems and field verification.
  • Pre-plan information including: specific building floor plans, hazardous materials, access and other site-specific information.
  • Combine with TPD system?
  • Merge with applicable Fire Department SOPs.

First Steps

  • Don't want to repeat past mistakes, i.e. buy a bunch of technology then find that the data/applications don't really fit.
  • Identify the pieces to a potential emergency response system, i.e. GIS spatial layers and attribute tables, existing mapping applications (MapGuide, TPD, etc.) and the development/programming expertise behind them, communications infrastructure and applications, etc. Classify each piece as something we have in place or in development, or something that we need to acquire.
  • A draft RFP for TFD laptops is about ready and will be made available to the subcommittee for review. Focus of conversation was hard drive size and processor speed. The long-term plan is to replace/augment each response vehicle's CRT(?)-based CAD system with the laptops.
  • The mechanism for GIS/attribute data storage and updates hinges on laptop hard drive size, wireless update potential, CD and/or DVD laptop drive, frequency of updates, etc.
  • Potential for TPD's system to be test driven by TFD.
  • Inter-jurisdictional integration of emergency response mapping systems is very preliminary.

List GIS data layer themes that should be included

  • A partial list has been put forth under TFD Wish List above.
  • TFD will inventory their paper maps to identify the layers that are displayed. The layers will then be categorized by which exist digitally, and which do not. Desired additional layers may be identified in this step as well.
  • The existing grid-based plat system that is used for the paper maps was discussed. The grid system is 1/4 Section based, and a suggestion was made to explore migrating to PLSS nomenclature. Tucson Water stated that the fire hydrants in their GIS are referenced by the plat system. The point was made that if Section boundaries are adjusted, feature attributes associated with their spatial location within a PLSS reference system would have to be updated.

List database themes that should be included

  • TFD will inventory the information that is available through the CAD system. Desired additional data may be identified in this step as well.

Where can we get further guidance?

  • TPD, with their work on on-board GIS capabilities.
  • Phoenix Fire.
  • Marana PD.

Systems that can pull all this data together

  • The potential for TFD to test-drive TPD's system will be explored.
  • A field trip to Phoenix Fire will be arranged.
  • There is a threshold at which point too much information is being delivered to effectively make decisions, i.e. on route to an emergency. This points out a difference between CAD textual data and map-based data.
  • Electronic redlining capabilities would enable field verification and updating.
  • Printing capabilities should be explored.

Funding

  • There exists a HR issue, in that TFD could use additional GIS staff.
  • Homeland Security grants, and others.
  • Suggestion that grant money be used to hire photogrammetric firm to extract building footprints from the existing PAG orthophotos, or from future imagery projects.

Open floor.

  • Joe Gullota volunteered to chair this subcommittee.

Expanded Membership

This topic was brought up as a reality check to see if the group is still amenable to further expanding participation in the GIS Cooperative. Christine O'Connor pointed out that the original report that started the group reflected that this would be a City hosted group, and one of the main objectives was to build partnerships. It was agreed by all in attendance that we should continue to expand the participation.

Other organizations that were mentioned as not regularly participating include COT Parks & Rec., other City departments, other area fire departments, and utilities. Obviously we could list many more off the tops of our heads, so if you have other suggestions for who should be participating in the Cooperative, please send them to the chair. Meanwhile, we should consider putting together a white paper on the Cooperative and its project efforts for this year, which could then be distributed to potential participants.

Budget

All budget requests have been reviewed by Steve Whitney and Larry Cassen, and it looks like we have enough to finish out the budget for this fiscal year. A meeting will be scheduled with the requesting parties to finalize the procurement details.

Open Floor

Manny Rosas - PAG will focus its next round of jurisdictional member training on ArcGIS introductory classes and possibly a mid-level ArcGIS course.

Christine O'Connor - The City Information Technology Customer Advisory Board (CAB) meets on Tuesday, May 4th, 3:00 - 4:30 p.m. in the IT Pueblo Room. GIS Cooperative representation is encouraged.

Steve Whitney - Proposes moving the email list to the Geowiz listserv, to further encourage the use of this forum for discussing issues and passing along information.

Next Meeting:

Tuesday, April 20, 2004 / 3:00 P.M / City I.T. Pueblo Room