|
|
|
|
|
|
GIS Cooperative Meeting Notes
City Information Technology Dept. Pueblo Room
Tuesday, April 20, 2004
GIS Cooperative Chairman Steve Whitney presiding.
Electronic Plan Submission Guidelines
The Electronic Plan (EP) subcommittee has finalized the guidelines for plan submittal in electronic format, and they are as follows:
These Electronic Plan Guidelines are provided to help in the construction of the Pima County GIS landbase. The landbase is used by government agencies, utilities, private companies and the public. The landbase is made up of subdivisions and development plans. When new ones come in, this new information updates the existing landbase. Providing data electronically in a timely manner makes the landbase more current, accurate and useful as a community resource.
Notes:
- These guidelines are for subdivisions and development plans only. The purpose is to keep the GIS landbase as current as possible.
- The submission of EP information does not change or circumvent any agency's development review process or requirements.
EP Guidelines:
1. EP Format
a. If a CAD drawing is submitted, it should be in DWG or DGN format.
a. If GIS data is submitted, it should be in Shapefile format (Shapefiles must include all relevant files, such as .shp, .dbf. and .shx).
a. The CAD drawing or GIS data should include the complete subdivision (or block) plat set or development plan sheets.
a. 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).
a. GIS data should include a separate Shapefile for each feature. (For example all lot lines should be in one Shapefile, street center lines in another Shapefile.)
2. EP Email
a. Email electronic plans to: subdivisions@dot.pima.gov . This email will automatically forward message and files to all the participating agencies.
a. The Name and Status (Tentative/Final) of the project should be in the subject line of the email.
a. The CAD drawing, GIS data, and any other related files should all be attached to the email.
a. Any special fonts, X-REFs, or attachments should be included in the email.
a. A data dictionary, or metadata, should be sent in the email that explains the name of each layer/level or Shapefile. This information may be in a simple text file, Word Document, Excel spreadsheet, or in the body of the email itself. (For example, Par2 = Parcels, Street = Street Centerlines)
a. Optional: If the CAD drawing has a ctb file (color palette),it should be included as well, so the printed version looks like the original design.
a. Optional: If possible, zip together all files into one zip file, named with the project name.
a. Optional: If possible, please include a projection file or a note with the spatial reference. (For example, this data is in Arizona State Plane Central, NAD83, International Feet).
Please direct any comments that you have on any of the above to Steve Whitney or Laura Pinnas by the end of the day next Wednesday, May 5, 2004.
Emergency Response Subcommittee
The Emergency Response subcommittee met and is focusing on three main activities:
a. Data - create a table of emergency response layers, then classify them by their existence, availability, security, etc.
a. Application - focus on TPD's pilot project, along with visiting the Phoenix Fire Department to check out their system.
a. Hardware - ensure that proposed hardware upgrades at TFD will be suitable for GIS applications.
Pictometry Demonstration
The Pictometry presentation was very well receved. The PAG Regional Data Committee (RDC) met on April 29, 2004 and is exploring the possibility of doing a pilot project with Pictometry before the end of this fiscal year (June 30, 2004).
Next Meeting:
Tuesday, May 18, 2004 / 3:00 P.M / City I.T. Pueblo Room
|
| |
|