I setup a mobile iGate because my tow vehicle has built in hotspot, then had some deep discussions elmers and the general consensus is that Mobile iGates are bad for the network.. kinda like a mobile W2 digi.. TX igate requires that you heard someone nearby before you TX, and then you've done and gone and moved.. APRSIS isint supposed to have key points of infrastructure there one min, and gone the next.. now temporary igates to fill in at events or something would be fine.. but one traveling across the country, gating packets at one position one min.. and then gone the next.. You are supposed to be able to drop into any location get a good picture of the network within 10-20mins, oh look theres an igate nearby.. let me change my path from W1,W2-2 to W1,W2-1, aaand the igates gone and I'm no longer making it to APRSIS..
At the very least, if you want to continue w/mobile iGate.. make it clear that its mobile/temporary and entirely opportunistic in your beacons so nobody tries to use you as a reliable route.
At home I deployed a TX iGate bout a year ago, sat around and watched the traffic and noticed I could hear a large area of town that none of the mountain top digis were hearing.. so I checked some coverage maps on AprsDirect/AprsFi of the local W2 repeaters and saw a big gaping hole that nearly covered all of Denver County.. they were so high they were shooting right over it, packets from the core of denver were being heard by me, but nothing else. So I converted my TX iGate into a iGate+Digi, made a geo fence that basically includes the i25->i70->i225 loop where I was seeing the poor coverage and put it back online.. Now, right in the heart of the Urban Canyonland, the APRS network is working far better than it was before I converted to a Digi... but if I take that GeoFence off, I could easily double the noise on the network because my RX sensitivity is very high and I can hear a ton of traffic for quite a ways, my TX can hitup over four 13k+ high W2 digi's consistently, from Fort Collins to Co Springs