<?xml version="1.0" encoding="utf-8"?>
<resources>
    <string name="key.usercache.location">background/location</string>
    <string name="key.usercache.activity">background/activity</string>
    <string name="key.usercache.accelerometer">background/accelerometer</string>
    <string name="key.usercache.battery">background/battery</string>
    <string name="key.usercache.config_sensors">config/sensors</string>
    <string name="key.usercache.transition">statemachine/transition</string>
    <string name="metadata.usercache.write_ts">write_ts</string>
</resources>
<?xml version="1.0" encoding="utf-8"?>
<resources>
    <string name="key.usercache.location">background/location</string>
    <string name="key.usercache.filtered_location">background/filtered_location</string>
    <string name="key.usercache.activity">background/activity</string>
    <string name="key.usercache.accelerometer">background/accelerometer</string>
    <string name="key.usercache.battery">background/battery</string>
    <string name="key.usercache.config_sensors">config/sensors</string>
    <string name="key.usercache.transition">statemachine/transition</string>
    <string name="metadata.usercache.write_ts">write_ts</string>
</resources>
Add a new "filtered_location" key
Add a new "filtered_location" key

We use this to efficiently filter location entries for detecting the trip end.
Yes, we will send up sending two sets of locations to the server, but that is
only for now, while we are still evaluating stuff. We can stop logging the raw
"location" entries later.
