Defining and matching segments
First Claim
1. A method, comprising:
- receiving a user submitted definition of a first segment via a user interface input, wherein a recorded effort comprises the first segment and one or more of the following;
heart rate, speed, time, and power, wherein the first segment comprises a portion of a set of Geographic Positioning System (GPS) data associated with the recorded effort, and wherein the first segment is defined based at least in part on a user selected segment start point and a user selected segment end point based on the set of GPS data associated with the recorded effort;
storing the first segment in a segments database;
determining that the first segment is redundant with respect to a second segment stored in the segments database, wherein the second segment comprises a portion of a set of GPS data associated with a different recorded effort, and wherein determining that the first segment is redundant with respect to the second segment comprises determining that the user submitted definition of the first segment at least partially overlaps with a user submitted definition of the second segment; and
in response to the determination that the first segment is redundant with respect to the second segment;
discarding the second segment from the segments database;
maintaining the first segment in the segments database associating a set of GPS data to a matching effort; and
determining the matching effort by matching a set of GPS data associated with the matching effort to the first segment, wherein determining the matching effort comprises matching the set of GPS data associated with the matching effort to the first segment using a first threshold of match for a loose match or a second threshold of match for a tight match, and wherein the tight match comprises determining that the matching effort crossed a start line and a finish line.
0 Assignments
0 Petitions
Accused Products
Abstract
Defining and matching segments is disclosed. In some embodiments, defining and matching segments includes receiving a user defined segment via a user interface input; and determining a matching effort (e.g., which can include a set of Geographic Positioning System (GPS) data) to the segment using a processor. In some embodiments, the data associated with the effort includes one or more of the following: heart rate, speed, time, and power. In some embodiments, defining and matching segments further includes storing data associated with the matching effort with the segment. In some embodiments, the user defined segment is based at least in part in uploaded GPS data. In some embodiments, the user defined segment is based at least in part on selected points on a map application.
-
Citations
19 Claims
-
1. A method, comprising:
-
receiving a user submitted definition of a first segment via a user interface input, wherein a recorded effort comprises the first segment and one or more of the following;
heart rate, speed, time, and power, wherein the first segment comprises a portion of a set of Geographic Positioning System (GPS) data associated with the recorded effort, and wherein the first segment is defined based at least in part on a user selected segment start point and a user selected segment end point based on the set of GPS data associated with the recorded effort;storing the first segment in a segments database; determining that the first segment is redundant with respect to a second segment stored in the segments database, wherein the second segment comprises a portion of a set of GPS data associated with a different recorded effort, and wherein determining that the first segment is redundant with respect to the second segment comprises determining that the user submitted definition of the first segment at least partially overlaps with a user submitted definition of the second segment; and in response to the determination that the first segment is redundant with respect to the second segment; discarding the second segment from the segments database; maintaining the first segment in the segments database associating a set of GPS data to a matching effort; and determining the matching effort by matching a set of GPS data associated with the matching effort to the first segment, wherein determining the matching effort comprises matching the set of GPS data associated with the matching effort to the first segment using a first threshold of match for a loose match or a second threshold of match for a tight match, and wherein the tight match comprises determining that the matching effort crossed a start line and a finish line. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15)
-
-
16. A system, comprising:
-
a processor configured to; receive a user submitted definition of a first segment via a user interface input, wherein a recorded effort comprises the first segment and one or more of the following;
heart rate, speed, time, and power, wherein the first segment comprises a portion of a set of Geographic Positioning System (GPS) data associated with the recorded effort, and wherein the first segment is defined based at least in part on a user selected segment start point and a user selected segment end point based on the set of GPS data associated with the recorded effort;store the first segment in a segments database; determine that the first segment is redundant with respect to a second segment stored in the segments database, wherein the second segment comprises a portion of a set of GPS data associated with a different recorded effort, and wherein to determine that the first segment is redundant with respect to the second segment comprises to determine that the user submitted definition of the first segment at least partially overlaps with a user submitted definition of the second segment; and in response to the determination that the first segment is redundant with respect to the second segment; discard the second segment from the segments database; maintain the first segment in the segments database associating a set of GPS data to a matching effort; and determine the matching effort by matching a set of GPS data associated with the matching effort to the first segment, wherein determining the matching effort comprises matching the set of GPS data associated with the matching effort to the first segment using a first threshold of match for a loose match or a second threshold of match for a tight match, and wherein the tight match comprises determining that the matching effort crossed a start line and a finish line; and a memory coupled to the processor, wherein the memory is configured to provide the processor with instructions. - View Dependent Claims (17, 18)
-
-
19. A computer program product, the computer program product being embodied in a non-transitory computer readable medium and comprising computer instructions for:
-
receiving a user submitted definition of a first segment via a user interface input, wherein a recorded effort comprises the first segment and one or more of the following;
heart rate, speed, time, and power, wherein the first segment comprises a portion of a set of Geographic Positioning System (GPS) data associated with the recorded effort, and wherein the first segment is defined based at least in part on a user selected segment start point and a user selected segment end point based on the set of GPS data associated with the recorded effort;storing the first segment in a segments database; determining that the first segment is redundant with respect to a second segment stored in the segments database, wherein the second segment comprises a portion of a set of GPS data associated with a different recorded effort, and wherein determining that the first segment is redundant with respect to the second segment comprises determining that the user submitted definition of the first segment at least partially overlaps with a user submitted definition of the second segment; and in response to the determination that the first segment is redundant with respect to the second segment; discarding the second segment from the segments database; maintaining the first segment in the segments database associating a set of GPS data to a matching effort; and determining the matching effort by matching a set of GPS data associated with the matching effort to the first segment, wherein determining the matching effort comprises matching the set of GPS data associated with the matching effort to the first segment using a first threshold of match for a loose match or a second threshold of match for a tight match, and wherein the tight match comprises determining that the matching effort crossed a start line and a finish line.
-
Specification