Hi, We are building a reporting pipeline that replicates MyGeotab exception rule durations using the SDK. We have been able to match results for most vehicles, but we are seeing consistent discrepancies on units with sparse logging for rules based on Engine Speed thresholds. **Rule structure:** Status Data Diagnostic "Engine speed" &gt; 1200 RPM AND Status Data Diagnostic "Engine speed" &lt; 1400 RPM **How we currently process the data:** We download StatusData for DiagnosticEngineSpeedId and build a time series. For each consecutive pair of logged points, we calculate the interval duration and distribute that time proportionally across RPM ranges using linear interpolation between the two endpoint values. For large gaps where the device did not transmit, we interpolate between the last known value before the gap and the first value after it, using the full gap duration. Interestingly, reprocessing the same rule via the MyGeotab UI produces the same durations as the original — which suggests the data used for the calculation is persisted on the platform. **Our specific questions:** a) When MyGeotab evaluates an RPM-based exception rule, does it use only the StatusData records available via the SDK, or does it also use an internal higher-resolution data store not exposed through the API? b) Is there a StatusData search parameter, result type, or API endpoint that returns intermediate logged values not returned by a standard fromDate/toDate query? c) For a rule like the one above, does MyGeotab interpolate linearly between consecutive StatusData points to estimate duration within the threshold, or does it only count time when a logged point explicitly falls within the range? d) Are there any other diagnostic IDs, data types, or API calls we should be using to get the full Engine Speed time series that MyGeotab uses internally for exception calculation? Thank you,

RPM Values

I am setting up a rule with the following conditions: Speed &gt; 50 km/h AND Status Data Diagnostic 'Total Time Under Braking' &gt; 5s, but it is not returning any results. What could be causing this? Do I need to enable a specific setting or request access to this data? If so, should I reach out to Geotab Support or my Fleet Administrator? Note: The AI support provided general information about harsh braking (G-forces), but did not clarify the specific use of the 'Total Time Under Braking' diagnostic.

MyGeotab Rule not working as expected

I am currently extracting RPM values using the following logic:Filtering by trips (real driving intervals)Applying a physical filter (removing noise, e.g., values outside 50–4000 RPM)Resampling to 1‑minute intervals to approximate the UI behaviorPerforming a final cleanup of low outliersThis process produces consistent results; however, I have observed that certain values do not fully align with those presented in the MyGeotab interface. The discrepancies are minor but noticeable, with some offsets.My questions are:Does MyGeotab apply any internal filtering, normalization, or aggregation to raw diagnostic data (such as RPM or speed) before presenting it in the interface? If so, could you clarify the process or criteria used?On occasion, I encounter speed values that exceed what would normally be expected under typical driving conditions. I understand that such anomalies could potentially be influenced by temporary GPS signal loss from the GO device. Could you please clarify why these spikes occur and whether signal loss is a typical contributing factor? 

RPM & Speed values

I'm looking for clarification on the MyGeotab API rate limits. I've seen mentions of a 100k daily request limit, but I would like to know: Geotab DevelopersIs this limit fixed per database or per service account?Is there a way to query the system to see my current usage status or remaining 'credits' for the day?I want to make sure my extraction process is optimized and doesn't get throttled. Any guidance or links to specific documentation on tracking this would be great.

API Rate Limits

I'm currently working with the MyGeotab SDK and would like to confirm the feasibility of retrieving two specific data points:Power Usage: Is there a specific Diagnostic or variable (such as Engine Load or Torque) that returns the percentage of power required/utilized during driving? If this isn't available directly, is there a predefined Exception that monitors power peaks?Exception Location: When querying the ExceptionEvenT object, is it possible to get the exact geographic details (street, state, or road segment) directly from the API, or is it mandatory to perform manual Reverse Geocoding using the exception's coordinates?Thanks in advance for the help!

How to get Engine Power Usage and precise Exception Locations via MyGeotab SDK?

page-user page-user-francisco-ramirez-5672 template-account-profile page-status-200 theme-harmony user-guest

Company

Title

