Hello pidugu konda reddy,
Thank you for your contribution to OSM,
I noticed that you changed the classification of several existing streets to highway=construction in the following changesets:
changeset/175266163
changeset/175267993
changeset/175266434
changeset/175265865
changeset/175264459
By changing the classification to construction alone, many roads appear “floating” on the map without a defined road type. This can negatively affect routing, map rendering, and overall data quality.
According to OSM guidelines.
highway=construction
The correct way to map a road under construction or a future road is to use:
highway=construction together with construction=* (where * describes the type of road being built, e.g., construction=primary, construction=residential, etc.).
Also, I could not find any reliable sources or public documentation (e.g., local news or municipal announcements) justifying a long-term closure or full reconstruction of these roads.
Here are some of the affected streets for reference:
way/1040624349/history
way/222087274/history
way/624531373/history
way/903284498/history
way/1033971671/history
Could you please provide the sources or reasoning behind these edits and correct them if necessary?
Best regards,
Eslam Elsayed

Hello Ayumu "Osaka" Kasuga,
I noticed that you changed the classification for some streets in the following changesets:
changeset/160960328
changeset/160959539
One of the changes involved shifting the classification of this road from "Primary" to "Motorway" However, this classification does not seem to be suitable for the road network.
Could you please provide the sources or reasoning behind these edits?
Here’s the link to the streets for reference:
way/728130096/history
way/1050764767/history
Best regards,
Eslam Elsayed

Thank you for your kind words, and happy mapping!

Hello, pidugu konda reddy;
I noticed you reverted my edit and changed the value of the oneway tag from "yes" to "-1"
Example: https://osmlab.github.io/osm-deep-history/#/way/557409331
and added "oneway=-1" to some streets
For Example:
way/33903981
way/652131228
Please keep in mind that when you added the oneway tag It better be (yes), and you can check the OpenStreetMap wiki
oneway=-1
Regards
Eslam_Elsayed

Hello, andreidulgheru;
Thank you for your quick response. I'm pleased that we are in agreement on this matter.
Best regards,
Eslam Elsayed

Hello, andreidulgheru;
Thank you for your efforts in enhancing the base map in Qatar. I appreciate the collaboration and feedback.
I noticed that you've updated the access tags for the streets in the National Car Company: to "access=private"
But, according to the OSM Wiki definition:
access=permissive
A way is open for general public use, but access is not protected by law. The owner of the object or way may revoke access without following a legal process.
I also reviewed the provided ground imagery, such as from Kartaview and Mapillary, which show open gates in several tracks, indicating public access.
https://kartaview.org/details/9198857/0/track-info
https://www.mapillary.com/app/?pKey=443468537318665
Our team edited these streets as "access=permissive " after reviewing the imagery and found that "access=permissive" is more appropriate, reflecting the actual situation.
Changeset: changeset/154380957
Appreciate hearing from you your reasons for why you added "access=private" for the streets.
Best Regards
Eslam_Elsayed

Hello, oliviar_grab;
Thank you for your efforts in enhancing the base map in Qatar. I appreciate the collaboration and feedback.
I noticed that you've updated the access tags for the streets in the Ezdan Palace Hotel area to "access=private"
But, according to the OSM Wiki definition:
access=permissive
A way is open for general public use, but access is not protected by law. The owner of the object or way may revoke access without following a legal process.
I also reviewed the provided ground imagery, such as from Kartaview and Mapillary, which show open gates in several tracks, indicating public access.
https://kartaview.org/details/9149849/0/track-info
https://www.mapillary.com/app/?pKey=291595592600872
Our team edited these streets as "access=permissive " after reviewing the imagery and found that "access=permissive" is more appropriate, reflecting the actual situation.
Changeset: changeset/154379626
Appreciate hearing from you your reasons for why you added "access=private" for the streets.
Best Regards
Eslam_Elsayed

Correction: Source used was Maxar SecureWatch Imagery 2024-05-17

Hello cactolith;
I appreciate your contact, and I checked the GPS tracks it was helpful that you uploaded and I will keep in mind this point.
Regards
Eslam_Elsayed

Hello Ahmad-0772;
Thank you for reaching out.
Unfortunately, the satellite image has no update in this location.
From our side, we will keep tracking this image, and we will make the necessary updates when the new imagery is available.
We would appreciate it if, near this location, you could upload a new mapillary and we will make the necessary update.
Regards
Eslam_Elsayed

Appreciate your response:
These streets that you change the street names:
way/178063593
way/178718687
way/178063586
way/178063611
way/234851750
way/625368209
way/235428736
way/480288289
way/235428734
way/806400076
Thank you for your response.

Hello NO1xMOHAMED;
Thank you for your response to the message that we sent to you in private, Yes please if you can capture an image for the sign it will be helpful for the community also,
You can use also "mapillary" to take ground level imagery for new streets that opened or new signs that you find:
Here link might help you
How to Contribute to Mapillary
https://blog.mapillary.com/update/2022/08/31/getting-started-with-mapillary.html
Regards
Eslam_Elsayed

Hello Youssef ahmed65165345;
Please be careful you added many tags that didn't relate to geocode points.
Examples:
https://osmlab.github.io/osm-deep-history/#/way/98490517
Also, added vandalism relation.
Check OSMCha:
https://osmcha.org/changesets/138038690
I fixed all these issues.
Regards
Eslam_Elsayed

Hello LockOnGuy;
Thank you for reaching out. Our team and Maxar have an agreement that allows us to use Maxar’s most recent nonpublic imagery for updates in OpenStreetMap, and I updated this location now and using "Maxar SecureWatch Imagery 2023-05-22"
Link for changeset:
changeset/136829952
Regards
Eslam_Elsayed

Hello LockOnGuy;
I removed it by mistake and I Fixed it in this changeset
Link For changeset:
changeset/136829265
Regards
Eslam_Elsayed

Hello LockOnGuy;
Thank you for noticing that and I Fixed it in this changeset
Link For changeset:changeset/136826921
Regards
Eslam_Elsayed

Hello HagarZ;
I noticed you added new streets overlapping the existing roads and see you made this issue frequent in other locations.
Examples:
way/1164227615
way/1164200469
way/1164218053
Could you check this issue and fix it, please?
Regards
Eslam_Elsayed

Hello LockOnGuy;
Thank you for noticing that, I only updated this street to make it bi-direction because it was connected with some streets it was under construction and I saw you update this street as your local knowledge in this located in this changeset:
https://overpass-api.de/achavi/?changeset=133101244
Thank you for your understanding.
Regards
Eslam_Elsayed

Hello tmerc58;
I see you deleted one street and it already exists in satellite and tracks
Link for the street:
https://osmlab.github.io/osm-deep-history/#/way/1116221677
Link Mapillary:
https://www.mapillary.com/app/?pKey=471946121230020
Could you revert this street as it was, please?
Regards
Eslam_Elsayed

Hello commune echrayaa-machrek echames;
I noticed you removed the "highway" tag and added unofficial tags that didn't match the Wiki OpenStreetMap.
Example:
way/550324062
Could you verify it and fix it, please? If you want any help please let me know
Regards
Eslam_Elsayed