Database error: Buildings displayed in random order (St. John's)

[vid]

The city page building list for St. John's, and the St. John's building diagram, are listing buildings out of order when set to display buildings by roof height. This issue is resolved with the diagram display when the height preference is changed to pinnacle height.

I've plotted the buildings out on a spreadsheet listing their heights, and can't see what could be causing the problem there. It doesn't appear to matter whether the height is official or estimate, when the building entry was created, or what the status of the building is. It just seems random.

This issue is resolved. Changing the building height to a different number and then back to its original number fixed the ordering problem. This issue may exist for other cities, but I haven't found any.

Searching other cities:

Niagara Falls displays three observation decks at the end of the diagram but is otherwise in order.

Saint John, NB displays smoke stacks at the end but is otherwise in order.

Lansing displays Michigan State Capitol last but is otherwise in order.

Thunder Bay does not display its buildings in order.

With one minor issue corrected (height estimate not matching diagram), Duluth now displays its buildings in order.

Moncton displays one building out of order. (Moncton Place)

With an antenna/spire mix-up corrected, and ignoring the INCO Stack, Sudbury now displays its buildings in order.

Ljubljana displays its buildings in order.

[realcity]

The dia looks to be fixed to me. I think St John's has a decent skyline. I think it looks cool, surrounded in fog and the remotness

[Architype]

Thanks for trying to sort this out.
If it can't be fixed perhaps we could create new entries and delete the old ones.
Is this problem known to appear anywhere else?

[vid]

Originally Posted by realcity

Now can someone fix my login on diagrams so i can upload. It's probably my fault.

Send a PM or Email to Dylan or Mike, I'm pretty sure they both have the ability to fix that.

Originally Posted by Architype

Thanks for trying to sort this out.
If it can't be fixed perhaps we could create new entries and delete the old ones.
Is this problem known to appear anywhere else?

As I explained in a PM to you, simply changing the height data to different numbers and then re-adding that data seems to solve the problem.

[Architype]

Great!
Thanks for figuring that out.