Web traffic statistics for the several City-Parish websites, brla.gov, city.brla.gov, Red Stick Ready, GIS, Open Data etc. Information provided by Google Analytics.

Experience the power of Serpstat's Website Data API, offering comprehensive insights into key SEO metrics, organic traffic estimation, and semantical structure analysis. With our API, unlock valuable data to identify top-performing industry players, analyze competitor strategies, and optimize content for maximum impact.

Unveil essential SEO metrics such as website visibility, organic traffic estimation, and keywords that websites rank for organically. Additionally, gain insights into keywords that websites are shown in Google Ads, providing valuable intelligence for ad targeting and optimization.

Utilize our API to uncover top-performing content in any industry, enabling you to identify trends, understand user intent, and refine your content strategy accordingly.

Benefit from the most cost-effective API solution, starting at just $120 per million rows. Tailor your queries to extract the most relevant data for your specific use-cases, ensuring that you're equipped with the insights necessary to thrive in today's competitive digital landscape.

In 2023, most of the global website traffic was still generated by humans but bot traffic is constantly growing. Fraudulent traffic through bad bot actors accounted for 32 percent of global web traffic in the most recently measured period, representing an increase of 1.8 percent from the previous year. Sophistication of Bad Bots on the rise The complexity of malicious bot activity has dramatically increased in recent years. Advanced bad bots have doubled in prevalence over the past two years, indicating a surge in the sophistication of cyber threats. Simultaneously, simple bad bots saw a 6 percent increase compared to the previous year, suggesting a shift in the landscape of automated threats. Meanwhile, areas like entertainment, and law & government face the highest amount of advanced bad bots, with more than 78 percent of their bot traffic affected by evasive applications. Good and bad bots across industries The impact of bot traffic varies across different sectors. Bad bots accounted for over 57.2 percent of the gaming segment's web traffic. Meanwhile, almost half of the online traffic for telecom and ISPs was moved by malicious applications. However, not all bot traffic is considered bad. Some of these applications help index websites for search engines or monitor website performance, assisting users throughout their online search. Therefore, areas like entertainment, food and groceries, and financial services experienced notable levels of good bot traffic, demonstrating the diverse applications of benign automated systems across different sectors.

Mobile accounts for approximately half of web traffic worldwide. In the last quarter of 2024, mobile devices (excluding tablets) generated 62.54 percent of global website traffic. Mobiles and smartphones consistently hoovered around the 50 percent mark since the beginning of 2017, before surpassing it in 2020. Mobile traffic Due to low infrastructure and financial restraints, many emerging digital markets skipped the desktop internet phase entirely and moved straight onto mobile internet via smartphone and tablet devices. India is a prime example of a market with a significant mobile-first online population. Other countries with a significant share of mobile internet traffic include Nigeria, Ghana and Kenya. In most African markets, mobile accounts for more than half of the web traffic. By contrast, mobile only makes up around 45.49 percent of online traffic in the United States. Mobile usage The most popular mobile internet activities worldwide include watching movies or videos online, e-mail usage and accessing social media. Apps are a very popular way to watch video on the go and the most-downloaded entertainment apps in the Apple App Store are Netflix, Tencent Video and Amazon Prime Video.

Please refer to the original data article for further data description: Jan Luxemburk et al. CESNET-QUIC22: A large one-month QUIC network traffic dataset from backbone lines, Data in Brief, 2023, 108888, ISSN 2352-3409, https://doi.org/10.1016/j.dib.2023.108888. We recommend using the CESNET DataZoo python library, which facilitates the work with large network traffic datasets. More information about the DataZoo project can be found in the GitHub repository https://github.com/CESNET/cesnet-datazoo. The QUIC (Quick UDP Internet Connection) protocol has the potential to replace TLS over TCP, which is the standard choice for reliable and secure Internet communication. Due to its design that makes the inspection of QUIC handshakes challenging and its usage in HTTP/3, there is an increasing demand for research in QUIC traffic analysis. This dataset contains one month of QUIC traffic collected in an ISP backbone network, which connects 500 large institutions and serves around half a million people. The data are delivered as enriched flows that can be useful for various network monitoring tasks. The provided server names and packet-level information allow research in the encrypted traffic classification area. Moreover, included QUIC versions and user agents (smartphone, web browser, and operating system identifiers) provide information for large-scale QUIC deployment studies. Data capture The data was captured in the flow monitoring infrastructure of the CESNET2 network. The capturing was done for four weeks between 31.10.2022 and 27.11.2022. The following list provides per-week flow count, capture period, and uncompressed size:

