A. SUMMARY This dataset is used to report on public dataset access and usage within the open data portal. Each row sums the amount of users who access a dataset each day, grouped by access type (API Read, Download, Page View, etc). B. HOW THE DATASET IS CREATED This dataset is created by joining two internal analytics datasets generated by the SF Open Data Portal. We remove non-public information during the process. C. UPDATE PROCESS This dataset is scheduled to update every 7 days via ETL. D. HOW TO USE THIS DATASET This dataset can help you identify stale datasets, highlight the most popular datasets and calculate other metrics around the performance and usage in the open data portal. Please note a special call-out for two fields: - "derived": This field shows if an asset is an original source (derived = "False") or if it is made from another asset though filtering (derived = "True"). Essentially, if it is derived from another source or not. - "provenance": This field shows if an asset is "official" (created by someone in the city of San Francisco) or "community" (created by a member of the community, not official). All community assets are derived as members of the community cannot add data to the open data portal.

A. SUMMARY The dataset inventory provides a list of data maintained by departments that are candidates for open data publishing or have already been published and is collected in accordance with Chapter 22D of the Administrative Code. The inventory will be used in conjunction with department publishing plans to track progress toward meeting plan goals for each department. B. HOW THE DATASET IS CREATED This dataset is collated through 2 ways: 1. Ongoing updates are made throughout the year to reflect new datasets, this process involves DataSF staff reconciling publishing records after datasets are published 2. Annual bulk updates - departments review their inventories and identify changes and updates and submit those to DataSF for a once a year bulk update - not all departments will have changes or their changes will have been captured over the course of the prior year already as ongoing updates C. UPDATE PROCESS The dataset is synced automatically daily, but the underlying data changes manually throughout the year as needed D. HOW TO USE THIS DATASET Interpreting dates in this dataset This dataset has 2 dates: 1. Date Added - when the dataset was added to the inventory itself 2. First Published - the open data portal automatically captures the date the dataset was first created, this is that system generated date Note that in certain cases we may have published a dataset prior to it being added to the inventory. We do our best to have an accurate accounting of when something was added to this inventory and when it was published. In most cases the inventory addition will happen prior to publishing, but in certain cases it will be published and we will have missed updating the inventory as this is a manual process. First published will give an accounting of when it was actually available on the open data catalog and date added when it was added to this list. E. RELATED DATASETS

A. SUMMARY Location, cap color and other key attributes of parking meters in San Francisco. Does not include operating schedules or rate schedules. B. METHODOLOGY Updated via the SFpark data warehouse (Parking Space Inventory) by meter shop staff, with manual updates sourced from SFMTA CAD drawings and MTAB resolutions. C. UPDATE FREQUENCY Updated weekly. D. OTHER CRITICAL INFO For active meters only, filter for "Active_Met" = 'M" or "T". Meter operating and rate schedules are more complex and available as separate tables. Key field for joining is the Parking Space ID field.

A. SUMMARY This dataset contains all Street Vendor Permits issued by the Department of Public Works whose status is active or approved including the approximate location of the vendor. B. HOW THE DATASET IS CREATED The dataset pulls permit information from the Department of Public Works system of record. C. UPDATE PROCESS This dataset will refresh once a week, though the underlying data can be updated at any time. D. HOW TO USE THIS DATASET Use this dataset to understand the location, goods sold, and type of permit issued for street vendors. Please note that "roaming" vendors will not have a latitude or longitude. Learn more about the program here. E. RELATED DATASETS

A. SUMMARY This dataset contains information of Mental Health (MH) and Substance Use Disorder (SUD) programs / sites. It serves as provider directory for the general public to know and search for MH and SUD programs / sites contracted with the City and County of San Francisco. B. HOW THE DATASET IS CREATED The dataset is pulled from our electronic systems. C. UPDATE PROCESS The dataset is updated nightly through sf.gov through Application Programming Interface (API) whenever there are changes. There is monthly review and tracking. D. HOW TO USE THIS DATASET There are filters for some data fields for quick search. For example, if we want to search all MH and SUD programs that serve women, we would use the Gender filter and select “Women” and “All”. E. RELATED DATASETS

A. SUMMARY This dataset contains information of Mental Health (MH) and Substance Use Disorder (SUD) programs / sites. It serves as provider directory for the general public to know and search for MH and SUD programs / sites contracted with the City and County of San Francisco. B. HOW THE DATASET IS CREATED The dataset is pulled from our electronic systems. C. UPDATE PROCESS The dataset is updated nightly through sf.gov through Application Programming Interface (API) whenever there are changes. There is monthly review and tracking. D. HOW TO USE THIS DATASET There are filters for some data fields for quick search. For example, if we want to search all MH and SUD programs that serve women, we would use the Gender filter and select “Women” and “All”. E. RELATED DATASETS

A. SUMMARY Lookup table for City lots (Parcels), which enables the tracking which lots were the successor lots for the new lots created. The data is in changelog format, meaning each row is a change of parcel_id -- containing both the old parcel id and the new parcel_id. B. HOW THE DATASET IS CREATED This dataset is extracted from the SFGIS database C. UPDATE PROCESS This dataset will update daily D. HOW TO USE THIS DATASET Use this dataset to track and analyze how parcels have changed over time. E. RELATED DATASETS Parcels Active and Retired Map of Active Parcels

A. SUMMARY This dataset consists of San Francisco International Airport (SFO) air traffic cargo dataset contains data about cargo volume into and out of SFO, in both metric tons and pounds, with monthly totals by airline, region and aircraft type. B. HOW THE DATASET IS CREATED Data is self-reported by airlines and is only available at a monthly level. C. UPDATE PROCESS Data is available starting in July 1999 and will be updated monthly. D. HOW TO USE THIS DATASET Airport data is seasonal in nature; therefore, any comparative analyses should be done on a period-over-period basis (i.e. January 2010 vs. January 2009) as opposed to period-to-period (i.e. January 2010 vs. February 2010). It is also important to note that fact and attribute field relationships are not always 1-to-1. For example, Cargo Statistics belonging to United Airlines will appear in multiple attribute fields and are additive, which provides flexibility for the user to derive categorical Cargo Statistics as desired. E. RELATED DATASETS A summary of monthly comparative air-traffic statistics is also available on SFO’s internet site at https://www.flysfo.com/about/media/facts-statistics/air-traffic-statistics

Summary List of street blocks with parking meters.

Parking citations issued by the SFMTA. Citation information includes citation, violation and location details which indicate the location and amount of parking citations throughout the city. Citation data is provided by the SFMTA as an export of the citation management system. Citation data is provided daily and the DataSF datasource is updated daily with a 24 hour lag. The geolocation is based on a geocoding process upon load and may not be accurate based on incomplete address data. For more information on violation codes and descriptions, go here.