Hi joserrg12, I noticed you created two river crossings at way/972043042 and way/253171129, but I am not seeing any evidence of bridges or ferries at these two locations. Do you have any resources or local knowledge that can justify these river crossings?
Thank you!

Hi Pilou@nowhere, Thank you for following up! Regarding your intent to indicate the road quality in OSM, I’d like to point out that the OSM Wiki (highway=*) states that the highway key should be used to “indicate the importance of the highway within the road network as a whole” and that “Only highway=motorway and highway=motorway_link indicate quality. Other road types, from trunk to tertiary to residential, service, path, footway, cycleway or track, do not imply anything about road quality, only importance and intended main use.” It also highly recommends using surface=* tagging to describe road quality.
This same logic applies to Africa, as the OSM Wiki’s Highway Tag Africa page (osm.wiki/Highway_Tag_Africa) states “A road typology should be based on the road importance and not on the surface or the visual appearance of a road.”
I’d encourage you to revisit your previous highway classification changes and update them with this in mind. If you believe a track or unclassified highway may not accurately represent its importance within the road network, it might be more appropriate to upgrade the highway to tertiary, or maybe secondary, instead of using primary.
While doing so, please be careful to apply highway classification changes to the entire stretch of highway and its connecting highway links. I noticed many of your classification changes were not applied consistently, creating many inconsistent highways, such as areas near: way/108176349, way/108176301, way/164635656, way/167186736, way/493713967, way/232650458, way/1065726687, way/157033706, way/157483078, way/157332565, way/389088782, way/1068059065, way/404414757, way/659031701, etc.

Hi Pilou@nowhere, I noticed you have recently been changing many of the highway classifications in Senegal. I see that many of these classification changes were applied inconsistently and do not match the OSM Wiki’s definitions (highway=*). For example, an unclassified highway (way/172310855) near Thiès was upgraded to primary, but it is not “a major highway linking large towns.”, as the OSM Wiki suggests (highway=primary). In other scenarios, a remote pipeline (way/404268149) was changed to secondary, causing many crossing highway validation errors. Could you please provide your reasoning for these highway updates? Thank you!

Thanks for taking another look and adding the fixme tag, happy mapping!

Hi Enock4seth, Thank you for reaching out! 18Vish is no longer on the team, but I can help answer this. After reviewing this section of road again I still see some evidence that points to it being a oneway, including Maxar showing the road has a narrow single-car width and vehicular direction is consistently pointing in the southwest direction. Do you have local knowledge or other resources in this area that you can point me to? Thank you!

Hi joserrg12, I noticed you updated many of the highway refs in South Sudan back in August, but I saw RN 2(way/972869585), A43 (way/1008226339 to way/323986421), and B38 (way/323986421 to way/191424465) are still present, which appear to resemble the previous format. Do you know if these refs should also be updated, or are you aware of a resource I could check to find out? Thank you!

Thank you for confirming, I now see the edits you are referring to. Thank you for letting us know and the team is now aware that these tags should not be extended.

Hi Enock4seth, no problem. If you look into the history of way/102486101 in JOSM, or on OSM (way/102486101/history), you can see that GO_OSM added the noexit=yes tag in their 3rd version of this way, within changeset/8727151. Another helpful tool for reviewing changeset edits is OSMCha, which shows that no tags were changed in this changeset (https://osmcha.org/changesets/63858061/). I hope that helps!

Hi Enock4seth, Thank you for catching this and reaching out to one of my previous team members. It appears the “noexit=yes” tag was actually added by the user "GO_OSM” in a previous changeset (changeset/8727151).

Hi Zsolt Beringer, thank you for reaching out about this! AlumRock is no longer on the team, but I can provide some insight here. It does appear that Maxar Premium is currently misaligned, when compared to Strava gps traces. I would recommend offsetting Maxar Premium to about "-5.86; -0.72”, which aligns well with the Strava traces.