W-2022-44

Uncompressed Size: 19 GB Capture Period: 31.10.2022 - 6.11.2022 Number of flows: 32.6M W-2022-45

Uncompressed Size: 25 GB Capture Period: 7.11.2022 - 13.11.2022 Number of flows: 42.6M W-2022-46

Uncompressed Size: 20 GB Capture Period: 14.11.2022 - 20.11.2022 Number of flows: 33.7M W-2022-47

Uncompressed Size: 25 GB Capture Period: 21.11.2022 - 27.11.2022 Number of flows: 44.1M CESNET-QUIC22

Uncompressed Size: 89 GB Capture Period: 31.10.2022 - 27.11.2022 Number of flows: 153M

Data description The dataset consists of network flows describing encrypted QUIC communications. Flows were created using ipfixprobe flow exporter and are extended with packet metadata sequences, packet histograms, and with fields extracted from the QUIC Initial Packet, which is the first packet of the QUIC connection handshake. The extracted handshake fields are the Server Name Indication (SNI) domain, the used version of the QUIC protocol, and the user agent string that is available in a subset of QUIC communications. Packet Sequences Flows in the dataset are extended with sequences of packet sizes, directions, and inter-packet times. For the packet sizes, we consider payload size after transport headers (UDP headers for the QUIC case). Packet directions are encoded as ±1, +1 meaning a packet sent from client to server, and -1 a packet from server to client. Inter-packet times depend on the location of communicating hosts, their distance, and on the network conditions on the path. However, it is still possible to extract relevant information that correlates with user interactions and, for example, with the time required for an API/server/database to process the received data and generate the response to be sent in the next packet. Packet metadata sequences have a length of 30, which is the default setting of the used flow exporter. We also derive three fields from each packet sequence: its length, time duration, and the number of roundtrips. The roundtrips are counted as the number of changes in the communication direction (from packet directions data); in other words, each client request and server response pair counts as one roundtrip. Flow statistics Flows also include standard flow statistics, which represent aggregated information about the entire bidirectional flow. The fields are: the number of transmitted bytes and packets in both directions, the duration of flow, and packet histograms. Packet histograms include binned counts of packet sizes and inter-packet times of the entire flow in both directions (more information in the PHISTS plugin documentation There are eight bins with a logarithmic scale; the intervals are 0-15, 16-31, 32-63, 64-127, 128-255, 256-511, 512-1024, >1024 [ms or B]. The units are milliseconds for inter-packet times and bytes for packet sizes. Moreover, each flow has its end reason - either it was idle, reached the active timeout, or ended due to other reasons. This corresponds with the official IANA IPFIX-specified values. The FLOW_ENDREASON_OTHER field represents the forced end and lack of resources reasons. The end of flow detected reason is not considered because it is not relevant for UDP connections. Dataset structure The dataset flows are delivered in compressed CSV files. CSV files contain one flow per row; data columns are summarized in the provided list below. For each flow data file, there is a JSON file with the number of saved and seen (before sampling) flows per service and total counts of all received (observed on the CESNET2 network), service (belonging to one of the dataset's services), and saved (provided in the dataset) flows. There is also the stats-week.json file aggregating flow counts of a whole week and the stats-dataset.json file aggregating flow counts for the entire dataset. Flow counts before sampling can be used to compute sampling ratios of individual services and to resample the dataset back to the original service distribution. Moreover, various dataset statistics, such as feature distributions and value counts of QUIC versions and user agents, are provided in the dataset-statistics folder. The mapping between services and service providers is provided in the servicemap.csv file, which also includes SNI domains used for ground truth labeling. The following list describes flow data fields in CSV files:

ID: Unique identifier SRC_IP: Source IP address DST_IP: Destination IP address DST_ASN: Destination Autonomous System number SRC_PORT: Source port DST_PORT: Destination port PROTOCOL: Transport protocol QUIC_VERSION QUIC: protocol version QUIC_SNI: Server Name Indication domain QUIC_USER_AGENT: User agent string, if available in the QUIC Initial Packet TIME_FIRST: Timestamp of the first packet in format YYYY-MM-DDTHH-MM-SS.ffffff TIME_LAST: Timestamp of the last packet in format YYYY-MM-DDTHH-MM-SS.ffffff DURATION: Duration of the flow in seconds BYTES: Number of transmitted bytes from client to server BYTES_REV: Number of transmitted bytes from server to client PACKETS: Number of packets transmitted from client to server PACKETS_REV: Number of packets transmitted from server to client PPI: Packet metadata sequence in the format: [[inter-packet times], [packet directions], [packet sizes]] PPI_LEN: Number of packets in the PPI sequence PPI_DURATION: Duration of the PPI sequence in seconds PPI_ROUNDTRIPS: Number of roundtrips in the PPI sequence PHIST_SRC_SIZES: Histogram of packet sizes from client to server PHIST_DST_SIZES: Histogram of packet sizes from server to client PHIST_SRC_IPT: Histogram of inter-packet times from client to server PHIST_DST_IPT: Histogram of inter-packet times from server to client APP: Web service label CATEGORY: Service category FLOW_ENDREASON_IDLE: Flow was terminated because it was idle FLOW_ENDREASON_ACTIVE: Flow was terminated because it reached the active timeout FLOW_ENDREASON_OTHER: Flow was terminated for other reasons

Link to other CESNET datasets

https://www.liberouter.org/technology-v2/tools-services-datasets/datasets/ https://github.com/CESNET/cesnet-datazoo Please cite the original data article:

@article{CESNETQUIC22, author = {Jan Luxemburk and Karel Hynek and Tomáš Čejka and Andrej Lukačovič and Pavel Šiška}, title = {CESNET-QUIC22: a large one-month QUIC network traffic dataset from backbone lines}, journal = {Data in Brief}, pages = {108888}, year = {2023}, issn = {2352-3409}, doi = {https://doi.org/10.1016/j.dib.2023.108888}, url = {https://www.sciencedirect.com/science/article/pii/S2352340923000069} }

The global website analytics market, encompassing solutions for large enterprises and SMEs, is poised for significant growth. While the provided data lacks specific market size and CAGR figures, a reasonable estimation based on industry trends suggests a 2025 market size of approximately $15 billion, experiencing a compound annual growth rate (CAGR) of 12% from 2025 to 2033. This robust growth is fueled by several key drivers: the increasing reliance on data-driven decision-making across businesses, the escalating need for enhanced website performance optimization, and the growing adoption of sophisticated analytics tools offering deeper insights into user behavior and conversion rates. Market segmentation reveals strong demand across diverse analytics types, including product, traffic, and sales analytics. The competitive landscape is intensely dynamic, with established players like Google, SEMrush, and SimilarWeb vying for market share alongside emerging innovative companies like Owletter and TrendSource. These companies are constantly innovating to provide more comprehensive and user-friendly analytics platforms, leading to increased competition. This competitive pressure fosters innovation, but also necessitates strategic differentiation, focusing on specific niche markets or offering unique features to attract and retain customers. The market’s geographic distribution shows significant traction in North America and Europe, but emerging markets in Asia Pacific are also exhibiting substantial growth potential, driven by increasing internet penetration and digital transformation initiatives. While data security concerns and the complexity of implementing analytics tools present some restraints, the overall market outlook remains highly positive, promising considerable opportunities for market participants in the coming years.

Traffic count data downloaded from GDOT public map here: https://gdottrafficdata.drakewell.com/publicmultinodemap.aspRetrieved Annual Statistics Reports: "All Station AADT and Truck Percent Statistics." Mapped by Lat/Long field.Retrieved and rehosted for staff use and overlay on city maps on 12/14/2018."The Georgia Department of Transportation’s Traffic Analysis and Data Application (TADA!) website presents data collected from the Georgia Traffic Monitoring Program located on the public roads in Georgia. The Website uses a dynamic mapping interface to allow the User to access data from the map as well as in a variety of report, graph, and data export formats."

Click is global web traffic data combined with transaction data to enhance signal capabilities. Click adds a layer to your analysis for richer spending behavior on consumer & B2B websites, addressable market overview, trends and shopping behavior shifts, and effects of pricing on growth.

Context

The Google Merchandise Store sells Google branded merchandise. The data is typical of what you would see for an ecommerce website.

Content

The sample dataset contains Google Analytics 360 data from the Google Merchandise Store, a real ecommerce store. The Google Merchandise Store sells Google branded merchandise. The data is typical of what you would see for an ecommerce website. It includes the following kinds of information:

Traffic source data: information about where website visitors originate. This includes data about organic traffic, paid search traffic, display traffic, etc. Content data: information about the behavior of users on the site. This includes the URLs of pages that visitors look at, how they interact with content, etc. Transactional data: information about the transactions that occur on the Google Merchandise Store website.

Fork this kernel to get started.

Acknowledgements

Data from: https://bigquery.cloud.google.com/table/bigquery-public-data:google_analytics_sample.ga_sessions_20170801

Banner Photo by Edho Pratama from Unsplash.

Inspiration

What is the total number of transactions generated per device browser in July 2017?

The real bounce rate is defined as the percentage of visits with a single pageview. What was the real bounce rate per traffic source?

What was the average number of product pageviews for users who made a purchase in July 2017?

What was the average number of product pageviews for users who did not make a purchase in July 2017?

What was the average total transactions per user that made a purchase in July 2017?

What is the average amount of money spent per session in July 2017?

What is the sequence of pages viewed?

Competitive Analysis of Industry Rivals The market for competitive analysis is expected to grow significantly over the forecast period, driven by increasing need for businesses to understand their competitive landscape. Key players in the market include BuiltWith, WooRank, SEMrush, Google, SpyFu, Owletter, SimilarWeb, Moz, SunTec Data, and TrendSource. These companies offer a range of services to help businesses track their competitors' online performance, including website traffic, social media engagement, and search engine rankings. Some of the key trends driving the growth of the market include the increasing adoption of digital marketing by businesses, the growing importance of social media, and the increasing availability of data and analytics tools. The market is segmented by type, application, and region. In terms of type, the market is divided into product analysis, traffic analytics, sales analytics, and others. In terms of application, the market is divided into SMEs and large enterprises. In terms of region, the market is divided into North America, South America, Europe, Middle East & Africa, and Asia Pacific. The North American region is expected to dominate the market during the forecast period, due to the presence of a large number of established players in the market. The Asia Pacific region is expected to grow at the highest CAGR during the forecast period, due to the increasing adoption of digital marketing by businesses in the region. This report provides a comprehensive analysis of the industry rivals, encompassing their concentration, product insights, regional trends, and key industry developments.

The Travel Monitoring Analysis System (TMAS) - Volume dataset was compiled on December 31, 2023 and was published on July 16, 2024 from the Federal Highway Administration (FHWA), and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The TMAS data included in this table have been collected by the FHWA from State DOTs through (temporal data representing each time period) permanent count data. DOTs determine what volume data is reported for any given month or day within the month. Each record in the volume data for the reported site, direction or lane is for the given day of record (it contains all 24 hours of data). The attributes are used by FHWA for its Travel Monitoring Analysis System and external agencies and have been intentionally limited to location referencing attributes since the core station description attribute data are contained within TMAS. The attributes in the Volume data correspond with the Volume file format found in Chapter 6 of the 2001 Traffic Monitoring Guide (https://doi.org/10.21949/1519109).

Desktop and mobile website traffic data showed that Germany domain of Zalando had by far the highest number of visitors compared to all other European countries. Between July 2023 and December 2023, zalando.de recorded more nearly 203 million visits. The Polish web domain followed in the ranking, as the total visits amounted to 99.2 million.

This map contains a dynamic traffic map service with capabilities for visualizing traffic speeds relative to free-flow speeds as well as traffic incidents which can be visualized and identified. The traffic data is updated every five minutes. Traffic speeds are displayed as a percentage of free-flow speeds, which is frequently the speed limit or how fast cars tend to travel when unencumbered by other vehicles. The streets are color coded as follows:Green (fast): 85 - 100% of free flow speedsYellow (moderate): 65 - 85%Orange (slow); 45 - 65%Red (stop and go): 0 - 45%Esri's historical, live, and predictive traffic feeds come directly from TomTom (www.tomtom.com). Historical traffic is based on the average of observed speeds over the past year. The live and predictive traffic data is updated every five minutes through traffic feeds. The color coded traffic map layer can be used to represent relative traffic speeds; this is a common type of a map for online services and is used to provide context for routing, navigation and field operations. The traffic map layer contains two sublayers: Traffic and Live Traffic. The Traffic sublayer (shown by default) leverages historical, live and predictive traffic data; while the Live Traffic sublayer is calculated from just the live and predictive traffic data only. A color coded traffic map can be requested for the current time and any time in the future. A map for a future request might be used for planning purposes. The map also includes dynamic traffic incidents showing the location of accidents, construction, closures and other issues that could potentially impact the flow of traffic. Traffic incidents are commonly used to provide context for routing, navigation and field operations. Incidents are not features; they cannot be exported and stored for later use or additional analysis. The service works globally and can be used to visualize traffic speeds and incidents in many countries. Check the service coverage web map to determine availability in your area of interest. In the coverage map, the countries color coded in dark green support visualizing live traffic. The support for traffic incidents can be determined by identifying a country. For detailed information on this service, including a data coverage map, visit the directions and routing documentation and ArcGIS Help.

We have used the Internet environment: 01 Switch, 01 IP camera, 01 server for monitoring, 01 server for honeypot and no firewall. This environment is directly connected to the Internet. We installed a server, functioning as a Monitoring Environment. The network traffic was obtained via Port Mirroring on the switch to the Monitoring Environment server.

We added 08 virtual machines and performed the following test with a denial of service DoS attack:

01 virtual machine from 04:00 pm to 23:55 pm on 2019-12-04 with an interval every 01 hour; 02 virtual machines from 23:55 am on 2019-12-04 to 08:50 am on 2019-12-05 with an interval every 01 hour; 04 virtual machines as of 08:55 am on 2019-12-05 to 05:25 pm on 2019-12-06 with an interval every 5 minutes; 08 virtual machines from 05:30 pm on 2019-12-06 to 23:59 on 2019-12-06 with an interval every 5 minutes; End of tests with shutdown of virtual machines at 23:59 on 2019-12-06.

The results were obtained from Suricata and Telegraf collections from the TICK stack. All evidence was performed by queries via EveBox, which received data from Suricata, Grafana or graphics with information extracted from the InfluxDB (Grafana) and PostgreSQL (EveBox) databases.

events.csv.gz - Suricata / Evebox collections

net.csv.gz - Telegraf collections from the TICK stack

netstat.csv.gz - Telegraf collections from the TICK stack

For correlation purposes, use the events.csv.gz file as a basis. The key to correlation is the 'timestamp' column events.csv.gz with the 'time' column in the net.csv.gz and netstat.csv.gz files.

The interval between collections, non-consecutive, was from 2019-12-04 to 2019-12-06

Google.com recorded an average monthly traffic of 4.79 billion visits in Japan from September to November 2024, which made it the most visited website. It was followed by Yahoo.co.jp and Youtube.com.

DataForSEO Labs API offers three powerful keyword research algorithms and historical keyword data:

• Related Keywords from the “searches related to” element of Google SERP. • Keyword Suggestions that match the specified seed keyword with additional words before, after, or within the seed key phrase. • Keyword Ideas that fall into the same category as specified seed keywords. • Historical Search Volume with current cost-per-click, and competition values.

Based on in-market categories of Google Ads, you can get keyword ideas from the relevant Categories For Domain and discover relevant Keywords For Categories. You can also obtain Top Google Searches with AdWords and Bing Ads metrics, product categories, and Google SERP data.

You will find well-rounded ways to scout the competitors:

• Domain Whois Overview with ranking and traffic info from organic and paid search. • Ranked Keywords that any domain or URL has positions for in SERP. • SERP Competitors and the rankings they hold for the keywords you specify. • Competitors Domain with a full overview of its rankings and traffic from organic and paid search. • Domain Intersection keywords for which both specified domains rank within the same SERPs. • Subdomains for the target domain you specify along with the ranking distribution across organic and paid search. • Relevant Pages of the specified domain with rankings and traffic data. • Domain Rank Overview with ranking and traffic data from organic and paid search. • Historical Rank Overview with historical data on rankings and traffic of the specified domain from organic and paid search. • Page Intersection keywords for which the specified pages rank within the same SERP.

All DataForSEO Labs API endpoints function in the Live mode. This means you will be provided with the results in response right after sending the necessary parameters with a POST request.

The limit is 2000 API calls per minute, however, you can contact our support team if your project requires higher rates.

We offer well-rounded API documentation, GUI for API usage control, comprehensive client libraries for different programming languages, free sandbox API testing, ad hoc integration, and deployment support.

We have a pay-as-you-go pricing model. You simply add funds to your account and use them to get data. The account balance doesn't expire.

In October 2024, totalwine.com had a bounce rate of 47.3 percent to its website, while nakedwines.com registered a bounce rate of 38.75 percent that month. Bounce rate is a marketing term used in web traffic analysis reflecting the percentage of visitors who enter the site and then leave without taking any further action like making a purchase or viewing other pages within the website ("bounce").

The Annual Average Daily Traffic (AADT) for sections of roads for all vehicle types, including single and combination trucks, reported in the 2023 Highway Performance Monitoring System (HPMS) federal report.Annual Average Daily Traffic (AADT) is used to represent vehicle traffic on a typical day of the year and is important for planning purposes, such as defining the federal functional classification of a roadway. The values are calculated using data collected from traffic counter devices, such as Automatic Traffic Recorders (ATR), Weigh In Motion (WIM) devices, and short term counters using tubes. All available traffic data collected throughout the year are then summed and divided by 365 to calculate the annual average daily traffic.Single unit trucks are any trucks that meets the requirements established for the FHWA Truck Classification Method for Categories 4 through 7. Combination unit trucks are any trucks that meets the requirements established for the FHWA Truck Classification Method for Categories 8 through 13. Refer to the Federal Highway Administration website for more information about truck classifications.Reported Extent: State Highway System (i.e. all ADOT-owned roads), National Highway System (NHS), and all federal aid-eligible roads. Federal aid-eligible roads include urban roads classified as minor collectors or above (functional system 1-6) and rural roads classified as major collectors or above (function system 1-5). Roads where ATRs are available, counts are updated annually. For roads where short term counters must be used, traffic counts are collected every three years for all National Highway System (NHS) roads as well as interstates (functional system 1), principal arterials (functional systems 2-3), and sample panel sections. All other federal aid-eligible roads, including minor arterials and collectors, are collected every six years.For undivided highways, which do not have a physical barrier between the two directions of traffic, values are reported as the sum total for both directions of travel. On divided highways, AADT is reported separately on the cardinal and non-cardinal directions of the roadway. Note, the cardinal direction refers to the direction of increasing mileposts.

You can also access an API version of this dataset.

TMS

(traffic monitoring system) daily-updated traffic counts API

Important note: due to the size of this dataset, you won't be able to open it fully in Excel. Use notepad / R / any software package which can open more than a million rows.

Data reuse caveats: as per license.

Data quality

statement: please read the accompanying user manual, explaining:

how

 this data is collected identification 

 of count stations traffic 

 monitoring technology monitoring 

 hierarchy and conventions typical 

 survey specification data 

 calculation TMS 

 operation. 

Traffic

monitoring for state highways: user manual

[PDF 465 KB]

The data is at daily granularity. However, the actual update

frequency of the data depends on the contract the site falls within. For telemetry

sites it's once a week on a Wednesday. Some regional sites are fortnightly, and

some monthly or quarterly. Some are only 4 weeks a year, with timing depending

on contractors’ programme of work.

Data quality caveats: you must use this data in

conjunction with the user manual and the following caveats.

The

 road sensors used in data collection are subject to both technical errors and 

 environmental interference.Data 

 is compiled from a variety of sources. Accuracy may vary and the data 

 should only be used as a guide.As 

 not all road sections are monitored, a direct calculation of Vehicle 

 Kilometres Travelled (VKT) for a region is not possible.Data 

 is sourced from Waka Kotahi New Zealand Transport Agency TMS data.For 

 sites that use dual loops classification is by length. Vehicles with a length of less than 5.5m are 

 classed as light vehicles. Vehicles over 11m long are classed as heavy 

 vehicles. Vehicles between 5.5 and 11m are split 50:50 into light and 

 heavy.In September 2022, the National Telemetry contract was handed to a new contractor. During the handover process, due to some missing documents and aged technology, 40 of the 96 national telemetry traffic count sites went offline. Current contractor has continued to upload data from all active sites and have gradually worked to bring most offline sites back online. Please note and account for possible gaps in data from National Telemetry Sites. 

The NZTA Vehicle

Classification Relationships diagram below shows the length classification (typically dual loops) and axle classification (typically pneumatic tube counts),

and how these map to the Monetised benefits and costs manual, table A37,

page 254.

Monetised benefits and costs manual [PDF 9 MB]

For the full TMS

classification schema see Appendix A of the traffic counting manual vehicle

classification scheme (NZTA 2011), below.

Traffic monitoring for state highways: user manual [PDF 465 KB]

State highway traffic monitoring (map)

State highway traffic monitoring sites

Streaming is by far the predominant type of traffic in communication networks. With thispublic dataset, we provide 1,081 hours of time-synchronous video measurements at network, transport, and application layer with the native YouTube streaming client on mobile devices. The dataset includes 80 network scenarios with 171 different individual bandwidth settings measured in 5,181 runs with limited bandwidth, 1,939 runs with emulated 3G/4G traces, and 4,022 runs with pre-defined bandwidth changes. This corresponds to 332GB video payload. We present the most relevant quality indicators for scientific use, i.e., initial playback delay, streaming video quality, adaptive video quality changes, video rebuffering events, and streaming phases.