Carshare pilot spaces

| A. PURPOSE | This feature class was first created as part of the SFMTA On Street Car Share Pilot Program (approved by the MTA Board in July 2013) to illustrate the location of implemented and planned (various stages) spaces throughout the city.

| B. METHODOLOGY | The locations were originally provided to the MTA as requests by the three car share organizations (CSOs). These were given as a .kml file, which was converted to a .shp. Additional fields were created using spatial joins (zipcode, supervisor district, CNN, etc). Use definition query tool to display those locations with a certain attribute. For example, query Existing = 1 to display those locations that are on street operating. 500 submissions were given by CSOs to the MTA, but only a portion of those were brought to the MTA Board for approval, and even fewer were implemented as operational on street spaces. With no definition query, you can see all spaces as features, with varying levels of data completion.

| C. UPDATE FREQUENCY | During periods of implementation/construction, updates were as frequent as daily or weekly. However, as the frequency of newly implemented spaces slowed over the course of the pilot, updates occured less frequently--weekly or monthly. Updates will be needed as new spaces are implemented--many of the spaces not taken past MTA Board approval have incomplete data.

| D. OTHER CRITICAL INFO | Each feature (or each row, or point) represents a single car share parking space. Some parking spaces belong to a "pod" where there are two adjacent car share parking spaces, indicated by the "PodType" field. To summarize or analyze by pod, use the "POD" field.

| E. ATTRIBUTES | Space ID: Unique identifier for the on-street car sharing space (refers to the CSO and location of the space request, where City CarShare begins with C; Getaround with G; Zipcar with Z. All numbers are three digits); INTERSXN: The nearest intersection to the car share space (this is included for ease of discussion (e.g. this space is at Grove and Ashbury, inst...


Publishing Department: Municipal Transportation Agency

Dataset Link: https://data.sfgov.org/d/5nea-2cc2

Field Name (opt. alias)Field DefinitionAPI Key
CNN (Centerline Network Number)Centerline Network Number is the primary key/identifier for a street segment or node assigned by the Department of Public Works in the city's official basemap. Segments refer to lines representing the street, nodes represent points where two or more segments intersect. CNN IDs are often found encoded as text (CNNTEXT) or numbers (CNN). Basemap street segments are available here: https://data.sfgov.org/d/7hfy-8sz8; Basemap intersections (nodes) are here: https://data.sfgov.org/d/ctsg-7znqcnn
CNNTEXT (Centerline Network Number)Centerline Network Number is the primary key/identifier for a street segment or node assigned by the Department of Public Works in the city's official basemap. Segments refer to lines representing the street, nodes represent points where two or more segments intersect. CNN IDs are often found encoded as text (CNNTEXT) or numbers (CNN). Basemap street segments are available here: https://data.sfgov.org/d/7hfy-8sz8; Basemap intersections (nodes) are here: https://data.sfgov.org/d/ctsg-7znqcnntext
CREATED_DATEcreated_date
CREATED_USERcreated_user
HH_PEDMODEhh_pedmode
LAST_EDITED_DATElast_edited_date
LAST_EDITED_USERlast_edited_user
MAXPCTSLPEmaxpctslpe
MODEL6_VOLmodel6_vol
OBJECTID (ObjectID)The system ID generated by Esri ArcGIS software. Not an administrative ID.objectid
PCOL_04_09pcol_04_09
PCOL_RATEpcol_rate
PKGMETERSpkgmeters
SIGNALIZEDsignalized
ST_NAME1st_name1
ST_NAME2st_name2
ST_NAME3st_name3
ST_NAME4st_name4
ST_TYPE1st_type1
ST_TYPE2st_type2
ST_TYPE3st_type3
ST_TYPE4st_type4
the_geom (Geometry)Contains the geometry of the record in Well Known Text (WKT) format.the_geom
TOTEMP2totemp2
UNIVPROXunivprox