Hi, We are building a reporting pipeline that replicates MyGeotab exception rule durations using the SDK. We have been able to match results for most vehicles, but we are seeing consistent discrepancies on units with sparse logging for rules based on Engine Speed thresholds. **Rule structure:** Status Data Diagnostic "Engine speed" &gt; 1200 RPM AND Status Data Diagnostic "Engine speed" &lt; 1400 RPM **How we currently process the data:** We download StatusData for DiagnosticEngineSpeedId and build a time series. For each consecutive pair of logged points, we calculate the interval duration and distribute that time proportionally across RPM ranges using linear interpolation between the two endpoint values. For large gaps where the device did not transmit, we interpolate between the last known value before the gap and the first value after it, using the full gap duration. Interestingly, reprocessing the same rule via the MyGeotab UI produces the same durations as the original — which suggests the data used for the calculation is persisted on the platform. **Our specific questions:** a) When MyGeotab evaluates an RPM-based exception rule, does it use only the StatusData records available via the SDK, or does it also use an internal higher-resolution data store not exposed through the API? b) Is there a StatusData search parameter, result type, or API endpoint that returns intermediate logged values not returned by a standard fromDate/toDate query? c) For a rule like the one above, does MyGeotab interpolate linearly between consecutive StatusData points to estimate duration within the threshold, or does it only count time when a logged point explicitly falls within the range? d) Are there any other diagnostic IDs, data types, or API calls we should be using to get the full Engine Speed time series that MyGeotab uses internally for exception calculation? Thank you,

That's true! You're absolutely right, I hadn't considered that. The idea was for the rule to avoid noise, but I think it would be better to relax the time condition to 1 or 2 seconds. However, if it still doesn't register any events even then, how could I resolve it?

I am setting up a rule with the following conditions: Speed &gt; 50 km/h AND Status Data Diagnostic 'Total Time Under Braking' &gt; 5s, but it is not returning any results. What could be causing this? Do I need to enable a specific setting or request access to this data? If so, should I reach out to Geotab Support or my Fleet Administrator? Note: The AI support provided general information about harsh braking (G-forces), but did not clarify the specific use of the 'Total Time Under Braking' diagnostic.

I am currently extracting RPM values using the following logic:<ul><li>Filtering by trips (real driving intervals)</li><li>Applying a physical filter (removing noise, e.g., values outside 50–4000 RPM)</li><li>Resampling to 1‑minute intervals to approximate the UI behavior</li><li>Performing a final cleanup of low outliers</li></ul>This process produces consistent results; however, I have observed that certain values do not fully align with those presented in the MyGeotab interface. The discrepancies are minor but noticeable, with some offsets.My questions are:<ol><li>Does MyGeotab apply any internal filtering, normalization, or aggregation to raw diagnostic data (such as RPM or speed) before presenting it in the interface? If so, could you clarify the process or criteria used?</li><li>On occasion, I encounter speed values that exceed what would normally be expected under typical driving conditions. I understand that such anomalies could potentially be influenced by temporary GPS signal loss from the GO device. Could you please clarify why these spikes occur and whether signal loss is a typical contributing factor?</li></ol>

Thank you for the detailed clarification. The explanation provided was very helpful and addressed the key points clearly!!

I'm looking for clarification on the MyGeotab API rate limits. I've seen mentions of a 100k daily request limit, but I would like to know: Geotab Developers<ol><li>Is this limit fixed per database or per service account?</li><li>Is there a way to query the system to see my current usage status or remaining 'credits' for the day?</li></ol>I want to make sure my extraction process is optimized and doesn't get throttled. Any guidance or links to specific documentation on tracking this would be great.

Thanks so much for your time!

When querying a LogRecord to locate an ExceptionEvent using its timestamp, the standard approach is to find the closest coordinates. My question is: how practical is it to use interpolation in these cases?If the event occurs at point B, but I only have GPS logs for points A (before) and C (after)—and they are more than a minute apart or on a curved path—I'm concerned that linear interpolation might cause errors, placing the vehicle off the actual road.In this scenario, is it better to just use the closest actual coordinate? Also, does the MyGeotab API have a native function for this interpolation, or is working with the nearest data points the standard practice?This is my first time working with telemetry; by the way, thank you so much for sharing the available diagnostics.Thanks again for your help!

Recent Activity

RPM Values

MyGeotab Rule not working as expected

RPM & Speed values