Name: Single Space Parking Meters

Display Field: METER_ID

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: Of the 7,800 parking meter spaces across the city, 4,000 are handled by the multiple-space payment kiosks that will remain in place. The 3,800 on-street single (or double-headed) meter spaces will all be converted to Smart Parking Meters by July 30, 2014. Approximately 700 to 725 new meters to be installed, this consist of old, broken and missing meters as well as new meters within commercial districts that were approved by City Council.The City of Oakland has coverted existing "coin-only, single-space, on-street" parking meters in retail and business districts across Oakland with state-of-the-art "Smart Parking Meters". The Smart Parking Meters provide a credit-card enabled, single-space mechanism which retrofits onto the existing poles. The meters offer multiple payment options (coins, credit/debit cards and pay-by-phone). They use solar powered/rechargeable battery technology and are managed wirelessly through a web-based management system, which means no additional technology infrastructure is required. The meters are provided by IPS Group, Inc. (design and manufacturing company) focused on low-power, wireless communication parking devices. Oakland parking meter times, rates and times of operation will remain unchanged. Enforcement and citations will also remain unchanged.On December 18, 2014, Enes Ceric, Project Manager of IPS Group, Inc., emailed us the Excel data.There were 4,512 records, but 31 pay station data points were removed, resulting in 4,481 records. There are 208 Latitude-Longitude coordinates and 5 meter IDs that repeat. Also, 2 records do not have x,y coordinates. According to Allen Law, the Public Works Electrical Services Manager, the contractors installed 3,863 Smart meters.

Definition Expression: N/A

Copyright Text:

Default Visibility: false

MaxRecordCount: 1000

Supported Query Formats: JSON, AMF, geoJSON

Min Scale: 4000

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: true

Can Modify Layer: false

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: 6043485.518441141
YMin: 2108526.530638963
XMax: 6071937.202679396
YMax: 2139886.3048615456
Spatial Reference: 102643  (2227)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Label:
Description:
Transparency: 0
Labeling Info:
Label Placement: esriServerPointLabelPlacementAboveRight
Label Expression: [METER_ID]
Use Coded Values: true
Symbol:
Color: [0, 0, 0, 255]
Background Color: N/A
Outline Color: N/A
Vertical Alignment: bottom
Horizontal Alignment: center
Right to Left: false
Angle: 0
XOffset: 0
YOffset: 0
Size: 9
Font Family: Arial
Font Style: normal
Font Weight: normal
Font Decoration: none

Min. Scale: 0.0
Max. Scale: 0.0

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID , alias: OBJECTID )
• METER_ID ( type: esriFieldTypeString , alias: METER_ID , length: 255 )
• STREET_ADDRESS ( type: esriFieldTypeString , alias: STREET_ADDRESS , length: 255 )
• STATUS ( type: esriFieldTypeString , alias: STATUS , length: 255 )
• LATITUDE ( type: esriFieldTypeDouble , alias: LATITUDE )
• LONGITUDE ( type: esriFieldTypeDouble , alias: LONGITUDE )
• LONLATCONCAT ( type: esriFieldTypeString , alias: LONLATCONCAT , length: 50 )
• SHAPE ( type: esriFieldTypeGeometry , alias: SHAPE )

Supported Operations:   Query   Generate Renderer   Return Updates