DNIT Brazil Highway Traffic Scraper avatar

DNIT Brazil Highway Traffic Scraper

Pricing

from $7.50 / 1,000 results

Go to Apify Store
DNIT Brazil Highway Traffic Scraper

DNIT Brazil Highway Traffic Scraper

Scrapes DNIT open-data endpoints for PNCT counting stations, volumetric counts, PNV highway grid, and SNV stretches. Returns each record as a flat row with optional state filter and up to 1,000,000 records per run.

Pricing

from $7.50 / 1,000 results

Rating

0.0

(0)

Developer

ParseForge

ParseForge

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

11 days ago

Last modified

Share

ParseForge

DNIT Brazil Highway Traffic Scraper

Scrape DNIT Brazil highway traffic data from official open-data endpoints, up to a million records per run. Get traffic counting stations, volumetric counts, and the national highway grid in one flat schema. No login or API key. Export to CSV, JSON, Excel, or XML.

DNIT publishes Brazil's highway traffic data as open-data endpoints, but querying them means handling pagination, filters, and raw JSON. This Actor reads those endpoints directly and returns each record as a flat row, ready for analysis. Filter by state (UF) and cap the number of records per run.

Who uses itWhat they scrape DNIT Brazil Highway Traffic for
Transportation plannersWhich highway segments have the highest traffic volumes for capacity planning
Logistics analystsWhere to position distribution centers based on traffic flow patterns
Academic researchersHistorical traffic counts for modeling and forecasting studies
GIS specialistsHighway geometry and station coordinates for mapping and spatial analysis

What it does

This Actor collects DNIT highway traffic records from the PNCT counting stations, PNCT volumetric counts, PNV highway grid, or SNV stretches endpoints, and returns each record as a flat row.

  • 🚦 Traffic counting stations: PNCT postos with location, road, and metadata.
  • πŸ“Š Volumetric counts: PNCT contagem-volumetrica with vehicle counts by class and time.
  • πŸ›£οΈ Highway grid: PNV national highway network with geometry and attributes.
  • πŸ“ Stretches: SNV trechos with segment-level details and state codes.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with DNIT Brazil Highway Traffic data

🚚 Plan logistics routes.

A logistics analyst scrapes PNCT volumetric counts for all stations in SΓ£o Paulo to identify congested corridors and reroute deliveries.

πŸ“ˆ Model traffic trends.

A researcher collects historical volumetric counts from multiple states to build a time-series model of highway usage.

πŸ—ΊοΈ Build highway maps.

A GIS specialist pulls the PNV highway grid to create a base layer for a national road network map.

πŸ—οΈ Prioritize road maintenance.

A transportation planner scrapes SNV stretches with high traffic counts to rank segments for resurfacing projects.

Why choose this scraper

What you get
Official dataDirect from DNIT dados-abertos, no third-party aggregation
Flat schemaEvery record normalized into a consistent row for easy export
State filterLimit results to a specific UF like SP, RJ, or MG
ScalableCollect up to 1,000,000 records in a single run

How it compares

No other Store actor targets DNIT Brazil Highway Traffic the same way, so the honest comparison is with the alternatives teams actually weigh.

DNIT Brazil Highway Traffic ScraperBuild it in-houseBy hand
SetupRun it now, zero configDays of engineeringNone, but hours per pull
When DNIT Brazil Highway Traffic changesMaintained for youYou fix itYou re-learn the page
Proxies, retries, anti-botBuilt inYour problemBrowser only
OutputFixed JSON schema, CSV/Excel exportWhatever you buildCopy-paste
CostPay per resultEngineering timeAnalyst hours

Configure the run

Drive the Actor from the DNIT open-data resource path, optionally filter by state (UF), and set a maximum number of records per run. The Input tab lists every parameter.

A first run with the defaults:

{
"maxItems": 10
}

A larger pull:

{
"maxItems": 200
}

Pricing

Pay-per-result: $0.0085 per result collected. You pay only for the results written to your dataset.

Results collectedApproximate cost
100 results$0.85
1,000 results$8.50
10,000 results$85.00

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

  1. Create a free Apify account with $5 in credit.
  2. Open the DNIT Brazil Highway Traffic Scraper.
  3. Set your inputs and any filters, then click Start.
  4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to DNIT Brazil Highway Traffic through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/dnit-brazil-traffic-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results?

Check that the 'resource' field is set correctly and that the 'region' filter matches a valid UF code. Also ensure 'maxItems' is at least 1. If the problem persists, try a different resource or remove the region filter.

Why is the run slow?

Large requests can take time. Reduce 'maxItems' or add a region filter to limit the number of records. The Actor processes data as it streams, so performance depends on the endpoint response size.

Why are some fields empty?

DNIT endpoints may not provide all fields for every record. Empty fields are returned as null or blank. Check the specific resource documentation for available fields.

Can I get data for a specific highway?

The Actor does not have a direct highway filter, but you can use the 'region' filter to narrow by state and then filter the output by road code in your analysis tool.

FAQ

QuestionAnswer
What DNIT data can I scrape?You can scrape PNCT counting stations, PNCT volumetric counts, the PNV highway grid, and SNV stretches. Each resource returns different fields, all flattened into a single row per record.
Do I need an API key or login?No. The Actor reads DNIT's public open-data endpoints directly. No registration or authentication is required.
How do I filter by state?Use the 'region' input field and enter a UF code like SP, RJ, or MG. The filter is applied as records are read, so only matching rows are returned.
What is the maximum number of records I can get?You can set 'maxItems' up to 1,000,000 records per run. The default is 10, but you can increase it for larger datasets.
What export formats are supported?The Actor outputs data in CSV, JSON, Excel, and XML formats, so you can use it directly in your analysis tools.
Can I scrape data for all of Brazil at once?Yes, leave the 'region' field empty to collect records from all states. Use 'maxItems' to control the total number of records.
How often is the DNIT data updated?The Actor reads live data from DNIT's endpoints each time it runs, so you always get the latest available records.
Is this Actor suitable for large-scale scraping?Yes, it can handle up to 1,000,000 records per run and runs on Apify's infrastructure, so it scales with your needs.
What is the difference between PNCT and PNV?PNCT is the National Traffic Counting Plan, which includes counting stations and volumetric counts. PNV is the National Highway Grid, which contains the road network geometry.
Can I get vehicle classification data?Yes, the PNCT volumetric counts resource includes vehicle counts by class, such as cars, buses, and trucks, depending on the station.

Browse the full ParseForge collection for more scrapers.

πŸ†˜ Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Departamento Nacional de Infraestrutura de Transportes (DNIT). It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.