Ideas about Orbit/Volvo

[afranke]

I find myself occasionally out in the world during my day having a thought about things to do for self-practice and learning, and much of the time lately my car and by association Orbit keep coming to mind.  Problem is, I think the ideas are decent, but don't/can't write them down and forget.  So I decided to start this thread for mostly myself to remember and discuss if some of them are even possible, otherwise the idea(s) will keep popping into my head 'anew' until I realize I already walked that path.  So here goes the short list of what I can remember at the moment, but more to come later.

Also some/many/most of these may have been discussed already, but my searching skills are lacking, so please forgive me.

1. Use the default car config details gathered in Orbit along with VIN/relevant option details to correlate common/"default" configurations for various options.  For example, if we can look at enough data we can say something like all '23 XC90s have ACC level x but all '23 V60s have ACC level y.  This may make swaps/conversions easier, as well as maybe glean some more detail about what the levels and options mean.
   
2. If you want to get fancy with Orbit, do like Volvo does and pull images of the connected car.  For example, using the Volvo developer API to get information about a car it returns a URL of an image.  Here's my car: https://cas.volvocars.com/image/dynamic/...?market=se . It's clear that the values in the URL are the variant codes and other basic details which can be modified to return different visual car configs.  Such as an Ember Red Metallic V60 PE with chrome window trim: https://cas.volvocars.com/image/dynamic/...000&w=1920
   
3. I can't remember at the moment, will update when it comes to me.