As an update I've finished reviewing all your prior edits and have reverted either fully or manually the data I strongly believe or you have stated to have been copied from the CTBUH proprietary database.

manually reverted in changeset/162301634 to remove proprietary data

also in changeset/162301618

This changeset has been manually reverted in changeset/162301600 to remove all proprietary data added.

hi as recently extensively discussed in changeset/158917740 skyscrapercenter.com is not an acceptable source for use in OSM. I reached out and they confirmed no commercial use is permitted, so it's definitely a no for OSM. I've had to revert a whole bunch of these added already due to this and it's causing some mess, but we need to ensure we have a 100% clean dataset in OSM from a licensing point of view.

I know you're very extensively been mapping buildings in Sydney, so can you please confirm if you had added any other data from the proprietary skypscrapercenter.com database?

hi as recently extensively discussed in changeset/158917740 skyscrapercenter.com is not an acceptable source for use in OSM. I reached out and they confirmed no commercial use is permitted, so it's definitely a no for OSM. I've had to revert a whole bunch of these added already due to this and it's causing some mess, but we need to ensure we have a 100% clean dataset in OSM from a licensing point of view.

I know you're very extensively been mapping buildings in Sydney, so can you please confirm if you had added any other data from the proprietary skipscrapercenter.com database?

Partially reverted in changeset/162301440 to remove building height as this was likely sourced from proprietary data.

building=skyscaper is not a tag in common use (<20 uses) and not documented on the wiki, nor have I seen any discussion on the tag.

In general I don't think this is a good idea, as "skyscraper" is hard to define, you'd need to pick an arbitrary height and then you may as well just set the height=* tag directly. Furthermore it removes the ability to define what kind of building it is, eg. residential tower or office building.

This changeset has been reverted in changeset/162301270 due to the use of proprietary data.

This changeset has been reverted in changeset/162301234 due to use of proprietary data.

This changeset has been reverted in changeset/162275879 due to use of proprietary data.

This changeset has been reverted in changeset/162275655 due to use of proprietary data.

This changeset has been reverted in changeset/162275567 due to the use of proprietary data.

This changeset has been reverted in changeset/162275515 due to use of proprietary data in the changes.

This changeset has been reverted in changeset/162275408

I reached out to CTBUH and heard back that "Republication of our data for commercial use in not allowed." and they did not provide a waiver to this, therefore on this basis the data is incompatible with OSM. We'll need to go through and remove all instances where you copied this data previously, and please going forward don't use their data as a source.

For building heights i would recommend other sources like compatible LIDAR data, a physical survey, or photogrametry.

While it's good they do include some information about the use of their data, I still feel "public use" is not clear enough. For example if I build their data into my commercial product and sell it, is that public use? because it's totally okay to do that with OSM data.

Even with regards to attribution, we usually confirm that a listing on osm.wiki/Contributors is sufficient, because we can't guarantee each item will directly include attribution.

It's nice to see the interest in improving our building heights data, however you can't use proprietary data when editing OSM osm.wiki/Copyright#Proprietary_data.

While sourcing a fact might be okay, in this case doing a bulk sourcing of their database is not okay. While their licensing terms at https://www.ctbuh.org/about/faq mention "public use" this is unclear.

hi could you please document your source of these building heights? It's a bit hard to claim you're "fixing" them without backing up how you came to these results?

Also for example way/466884767/history I set both ele and height, so that you can obtain the elevation of the top of the building, which could make 3D rendering more accurate as you're less dependent on the DEM, adjusting just the height without changing the ele would move the top of the building elevation.

Is this based on local knowledge, or otherwise how do you know this?

At the Newell Hwy intersection here, I couldn't see any street signs on the street level imagery, and further south we don't have any street level imagery, so it's unclear.
It was originally named based on DCS data, which still records it as Sherriff. I have no local knowledge here but it appears this follows the original Sherriff street before the new bridge was built.

Based on the DCS roads data and DCS address data, Wambat Street only starts south of the lake.