Layer: Transport sensor countlines (ID: 0)

View In: ArcGIS Online Map Viewer

Name: Transport sensor countlines

Display Field: COUNTLINE_ID

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: <DIV STYLE="text-align:Left;"><DIV><DIV>Access transport sensor count data here:Metadata info - https://gis-snowflake-opendata-public-wcc-arcgis-prod.s3.ap-southeast-2.amazonaws.com/transport_sen…2023 - https://gis-snowflake-opendata-public-wcc-arcgis-prod.s3.ap-southeast-2.amazonaws.com/transport_sen…2024 - https://gis-snowflake-opendata-public-wcc-arcgis-prod.s3.ap-southeast-2.amazonaws.com/transport_sen…2025 - https://gis-snowflake-opendata-public-wcc-arcgis-prod.s3.ap-southeast-2.amazonaws.com/transport_sen…File Listing - https://gis-snowflake-opendata-public-wcc-arcgis-prod.s3.ap-southeast-2.amazonaws.com/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 around the city.Abbreviations/Acronyms:WCC: Wellington City CouncilAPI: Application Programming InterfaceRefresh Rate: The dataset will be refreshed no less than once per calendar month.Data Security : PublicOwnership: Digital Innovation team, WCC. Please contact: digitalinnovation@wcc.govt.nz for questions or feedback about this data.Custodianship: Corporate GIS team, WCC.Stewardship: City Insights team, WCC. Authoritative Data Source (Data only): The primary source of data is from VivaCity Labs, which provides a dashboard and application programming interface (API) for collected data.Outling Limitations of Data:This dataset provides valuable insights into transport activity over time, but there are a few limitations to keep in mind: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.Work is underway to improve how data accuracy is monitored, resolved, and presented on the Open Data Portal.Temporary gaps may appear due to sensor outages or scheduled maintenance.If data for one direction of a countline appears blank, it means that the countline is configured to count in only one direction.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.Sensors vary in installation dates, resulting in different data collection start points.Historic data collected from old or inactive sensors may be excluded from the historic datasets.Data Dictionary:1. Dimension/Look-Up TableCountline Meta Info - 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.Fields:countline_id - A unique identifier for each countline.name - The name of the countline, indicating generic location of countline.latitude_start_line - The latitude coordinate where the countline starts.longitude_start_line - The longitude coordinate where the countline starts.latitude_end_line - The latitude coordinate where the countline ends.longitude_end_line - The longitude coordinate where the countline ends.direction_in - The compass direction of the countline when moving toward the sensor’s view.direction_out - The compass direction of the countline when moving away from the sensor’s view.earliest - The earliest date when the countline was recorded.latest - The latest date when the countline was recorded. An older date may indicate that the countline is inactive or no longer in use.2. Count Dataset - This dataset aggregates mobility data from different countline sources, providing a comprehensive view of traffic flow and directionality.Fields:countline_id - A unique identifier for each countline.countline_transport_class* - Classification of the transport modes, indicating the type of traffic being measured.countline_date - The date when the countline data was recorded.countline_hour - The hour of the day when the countline data was recorded.direction_count - The total count of traffic in a specific direction during the hour.direction - Normalised direction label, indicating the flow of traffic, as follows: N: North NE: North East E: East SE: South East S: South SW: South West W: West NW: North WestCountline transport classes<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

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: 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:

Fields:

OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID, editable: false, nullable: false, defaultValue: null, modelName: OBJECTID )
COUNTLINE_ID ( type: esriFieldTypeInteger, alias: COUNTLINE_ID, editable: true, nullable: true, defaultValue: null, modelName: COUNTLINE_ID )
Shape__Length ( type: esriFieldTypeDouble, alias: Shape.STLength(), editable: false, nullable: false, defaultValue: null, modelName: Shape.STLength() )

Templates:

Name: Transport sensor countlines
Description:
Prototype:
Drawing Tool: esriFeatureEditToolLine

Capabilities: Query,Extract

Sync Can Return Changes: false

Is Data Versioned: false

Supports Rollback On Failure: true

Supports ApplyEdits With Global Ids: false

Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Supported Operations: Query Query Attachments Query Analytic Calculate Validate SQL Generate Renderer Return Updates Iteminfo Thumbnail Metadata