A Need for More Sensor Data

I've been having a great time using NFC Launcher geofencing combined with URI calls and scripts to automate things. But one of the challenges I'm facing: lack of altitude and accelerometer sensor data.

Let me explain by outlining what I have, then specifying why lacking those bits presents a challenge. Or rather, describe the workflow.

Step 1) leave home
I exit geofenced home zone, Wi-Fi is turned off (except for location awareness), Bluetooth on, status message on IM clients and status board set to "in transit" with link to Location+ badge, ringer set high and vibrate, speak text (mine says "now leaving Sanctuary, prepare for renewal Runner" - Logan's Run reference), mobile data turn on.
That all works great, as does a similar anti-sequence on reentry.

Step 3) arrive at client location
I enter defined work zone, culled from Google Contacts in Business Client group address entries. Join their WiFi network, set phone to vibrate with low ring, keep the Bluetooth on because I'll likely have my headset on, update status to "On-Site", update client HUD for Fonality via HTTPS call to status "the doctor is in" / available, check in via xyz (foursquare and g+ primarily/eventually), mobile data off, and create a Calendar Event for one hour on site minimum in corresponding client billing resource calendar and invite myself at business calendar email address. The advantage to this is I now have an email on my device that I can reply to with time adjustment, notes, particulars, and I can invite those on-site that should be cc'd on the ticket.

Now, here are the two places I have a problem/annoyance.

1) Multiple clients on different floors of the same office building. Need to include altitude as part of their zone definition.
2) Clients near, over or under heavy traffic routes. Need accelerometer, because I don't want to generate a ticket for just walking by. I'm fast, but not that fast.