Screenlines
Screenlines are imaginary lines typically drawn along features such as rivers or railways, which have a minimum number of crossing points, making it more manageable to count traffic going from one side to the other. Symbology is based on the COUNTYEAR_EN field (Both = Count Collection during All Years / Even = Count Collection during Even Years / Odd = Count Collection during Odd Years), which describes when the count takes place.
A screenline (e.g. LN02, LN10) is made up of several stations placed to count east-west or north-south travel, which in total, capture all major travel routes across the imaginary screenline. The screenlines are located along geographical barriers, i.e. rivers, greenbelt – generally where several major transportation facilities are the main flow. To be truly representative of the flow, there is a station at each intersecting road, transit, and bike/walkway path on the screenline.
Date created: June 29, 2026
Update frequency: As required
Accuracy: Not intended to represent exact location on the ground
Attributes:
- SL_NUM (Screenline Number)
- SL_TEXT (Screenline Text ID)
- CORDON_EN (Cordon - screenlines or groups of screenlines that describe an area of interest (English text))
- CORDON_FR (Cordon - screenlines or groups of screenlines that describe an area of interest (French text))
- NAME_EN (Screenline name (English text))
- NAME_FR (Screenline name (French text))
- SEASON_EN (Season that the traffic count was captured (English text))
- SEASON_FR (Season that the traffic count was captured (French text))
- COUNTYEAR_EN ((Both = Count Collection during All Years / Even = Count Collection during Even Years / Odd = Count Collection during
- Odd Years) - describes when the count takes place (English text))
- COUNTYEAR_FR (Les deux = Comptage à chaque année / Paires = Comptage pendant les années paires / Impaires = Comptage pendant les années impaires) - describes when the count takes place (French text))
- CHANGE_EN (English text describing a change to a screenline)
- CHANGE_FR (French text describing a change to a screenline)
- YEAR (Year representing the version of the screenline feature)
- STATUS_EN (Latest – English text describing the data as the most recent captured)
- STATUS_FR (Dernier en date – French text describing the data as the most recent captured)
Author: Transportation Planning
Author email: [email protected]
Maintainer Organization: Geospatial Analytics, Technology and Solutions (GATS), PDBS
Datasets available for download
-
Screenlines / Lignes-écransFeature Layer
Layer 168 via ArcGIS REST API
-
Screenlines / Lignes-écrans (Explore)HTML
Explore Screenlines / Lignes-écrans on ArcGIS Hub
Additional Info
| Field | Value |
|---|---|
| Last Updated | June 30, 2026, 06:52 (UTC) |
| Created | June 30, 2026, 06:52 (UTC) |
|
Domain / Topic
Domain or topic of the dataset being cataloged.
|
|
|
Title
Title for the Dataset.
|
Screenlines |
|
Description
A description of the dataset.
|
Screenlines are imaginary lines typically drawn along features such as rivers or railways, which have a minimum number of crossing points, making it more manageable to count traffic going from one side to the other. Symbology is based on the COUNTYEAR_EN field (Both = Count Collection during All Years / Even = Count Collection during Even Years / Odd = Count Collection during Odd Years), which describes when the count takes place. A screenline (e.g. LN02, LN10) is made up of several stations placed to count east-west or north-south travel, which in total, capture all major travel routes across the imaginary screenline. The screenlines are located along geographical barriers, i.e. rivers, greenbelt – generally where several major transportation facilities are the main flow. To be truly representative of the flow, there is a station at each intersecting road, transit, and bike/walkway path on the screenline. Date created: June 29, 2026
Author: Transportation Planning Maintainer Organization: Geospatial Analytics, Technology and Solutions (GATS), PDBS |
|
Tags / Keywords
Keywords/tags categorizing the dataset.
|
|
|
Format (CSV, XLS, TXT, PDF, etc)
File format of the dataset.
|
|
|
Dataset Size
Dataset size in megabytes.
|
0.06 |
|
Metadata Identifier
Metadata identifier – can be used as the unique identifier for catalogue entry
|
|
|
Published Date
Published date of the dataset.
|
2026-06-29 |
|
Time Period Data Span (start date)
Start date of the data in the dataset.
|
|
|
Time Period Data Span (end date)
End date of time data in the dataset.
|
|
|
GeoSpatial Area Data Span
A spatial region or named place the dataset covers.
|
| Field | Value |
|---|---|
|
Access category
Type of access granted for the dataset (open, closed, service, etc).
|
public |
|
License
License used to access the dataset.
|
https://ottawa.ca/en/city-hall/open-transparent-and-accountable-government/open-data/about-open-data |
|
Limits on use
Limits on use of data.
|
|
|
Location
Location of the dataset.
|
https://od-dev2-ottawa.opendata.arcgis.com/datasets/ottawa::screenlines |
|
Data Service
Data service for accessing a dataset.
|
|
|
Owner
Owner of the dataset.
|
[email protected] |
|
Contact Point
Who to contact regarding access?
|
City of Ottawa |
|
Contact Point Email
The email to contact regarding access?
|
[email protected] |
|
Publisher
Publisher of the dataset.
|
City of Ottawa |
|
Publisher Email
Email of the publisher.
|
|
|
Author
Author of the dataset.
|
[email protected] |
|
Author Email
Email of the author.
|
|
|
Accessed At
Date the data and metadata was accessed.
|
2026-06-29 |
| Field | Value |
|---|---|
|
Identifier
Unique identifier for the dataset.
|
03259cf7caf442d3a236e768eada75fc |
|
Language
Language(s) of the dataset
|
English |
|
Link to dataset description
A URL to an external document describing the dataset.
|
https://od-dev2-ottawa.opendata.arcgis.com/datasets/ottawa::screenlines |
|
Persistent Identifier
Data is identified by a persistent identifier.
|
|
|
Globally Unique Identifier
Data is identified by a persistent and globally unique identifier.
|
|
|
Contains data about individuals
Does the data hold data about individuals?
|
|
|
Contains data about identifiable individuals
Does the data hold identifiable data about individual?
|
|
|
Contains Indigenous Data
Does the data hold data about Indigenous communities?
|
|
|
Portal Type
Platform type of the source portal.
|
| Field | Value |
|---|---|
|
Version
Version of the datatset
|
None |
|
Source
Source of the dataset.
|
None |
|
Version notes
Version notes about the dataset.
|
|
|
Is version of another dataset
Link to dataset that it is a version of.
|
|
|
Other versions
Link to datasets that are versions of it.
|
|
|
Provenance Text
Provenance Text of the data.
|
City of Ottawa |
|
Provenance URL
Provenance URL of the data.
|
|
|
Temporal resolution
Describes how granular the date/time data in the dataset is.
|
|
|
GeoSpatial resolution in meters
Describes how granular (in meters) geospatial data is in the dataset.
|
|
|
GeoSpatial resolution (in regions)
Describes how granular (in regions) geospatial data is in the dataset.
|
| Field | Value |
|---|---|
|
Indigenous Community Permission
Who holds the Indigenous Community Permission. Who to contact regarding access to a dataset that has data about Indigenous communities.
|
|
|
Community Permission
Community permission (who gave permission).
|
|
|
The Indigenous communities the dataset is about
Indigenous communities from which data is derived.
|
| Field | Value |
|---|---|
|
Number of data rows
If tabular dataset, total number of rows.
|
39 |
|
Number of data columns
If tabular dataset, total number of unique columns.
|
38 |
|
Number of data cells
If tabular dataset, total number of cells with data.
|
1482 |
|
Number of data relations
If RDF dataset, total number of triples.
|
|
|
Number of entities
If RDF dataset, total number of entities.
|
|
|
Number of data properties
If RDF dataset, total number of unique properties used by the triples.
|
|
|
Data quality
Describes the quality of the data in the dataset.
|
|
|
Metric for data quality
A metric used to measure the quality of the data, such as missing values or invalid formats.
|
0 Comments