Thanks for the response @Bryce-1261​ 

The support request has been sent and responded to by Geotab support, as ticket/case#00510110.

Both my request for exposed MyGeotab Map vehicle "Moving" event and @LPPapillon-1145​ request for MyGeotab Map "Pan/Zoom" events are very similar in scope, but not exactly the same.

The scope of the feature request should include BOTH events as generated by external map changes and not so much related to direct user-interaction.

@Bryce-1261​ thanks for the comment. I understand Geotab is not expected to implement every feature request in a matter of weeks, but I hate being in this kind of spot. We responded to this government RFP with solutions specialists at Geotab and our PAM was very much involved every step of the way. All we got were yesses. We got the contract and it's on me to deliver, and everything that was on Geotab to help us with has been pending so long and is making us look bad. This is one simple piece of the puzzle that I was hoping would be a quick fix - when map add-ins were released initially, there were 2-3 forum posts (on the old forums) asking for new properties to be able to use .change() on as well as other callback and feature improvements requested. They were available on mypreview 2 weeks later. I know this is not typical, I was just hoping for a Hail Mary.

@lmit-1292​ just to clarify, it's true our requests aren't exactly alike, and it's true I did mention pan/zoom in my request, but really the callback I asked for was a "painted" callback, for whenever the map is re-painted. That is regardless of if it was because of a pan/zoom or because of a location refresh, or because new vehicles were selected/deselected. Basically I need to react any time vehicle cursors move (with the exception of Active Tracking devices second-by-second updates). The motives are similar to yours as well, I don't want to intensively query for DeviceStatusInfo and other calls constantly, Geotab does so every 20 seconds already (as well as other cases mentioned above), and I could just react to those if I could easily time my function to be executed on this callback. Now I have to do some heavy polling and my icon updates stutter because they are not in sync with Geotab's.

@LPPapillon-1145​ Thanks for the "Painting" clarification. Makes allot of sense and that event alone would serve me as well. BUT a "Painting" event MAY be too generic an event to return the relevant info (in the event object) that every integrator would need so they could implement efficient but responsive UI designs that serve their business needs. So it's my thought that event specialization would need to be balanced with generalized "something happened" events by Geotab developers. Whatever they implement must serve everyone's needs, which is hard to get that recipe right. But something is better than nothing, which is where we're at right now with Map events.