# XLSForm spec proposal: auto-location type for background location capture with setlocation action

**URL:** <https://forum.getodk.org/t/xlsform-spec-proposal-auto-location-type-for-background-location-capture-with-setlocation-action/20831>\
**Category:** Development\
**Created:** [July 9, 2019, 10:52pm UTC](https://forum.getodk.org/t/xlsform-spec-proposal-auto-location-type-for-background-location-capture-with-setlocation-action/20831 "2019-07-09T22:52:30Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![LN](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/ln/32/1605_2.png) [@LN](https://forum.getodk.org/u/LN)\
**Post date:** [July 10, 2019, 11:26pm UTC](https://forum.getodk.org/t/xlsform-spec-proposal-auto-location-type-for-background-location-capture-with-setlocation-action/20831/3 "2019-07-10T23:26:55Z")

</div>

In the TSC call, there was discussion of changing the action name to `setgeopoint`. Let's finalize that naming at [Spec addition proposal: location preload - #14 by LN](https://forum.getodk.org/t/spec-addition-proposal-location-preload/10768/14) and then this spec can be made consistent with the action name.

> [@martijnr](#):
>
> And we'll likely have to add an 'end of record' event

Excellent point. Is that an argument for naming the type something more like `auto-start-location`, then? Or perhaps just `start-location` since the fact that it's linked to a particular event implies that it's automatic? That would be nicely analogous to the `start` and `end` time preloads.

---

_[View the full topic](https://forum.getodk.org/t/xlsform-spec-proposal-auto-location-type-for-background-location-capture-with-setlocation-action/20831)._
