Layer: Transport sensor countlines (ID: 0)

Name: Transport sensor countlines

Display Field: COUNTLINE_ID

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: <DIV STYLE="text-align:Left;"><DIV><DIV>Intended Purpose: This data source is created to provide access to data from transport sensors installed in Wellington City, which measure transport counts and help analyse how people move across the city. Abbreviations/Acronyms:WCC: Wellington City CouncilAPI: Application Programming InterfaceRefresh Rate (Data only): The dataset will be refreshed no less than once per calendar month.Ownership: This data is owned by the WCC’s Smart Council Business Unit. Please contact: digitalinnovation@wcc.govt.nz for questions or feedback about this data source.Stewardship: Data accuracy, completeness, and consistency, metadata documentation (definitions, sources), determining business needs for open data, and identifying and supporting issue resolution is actioned by the WCC’s City Insights Team.Custodianship: Corporate GIS Team, WCC.Authoritative Data Source (Data only): The primary source of data is from VivaCity Labs, which provides a dashboard and API for collected data.Outlining limitations of data: This dataset provides valuable insights into transport activity over time, but there are a few limitations to keep in mind:<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>While sensors are designed to be highly accurate, they may still produce occasional discrepancies due to technical faults, environmental conditions, or other external factors. The data is best used to understand patterns and trends rather than precise counts.</LI><LI>Work is underway to improve how data accuracy is monitored, resolved, and presented on the Open Data Portal.</LI><LI>Temporary gaps may appear due to sensor outages or scheduled maintenance.</LI><LI>If data for one direction of a countline appears blank, it means that the countline is configured to count in only one direction.</LI><LI>In locations where multiple sensors or countlines are close together, a single commuter may be counted more than once as they pass through each countline. Users should refer to the spatial layout provided in this layer to interpret the data accurately.</LI><LI>Sensors vary in installation dates, resulting in different data collection start points.</LI><LI>Historic data collected from old or inactive sensors may be excluded from the historic datasets.</LI><LI>Data dictionary:</LI></UL>1. Dimension/Look-up tableCountline Meta InfoDescription: This model processes and enriches countline metadata by calculating the bearing and direction of lines based on their start and end coordinates. It provides relevant compass directions for each line, which can be used for navigation or spatial analysis. <UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>Columns:<OL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>1. name: countline_id description: A unique identifier for each countline.</LI><LI>2. name: name description: The name of the countline, indicating generic location of countline.</LI><LI>3. name: latitude_start_line description: The latitude coordinate where the countline starts.</LI><LI>4. name: longitude_start_line description: The longitude coordinate where the countline starts.</LI><LI>5. name: latitude_end_line description: The latitude coordinate where the countline ends.6. name: longitude_end_line description: The longitude coordinate where the countline ends. 7. name: direction_in description: The compass direction of the countline when moving in a clockwise direction.</LI><LI> 8. name: direction_out description: The compass direction of the countline when moving in an anticlockwise direction.</LI><LI> 9. name: earliest description: The earliest date when the countline was recorded.</LI><LI> 10. name: latest description: The latest date when the countline was recorded.2. Count datasetDescription: This dataset aggregates mobility data from different countline sources, providing a comprehensive view of traffic flow and directionality.</LI></OL></LI><LI> Columns:</LI></UL>1. name: countline_id<OL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI> description: A unique identifier for each countline.<OL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI> 2. name: countline_transport_class* description: Classification of the transport modes, indicating the type of traffic being measured. </LI></OL></LI><LI> 3. name: countline_date description: The date when the countline data was recorded.</LI><LI> 4. name: countline_hour description: The hour of the day when the countline data was recorded.</LI><LI> 5. name: direction_count description: The total count of traffic in a specific direction during the hour.</LI><LI> 6. name: direction description: Normalized direction label, indicating the flow of traffic, as follows:<OL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI> N: North</LI><LI> NE: North East</LI><LI> E: East</LI><LI> SE: South East</LI><LI> S: South</LI><LI> SW: South West</LI><LI> W: West</LI><LI> NW: North West</LI></OL></LI><LI>Countline transport classes</LI></OL><TABLE><TBODY><TR><TD>Wellington Transport Class</TD><TD>Description</TD></TR><TR><TD>Pedestrian</TD><TD>People on foot</TD></TR><TR><TD>Cyclist</TD><TD>People on any type of bikes</TD></TR><TR><TD>Escooter</TD><TD>Electric scooters</TD></TR><TR><TD>Motorbike</TD><TD>Motorbike</TD></TR><TR><TD>Car</TD><TD>Small passenger vehicles including car, taxi, and emergency car.</TD></TR><TR><TD>LGV</TD><TD>LGV (Light Goods Vehicle) includes van and emergency van.</TD></TR><TR><TD>Bus</TD><TD>All types of buses and minibuses</TD></TR><TR><TD>OGV1</TD><TD>OGV 1 (Ordinary Goods Vehicle 1). Larger vehicles with two or three axles. Includes Rigid and Fire Engine in Wellington context.</TD></TR><TR><TD>OGV2</TD><TD>OGV 2 (Ordinary Goods Vehicle 2). Includes truck in Wellington context.</TD></TR></TBODY></TABLE>Countline Directionality and Data InclusionsCountline data can be recorded in two directions (in and out) to capture movement across a countline location. In certain cases, only one direction is relevant. For example, if a countline is located on a one-way street, only the direction that aligns with traffic flow may be included in the dataset.This directionality inclusion is reflected in the Countline Meta Info columns:<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>direction_in and direction_out indicate the compass direction of movement. </LI><LI>If a direction is excluded, the corresponding column will show no compass direction, signalling that data for that direction is not part of the countline record.</LI></UL>This approach ensures that the dataset accurately represents valid transport movements and avoids misleading counts for irrelevant directions. <OL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI></LI></OL></DIV></DIV></DIV>

Copyright Text: Wellington City Council, Viva City

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

Drawing Info:

Renderer:

Simple Renderer:

Symbol:

Style:

Color:

Width:

Label:

Description:

Transparency:

Labeling Info:

Advanced Query Capabilities:

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
COUNTLINE_ID ( type: esriFieldTypeInteger, alias: COUNTLINE_ID )
Shape ( type: esriFieldTypeGeometry, alias: Shape )
Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )

Supported Operations: Query Query Attachments Query Analytic Generate Renderer Return Updates

Iteminfo Thumbnail Metadata