Brian.oco 0 Posting Whiz

On a trip to Newport Beach, Oregon, this past summer, I was introduced to a global positioning satellite device for the first time.

It was a real eye-opener. All I had to do was type in the address I was heading toward, and the satellite took care of the rest. For the two-hour trip, I was gently reminded by the device's "voice -- call it Julie Andrews-like in her "Sound of Music" days, to "turn right in one mile" or "turn left at Juniper Street" . . . and so on and so on until we reached our destination.

Now I'm hooked. I bought my own GPS unit on my return home and, judging from the research I'm seeing, I'm hardly alone. ABI Research says that traffic and driving "location" technologies will reach more than 83 million users worldwide by 2012.

The technology is getting better as the market is growing bigger. ABI sites in a recent report entitled "Traffic Information for Navigation Systems" that the technology's next frontier is a richer variety of location-aware content. According to ABI, the first prominent example of such dynamic content is real-time traffic information, which will be further enhanced by the addition of historical and predictive traffic data to assist drivers in determining the best route.

“When it comes to collecting and distributing useful traffic data,” says research director Mike Ippoliti of ABI Research, “the emphasis is shifting. Reporting of ’incident data’ from accidents, road closures, other emergencies is becoming routine; the next step is predictive and probe-derived data that can deliver information on more complex problems and support re-routing of drivers around traffic problems.”

ABI Research sees three elements to the puzzle of providing truly useful traffic data for navigation systems.

First, the traffic data collection ecosystem is very complex. Infrastructure measurement systems (road sensors, cameras, radar, or loop sensors) are expensive and hard to install. But alternative collection methods such as floating-car data, and potentially cellular movement data, require no roadside installations, and may prove to be the sources of choice for many data collectors.

A second challenge is traffic data aggregation. As the basic data becomes more available, the complex data derived from floating-car probes or predictive modeling will become the differentiator. But such data are harder to integrate into navigation routing.

A third factor is market landscape. ABI Research expects INRIX and NAVTEQ/ to become the two players in traffic data. Other players will largely become marginalized, or will supply INRIX or NAVTEQ/Traffic.com. That said, Ippoliti adds, “INRIX is itself a prime target for acquisition within the next few years. One could speculate on potential buyers, such as a PND maker who was disappointed not to acquire a map data provider, and needs a source of data leverage in the market.”

All in all, a very bullish sentiment from ABI on a rapidly emerging, commercially viable technology. With ongoing improvements in GPS/traffic applications, the road does indeed go on forever.

Dani AI

Generated

called the shift correctly: navigation moved from static maps to live, context-aware routing. That trend has matured into systems that fuse de-identified device telemetry, fleet and infrastructure feeds, and historical models to produce both current congestion maps and predictive ETAs. Modern platforms expose those capabilities to developers so apps can show live delays and recommend better routes. Google on predictive travel times · Mapbox Traffic Data overview. (mapsplatform.googleblog.com)

Quick checklist for teams evaluating traffic data suppliers: update cadence and effective latency (seconds vs minutes), network coverage and link-level granularity, whether the provider supplies historical/predictive baselines, delivery format (tiles, streaming, REST) and map-matching accuracy, and commercial terms (rate limits, licensing). Vendor docs illustrate real differences in cadence and coverage—compare examples like TomTom Traffic APIs and Mapbox Traffic Data when testing. TomTom Traffic APIs · Mapbox Traffic Data. (tomtom.com)

Integration pattern to reduce surprises: ingest raw speed samples into a durable queue, persist time-series samples for short-term analysis, map-match into your road graph (PostGIS or equivalent), compute ETA deltas in a worker pool, and only surface reroutes when the expected ETA improvement justifies driver distraction. Minimal example request (traffic-aware ETA via Google Directions/Routes):

curl "https://maps.googleapis.com/maps/api/directions/json?origin=37.7749,-122.4194&destination=37.3382,-121.8863&departure_time=now&key=YOUR_API_KEY"

See the Routes/Directions docs for request options and traffic models. (developers.google.com)

Privacy and safety notes: precise location is treated as personal data in many jurisdictions—apply minimization, strong anonymization, retention limits, and clear opt-in/opt-out notices to meet rules such as the GDPR and CCPA. Expect more vehicle-to-everything (V2X) feeds as governments push connected-vehicle programs, which will expand data sources and safety use cases. GDPR summary (EUR‑Lex) · CCPA (CA Attorney General) · USDOT V2X deployment plan. (eur-lex.europa.eu)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.