Hi rab, thanks for the tip. Road section is indeed in th meantime finished and open to motorvehicles. I changed the tagging. See changeset changeset/115554305.
Greetings and happy new year, Bert Araali

Thanks Baden for the repair. The same can be done with merge from the utils plugin in JOSM, I believe it also preserves the history of the first item you select to do the merge. Greetings, Bert Araali

Hi Habi,
I am running some test where I use JOSM as an editor with a seperate layer containing data that shouldn't be uploaded to OSM. The tag OSM=no landed by mistake from this layer on some OSM items. So I deleted it from these items. Sorry for the confusion.

Changed the catholic church back to a basketball field and the fish pond to the water well, according Mapillary survey made in 2017.

Changed the decimal , to . . Noticed also that mistakenly some buildings were copied with lat and lon on a building, copy error. Deleted those tags. Everything is now according to calibration points also stored in Imagery Offset Database. Will prepare doc later this week.

They are not offsets, it doesn't refer to any imagery, it is like the calibration points in the Imagery Offset database, coordinates in WGS84 as default in OSM, independent from any imagery or other data but usable to determine offsets accurately. Calibration:lon and calibration:lat refer to the initial positions and part of the calibrated shape. They are not stand alone nodes. If we use them on geodetic or surveyed points they will be added as attribute tags. They are required so one can verify if the original calibration shape is retained when calibration was done. You have a point with the comma, should be a point, is caused by my keyboard locale settings, will change that. The buildings are not in a different location, the nodes with the coordinates apply to that specific object they are part of. The objects should not be moved, they are calibrated with GPS readings, that's the whole point of this tagging. Be patient, will become clear when it is properly documented.

I know, and I am a very intensive user of it. The calibration point keys I am adding at this time are an extension and tested out locally. A proposal will be established when it gains support. Although the Imagery_Offset_Database is a nice implementation it has the following issues:
1. Data is stored in an external db, currently only as plug-in for JOSM. The calibration points and offsets are not accessible or implemented in other editors like iD. Since it is an external dB with a server outside OSM, one might question how long it may exist, it's up to the support and gratitude of the developer.
2. It uses a license different from OdBl, compatible but might create attribution or licensing issues in other editors.
3. The source of the calibration data cannot be entered, only limited comments are possible.
4. Only support way data. This is an issue when you want to use geodetic ref points as nodes, calibration points by default. It also doesn't allow to enter or reference coordinates in different datum.
5. Applicability is defined as a fixed radius of 15 km. Maintenance tools are poor. This especially is an issue in mountainous areas where a higher density of calibration points is needed.
So this new or reused calibration (recovered from the True Offset proposal which never gained support) key and namespace tries to address these issues, we will see if it is useful and gets support. Will truly resolve ever growing issues mostly by beginners and HOT teams to disregard true offsets. Storing it in OSM is even more desirable as it stores real ground truth and verifiable information, not just for imagery offsets but also for support of other GIS related dataset coordination. Don't worry, I will keep track of the sets I am creating, when no support is gained I will remove them later. Greetings, Bert Araali.

Thank you Habi, much appreciated ! Will search for the same typo in other changesets I made recently.
Greetings, from Uganda

You deleted a building (Plan B pub, now hanging idle) consisting of 3 units. Recent satellite imagery shows only the middle unit was demolished. Can you please add the remaining units back and consult the previous editor if the previous pub located there still exists ? Stop deletions please and use life cycle tagging so the current situation can be accurately verified in the field. We have lots of mappers around in Kampala. "Imaginary buildings" as you call them were actually there recently, it doesn't improve the Kampala map to replace them with "imaginary deletions".

As source you give survey, does this mean that the construction area you created on top of the Arua Hill pitch is no longer a community park and sports area ? Mapilary imagery of feb 2018 shows the contrary, shows it still as a playground.

You deleted a still existing building, Biryani House garage in the garden. It is hardly visible in latest imagery since overgrown by trees and was incorrectly aligned. Corrected it in changeset/105702922. Please stop deleting buildings in case of the slightest doubt and contact mapper of the original to verify. Use lifecycle tags like raze: or disused: instead of deleting.

