Merging places breaks collection projects

I just ran into a nasty surprise. I was merging several redundant places for Frozen Head State Park (one with no boundaries, two with rough boundaries, and one with accurate boundaries), ultimately consolidating on this one:

Unfortunately, there is a collection project which used one of the places with a less-accurate boundary to set its location. On merge, the location simply disappeared from the collection project! I would have expected it to update the collection project to use the place being merged into. I notified the project manager, but it’s alarming that this failed silently, so to speak.

1 Like