Specifically, the City minimally requires: • Access to any data via APIs in a machine-readable format. • Full documentation of APIs (including field names and objects) and the database schema used by the application. • Ability for City to push data as needed to these software systems to update base datasets. • Any location-based data or platform utilizes the City’s Base Units geocoder, Base Units Database, and/or address data standards as applicable. For more information see: https://base-units-detroitmi.hub.arcgis.com/pages/about-base-units • The ability for the City to use and govern this data as it deems necessary- - centralizing it, porting it into other systems, and using it for additional and future organizational needs. The City prefers: • System or platform has the capacity to store field-level metadata and display it in the user interface when appropriate • API is able to provide data in a JSON format. • Data system or data exports integrate easily with ESRI products including feature services. • Systems or platforms that support data exchanges (pushes and pulls) that can happen dynamically.