Hello Jean-Marc, created a new calibration point in changeset #105700682. Roundabout on the Northern Bypass (find it in the Imagry Offset Database). I stopped storing offsets since they are only applicable for a specific source and for a limited time since imagery gets updated. Buildings and most of the minor roads are misaligned from various HOT projects, working on awareness in HOT teams about importance of correct offsets. Except the major roads around the roundabout didn't clean up the area but buildings are generally seriously offset. Feel free to help to correct. Please be aware that the Northern Bypass at this time is still a large construction area, which means highway classification might change over time along a single named road, we update them as the works proceed. Many roads are incorrectly tagged though, especially unclassified is used to often for major roads which should be tertiary and secondary. Are you still using ESRI ? Maxar is much more up to date for Uganda in general.

I used the Maxar Premium Imagery, you can always find that in the source of the changeset. Determining the date of Maxar Imagery might be a challenge since the metadata is not accisble through any OSM editor. However, other resources using also Maxar might give you a clue, so referencing some recent new buildings in Kibuku indicates that the Maxar Premium Imagery in OSM is from 01/2018, so much more recent then the 02/2016 you refer in the source of the buildings added. Regarding offsets, yes they were updated by another user in 2019, incorrectly, he aligned roads with his imagery and even changed many road classifications. The imagery originally was aligned according gpx tracks, as stated in the changeset comment, in an older HOT project. So I tried to find out the correct calibration of the map. Nearby, the Fort Portal - Ntoroko road (a bit south of your changeset) has a very accurate GPS track stored and freely accessible in OSM. The land north of this road is fairly flat, south is the Rwenzori's. Offset remains fairly constant across large distance in flat areas, so it is safe to use it for your area of interest. For your convenience I added an angular road plot in Kibuku town which can be accessed thorugh the Imagery Offset Database, in JOSM. If you use iD I can give you the exact location. These are calibration points, so no offsets for the imagery you are using, you have to determine the offset and align imagery correct in regard to these calibration points before you start mapping or changing anything. So from now on it is safe to re-align your imagery and change the position of the buildings on the map. Never change map to fit your imagery as no imagery is correctly calibrated, none. For your convenience for the current imagery available in OSM, the offsets are as follows:
Bing = -7.17; 1.94 (imagery capture date up to 02/2016)
Esri (clarity) beta = -0.15; -4.48 (imagery capture between 03/2016 and 11/2018)
Maxar Premium = 5.74; -1.12 (imagery capture 01/2018).
The buildings I used to check for imagery dating are at 0.939 , 30.238 . You can verify those with the dating of your imagery to find out what is the most recent but as far as I am concerned it doesn't lake sense to import data based on imagery which is older of what we have. Importing is discouraged anyway since it leads to this kind of inaccuracies.

The source you are referring to is not accessible nor verifiable, please supply decent change comment (osm.wiki/Good_changeset_comments)and valid source URL. Licensing of this source is not verifiable, it is not listed and referred to in the project description (osm.wiki/Organised_Editing_Guidelines). Please correct and justify.

Same comments as on changeset/104534545#map=12/3.4050/30.9039. Waiting for your replies.
Also the mentioned source is dubious. Is it's licence compatible or is there a waiver ?

These projects suppose to add buildings, not delete. Also major shifts are made to roads. The imagery you use is private and incorrect aligned. Before any mapping you should align the imagery with the existing GPS tracks or map, not the other way around. Please repair.

Seems this is part of the large scale building imports in UG, however the changeset comment does not give a project reference number or any useful information. This is not according the Good Practices of OSM.

Can you please explain why you changed the international border between UG and DRC ?

Can you please explain why this changeset changed the international border between DRC and UG and why you are doing mass deletions ?

Yet another shift in the international border between DRC and UG and ongoing mass deletions ? Please explain. Again a reference to the project 8886 which I can't find on HOT website.