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.
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.