Just back from a trip, and iFly was still indispensable! And I found 2 new airspace bugs.....
One I only found because I live nearby and looked at the map often enough for the discrepancy to sink in: there's a national-security altitude request zone over Oak Ridge, Tennessee, and the Y-12 nuclear facility which is specified as minimum-3000 AGL on the sectional chart but described as minimum-3000 MSL in the iFly vector map info note. Maybe that's the only such bug in the system...I haven't looked anywhere else for similar airspace. Maybe Hanford WA and Savannah River Site SC?
A more concerning discrepancy exists in the vector map's failure to depict a piece of the restricted space east of Altus OK, R-5601G. I left KAXS and turned east from north of the field, planning on transitioning north of the restricted sectors shown in the iFly vector map, seeing no G sector there, but as I approached the northern tip of the G sector, my 530W gave an airspace alarm. I had enough time to click the Garmin airspace (navdata current through Jan 3, 2019) and confirm the name and altitude limits, then initiate a parallel course northward far enough to miss the sector's tip as I continued east. Then I saw the sector is depicted on the current sectional. Since adopting iFly in 2014, I rarely look at the sectional charts when planning a route, so this reminds me the sectional graphics are still the legal reference that must be consulted. I get lazy! Hopefully this is a data transformation artifact that ends up being a one-off.
Still the best tool for planning and flying coast to coast at 160kt in all kinds of weather, thanks!