Skip to content

Melb: destinations do not have unique IDs #189

@carlhiggs

Description

@carlhiggs

The Melbourne microDestinationAttraction features do not have unique IDs, however Manchester's do.

As per #175 (comment) , this is an oddity that plausibly could have some impact (even if it may not necessarily be the one causing #175 , but we can hope).

We should correct the Melbourne features to have unique IDs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions