Any log can be a movement

I'm starting with a new Field Collection called "Movement" (field_farm_movement) with three sub-fields from the original movement logs: "To" (area reference), "From" (area reference, optional), and "Geometry" (geofield, optional).

I'll need to write an update function to migrate data from the old fields to the new ones. And there is a lot of related location code to update.

I'm not sure what the fate of the Movement logs themselves will be, but I'm leaning towards migrating them to "Activity" logs and removing the Movement logs altogether.

Moving forward...

Using the "Current location" pseudo-field in asset edit forms will automatically create an Observation log with the movement fields filled in and a title of "Current location: [area(s)]".

Using the "Move" button from asset lists will create an Activity log with the movement fields filled in and a title of "Move [asset(s)] to [area(s)]".

Movement logs will be automatically migrated to activity logs.

Any extra fields on movement logs that don't exist on activities will be moved there.

This is done. It was a complex change across a few different modules. All updates will be packaged in the next release of farmOS: #2876592: [META] farmOS 7.x-1.0-beta13

All farmOS repositories have been merged into the farmOS distribution (see #2876992: Merge farmOS repositories into drupal.org/project/farm). I'm going through and moving all open issues from the various project issue queues to the central queue now...