16-Appendix L - Enterprise Geographical Information Systems (GIS).pdf

Appendix L - Enterprise Geographical Information Systems (GIS)

Enterprise Geographic Information Systems (GIS)

This appendix is intended to give GIS standards that will be adhered to on all bids, Request for Proposals (RFPs), Request for Competitive Sealed Proposals (RFCSP), grant programs, and volunteer non-profit efforts of the City. This appendix also applies to any other business partners’ solution leveraging location-based GIS technology. These standards are intended for all parties submitting data and/or delivering geospatial solutions that will, or potentially could have, a reliance and/or dependency on the City’s GIS.

Minimum GIS Standards

The City GIS standards are a group of standards outlined for City geospatial datasets, datasets that include spatial attributes, infrastructure, services, resources, and applications.

Conformance to these standards is required by all parties including Proposers, business partners and contractors alike. All proposed solutions shall conform to the standards.

Conformance to these standards will ensure that proposed spatial solutions will seamlessly integrate the City’s GIS and other business systems in a consistent and sustainable manner.

GIS Metadata:

The City requires Federal Geographic Data Committee (FGDC) compliant documentation for all data to be included in the City GIS database.

The FGDC Content Standard for Digital Geospatial Metadata (CSDGM) has been adopted by the City as the documentation or "metadata" format for all data included in the City GIS database.

Participating parties are responsible for providing documentation in FGDC compliant metadata format for geospatial data products.

FGDC metadata is the required documentation of all geospatial data products produced through partnerships, suppliers, grants, or contracts. Geospatial data collected or produced by City Departments must adhere with all relevant standards adopted through the FGDC process.

Departments are to verify compliance prior to obligating funds. These standards are required if the data is collected or produced directly or indirectly. Indirect data collection or production refers to data from or through grants, partnerships, suppliers, or contracts with other entities.

Projection (Coordinate System) (PCS) Requirement All geospatial data will be delivered in the City standard PCS. State Plane North American Datum 1983, North Central Texas, FIPS 4202, GRS 80 Spheroid, Units feet (SRID 2276).

Digital GIS Data

Digital data submitted for inclusion in the City GIS database will be topologically clean and free of errors. All points, lines, and polygons will have a single unique user-id number (Long Integer).

Data will have:

No overshoots No slivers No open polygons (e.g., undershoots) No label errors No unresolved node errors No unresolved line segment intersections Contiguous features should be edge matched or closed Line segments (arcs) that intersect the boundaries of a coverage/layer must be accurately edge matched with corresponding datasets Map features should not extend beyond prescribed dataset boundaries Arcs must not extend beyond (overshoot) nor fall short of (undershoot) the dataset boundary

Raster (Image) Data

All Geospatial image (raster) data delivered will be in the one of the following formats:

Ortho Rectified Tagged Image File Format (TIFF)/Tagged Image File (.TIF) with accompanying Text World File (.TFW) Ortho Rectified Joint Photographic Experts Group (JPEG/JPG) with accompanying

JPEG/JPG World file (.JGW) Ortho Rectified Multiresolution Seamless Image Database (MrSID) Security Identifier (.SID) with accompanying StarOffice Writer Document (.SDW) World file

Attribute Coding Accuracy

If data is deemed by the City to contain errors, it will be the data provider’s responsibility to correct the data attribute errors.

It is the responsibility of the producing agency or City department that has entered a contract with the producing agency to verify that the data has been encoded within the accuracy limits set by the standards. The City GIS Services division (Enterprise GIS/ITS) will not verify attribute accuracy of the delivered data. It is the responsibility of the data provider to confirm the accuracy.

Attribute Coding Requirements:

Data and codes should be both consistent and the descriptions well documented in the metadata or data dictionary

Attribute coding schemes should be well defined and in common use Names of new datasets should not be the names of existing datasets in the City GIS database unless replacing that dataset Begin all dataset names, item names, and attribute codes with a letter.

Eliminate punctuation, including hyphens, pound signs, and periods, from dataset names, item names and attribute codes Define items according to intended use, i.e., numeric data types for statistical data or for data that will be used for calculation, characters data types where these functions are not anticipated.

Eliminate the use of the Boolean values 0 and 1 as attribute codes Wherever practicable utilize character attribute codes, i.e., previously defined acronyms or abbreviations in common use.

Any physical property (street) address (Address Format) will be broken into its component fields as follows:

o Street Address Number o Street Prefix direction o Street Name (make sure they are spelled correctly) o Street Type - US Postal Service (USPS) abbreviations required. Cf. USPS Publication 28, Section C.

o Street Suffix direction o City o State o USPS ZIP Code

Address Validation Requirements

Validation of addresses and geocoding, all parties will use the City approved standard locator service(s) only, per the business requirements for the application. The URL for the locator service(s) will be provided upon request by the Purchasing Agent.

City GIS Infrastructure and Associated Technical Requirements:

The contracted Proposer shall leverage City Enterprise GIS infrastructure without modification (as-is). This includes the edition that the City is leveraging at the time of the implementation.

o The City standard for data sharing for applications is the ArcGIS Representational State

Transfer (REST) Application Programming Interface (API) * or comparable technology.

o The City public REST endpoint (catalogue URL) is:

http://gis.dallascityhall.com/wwwgis/rest/services.

o The configuration of City Enterprise GIS infrastructure will not be modified to support the technical requirements of a proposed application or system. If any customization is required, an instance of GIS web application and/or database software is required separate and apart from the Enterprise GIS infrastructure. Further, the cost of a stand-alone instance for GIS application and/or database software and associated hardware must be included in the proposal as separate line items. The City cannot supply dedicated GIS licensing or hardware to support an application.

o If the proposed application requires the editing of data via the application, the data must be hosted on a database separate and apart from Enterprise GIS infrastructure.

o If the proposed application requires an ArcGIS Online subscription or access to ArcGIS Online * or comparable technology, the Proposer must provide the subscription and adequate Named Users as part of the proposal. This cost must be included in the proposal as separate line items. The City cannot use its ArcGIS Online Organizational account to support a third-party system.

o Under no circumstances, shall it be assumed that Enterprise GIS will make allowances to support a proposed system without prior affirmative commitment from the GIS Manager, the ITS Executive over Enterprise GIS, or the CIO.

o The publication of dedicated standard read-only REST services to support a business need may be requested for the implementation of proposed system, provided that the City has the data to support the services and the services do not require any custom functionality or non-standard configurations.

Questions from Proposers on Solutions adhering to GIS Standards

If there is a question about whether a technical requirement or specification of a proposed system may not conform to City GIS standards, the Proposer should forward the question through the Purchasing Agent assigned to the bid for handling.

Comparable products will be reviewed by the City Enterprise GIS/ITS group and determination of compatibility will be made. If compatibility of given solution is not equal or above the identified City requirement the City Enterprise GIS/ITS group has the right to exclude the solution from consideration.

The City leverages Federal Geographic Data Committees (FGDC) Geospatial Standards. These published standards can be seen at https://www.fgdc.gov/resources/download-geospatial-standards.

The City reserves the right to require adherence to FGDC Geospatial standards in the absence of internally published City geospatial standards.