@Sammyhawkrad Reverted a bunch of ped streets to footways in downtown Accra fyi.

Thx for the reply @Sammyhawkrad - I'll answer these tomorrow. Today was a chemotherapy infusion day for me and I'm crashing now (it's midnight here)

@Enock4seth Please specify which places changed to neighborhoods from suburbs are incorrect. The very definition of the suburb tag shows that it was created for rendering. Plopping a new suburb down every 300 meters goes against everything in the definition. While it could be argued that some of these are quarters instead of neighborhoods, that's mostly just semantics.

Sorry @Enock4seth didn't notice you had inserted yourself in the convo - thought I was still talking to sammyhawkrad

There is a difference between "mapping for the renderer" and "mapping so it renders". I don't map for a specific downstream client, so I'm not "mapping for the renderer" - I'm just trying to make sure that these areas and districts actually show up! It sounds like you're local and you couldn't care less about them rendering so I'll stop changing them.

Building=part has to be in a relation for it to be valid. The only parts I deleted were for buildings that were already mapped as building=yes. Some of the stand-alone parts I just retagged as building=yes.

suburbs vs neighborhoods - pls look at the definition for each.
There are suburbs stacked practically on top of each other - suburbs render as towns, whereas neighborhoods do not. A cluster of "suburb" nodes will only render one node in almost ALL downstream clients.
As an example - La is definitely a suburb, places like Ringway Estates, North Ridge and Asylum Down are NOT.

Deleted church: Pls identify via node id

You're kinda spamming me with questions so pls be patient as I answer.
Pedestrian street vs footpath
These are streets with street names that do not allow vehicle traffic, versus simple footpaths. Footpaths often do not get rendered downstream, whereas pedestrian streets do. If the street isn't named, fine. Turn it into a footway.

Uhhhhhhh....
Well THAT'S embarrassing. I have no idea what that is, tbh. I used to sometimes make an outline of a feature I was deleting - in case I needed to re-add it later - but I can't imagine that's the case here. I'm not at my computer right now - if this way is unconnected and untagged, please delete it!

Got it - thx!

Give me the way id#

main source = Grand Co cadastral database : roads and parcel layers

It was supposed to be "alt_name". It has been fixed - thx for letting me know.

Aluu and hello! - Thanks for your contributions, but this is most definitely not how you mark out a trail on OSM. Duplicating a trail over a road tells the map database that there are 2 separate ways there.
Let me know if you want a hand creating relations for these trails you're putting down, I'd be happy to help.
Nakurmiik!

Please DO NOT map outside your area as you just did.

Don't use the "name" or "ref" key to describe what the feature is.
The "ref" field is for highway number, the "name" field is for the proper name of the feature.

fyi - I mapped this 3½ years ago, and Bing imagery from 4 years ago shows the bridge.

If I remember correctly, there was a social media post about a "tiny bridge" leading to the cabin - if there's no bridge actually there PLEASE fix it! :)
-Greg

Hey fellow Africa mapper!
2 things: Please don't convert unclassified through roads to "track", that makes them non-routable for most downstream apps.
If the road doesn't connect with any others then it's fine to convert to track.
Second, don't put a layer -1 on an entire stretch of road unless it's in a tunnel. Even though id urges you to do it, it fixes intersection errors by introducing a new error.
Questions gladly answered - happy mapping!