Geohash-related location predictions
US-9769616-B1 · Sep 19, 2017 · US
US11699100B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11699100-B2 |
| Application number | US-202117381290-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 21, 2021 |
| Priority date | Apr 4, 2019 |
| Publication date | Jul 11, 2023 |
| Grant date | Jul 11, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Disclosed are systems and methods relating to providing intersection metrics based on road network data and telematic data.
Opening claim text (preview).
What is claimed is: 1. A traffic analytics system comprising a first datastore and a processing resource, the traffic analytics system configured for: providing first road network data indicating a first plurality of road network subzones defining a geographic area occupied by a road network, the road network including a plurality of intersections; processing the first road network data for labelling each road network subzone as one of a core subzone and a non-core subzone for forming a first plurality of core subzones and a first plurality of non-core subzones and storing an indication thereof in the first road network data; mapping each of the first plurality of core subzones to an intersection of the plurality of intersections of the road network and storing an indication thereof in the first road network data; forming a plurality of subsets of core subzones of the first plurality of core subzones, each thereof defining a geographic area occupied by an intersection core of an intersection of the plurality of intersections; processing the first road network data for mapping each non-core subzone of the first plurality of non-core subzones to at least one intersection of the plurality of intersections; forming second road network data including the first road network data and an indication of the at least one intersection of the plurality of intersections of the road network to which each non-core subzone of the first plurality of non-core subzones is mapped; forming trip metadata dependent on the second road network data and third vehicle data corresponding to the first plurality of road network subzones; and processing the trip metadata associated with a first intersection of the plurality of intersections for forming traffic metrics data indicative of intersection metrics for the first intersection. 2. The traffic analytics system of claim 1 wherein processing the first road network data for mapping each non-core subzone of the first plurality of non-core subzones to the at least one intersection of the plurality of intersections of the road network includes, for each road network subzone of the first plurality of road network subzones, processing the first road network data for forming point data indicating a point representing a location of the road network subzone, for each intersection of the plurality of intersections, processing point data of a corresponding intersection core and point data of the first plurality of non-core subzones for clustering corresponding points into groups, and for each point of a non-core subzone of the first plurality of non-core subzones grouped in a same group as points of an intersection core, mapping the non-core subzone to a corresponding intersection of the intersection core. 3. The traffic analytics system of claim 2 wherein processing the point data of the corresponding intersection core and the point data of the first plurality of non-core subzones for clustering corresponding points into groups includes, for at least a road network subzone, processing road network data for determining a centre point of the road network subzone. 4. The traffic analytics system of claim 2 wherein processing the point data of the corresponding intersection core and the point data of the first plurality of non-core subzones for clustering corresponding points into groups includes clustering the corresponding points into groups using a spatial clustering algorithm. 5. The traffic analytics system of claim 4 wherein the spatial clustering algorithm includes a density-based spatial clustering of applications with noise spatial clustering algorithm. 6. The traffic analytics system of claim 1 wherein forming the trip metadata dependent on the second road network data and the third vehicle data corresponding to the first plurality of road network subzones includes, for each vehicle of a plurality of vehicles corresponding to the third vehicle data, selecting at least a first subset of temporally consecutive third vehicle data instances indicating the vehicle transitions from a first undrivable state to a second drivable state to a third undrivable state for forming journey data; processing the journey data and road network data for mapping an instance of journey data to a road network subzone of the first plurality of road network subzones based on the instance of journey data corresponding to the road network subzone of the first plurality of road network subzones and storing an indication of a location of the road network subzone, a label of the road network subzone, and intersection mapping of the road network subzone in the journey data; selecting subsets of journey data instances for forming trip data indicative of vehicle trips and mapping the trip data to an intersection of the plurality of intersections of the road network; and processing each trip data instance of the trip data for forming the trip metadata. 7. The traffic analytics system of claim 6 wherein for the plurality of vehicles corresponding to the third vehicle data, selecting at least the first subset of temporally consecutive third vehicle data instances indicating the vehicle transitions from the first undrivable state to the second drivable state to the third undrivable state for forming the journey data, includes, for at least a vehicle, selecting at least a sequence of third vehicle data instances including a third vehicle data instance indicating an ignition status of the vehicle is OFF, immediately followed by a third vehicle data instance indicating the ignition status of the vehicle is ON and the vehicle has a speed greater than 0 kilometers per hour (km/h), immediately followed by one or more third vehicle data instances indicating the ignition status of the vehicle is ON, immediately followed by a third vehicle data instance indicating the ignition status of the vehicle is OFF. 8. The traffic analytics system of claim 6 wherein selecting the subsets of journey data instances for forming the trip data indicative of vehicle trips includes, selecting at least one first sequence of journey data instances from journey data for forming trip data, the at least one first sequence of journey data instances including at least one journey data instance corresponding to a core subzone that is mapped to the first intersection immediately followed by a journey data instance mapped to a second intersection, wherein the second intersection and the first intersection are not the same intersection; and mapping each trip data instance to the first intersection and storing an indication of the mapping therein. 9. The traffic analytics system of claim 6 wherein selecting the subsets of journey data instances for forming the trip data indicative of vehicle trips includes, selecting at least one first sequence of journey data instances from the journey data including at least one journey data instance corresponding to a core subzone that is mapped to the first intersection immediately followed by a journey data instance mapped to a second intersection, wherein the second intersection and the first intersection are not the same intersection; selecting a second sequence of journey data instances including at least a journey data instance corresponding to a non-core subzone mapped to the first intersection immediately preceding the at least one first sequence of journey data instances; forming the trip data based on the first sequence of journey data instances and the second sequence of journey data instances; and mapping each trip data instance to the first intersection and storing an indication of the mapping therein. 10. The traffic analytics system of claim 6 wherein forming the trip metadata includes forming the t
Satellite radio beacon positioning systems transmitting time-stamped messages, e.g. GPS [Global Positioning System], GLONASS [Global Orbiting Navigation Satellite System] or GALILEO · CPC title
Road feature data, e.g. slope data · CPC title
Machine learning · CPC title
Traffic data processing · CPC title
Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.