Skip to content

Locations: manage OSM changes (shop changes brand) #1018

@raphodn

Description

@raphodn

Story

Following #388 we store a Location.osm_version.

We now need a mechanism to actually create different location objects when the same OSM ID is used for shops that have changed.

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    Decided and/or owned

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions