OpenStreetMap Canada

the Sovereign Tech Agency is supporting essential updates to OpenStreetMap’s core technology. The work will modernize OpenStreetMap’s codebase, bringing it in line with current software standards, and enhancing the contribution process through improved documentation and testing

I'm very new to this. I have used Street Complete to do some little things over the last few months, but made my first manual edits yesterday.

I'm starting by fixing up the small community where I live. A lot of stuff has already been done by some automation using "NRCan-CanVec-7.0" data and it's really wrong for civic numbers. But, it matches the numbers in the "standard" layer in the maps. I'm happy to go around and manually draw houses and update civic numbers (I did say it's a small community) but the map is going to look confusing when the base layer shows conflicting numbers. How can I fix that?

I’m outlining rooves block by block. It takes so long but I don’t want my maps to be barebones.

Tools

Mobile

• Organic Maps: Android & iOS app for viewing maps
• StreetComplete: Android 'game' where you complete quests by doing surveyor tasks
• EveryDoor: Best for editing POIs, entrances, and business details
• Mapillary: For collecting street-level imagery
• OSMGo!: Editor on Android

Desktop / Web

• openstreetmap.org: iD editor
• osmose: For detecting QA issues with map data
• JOSM: Detailed editing (steeper learning curve)
• RapidEditor

Guides

• wiki.openstreetmap.org

I see that quite a few major roads in Ontario are getting paved shoulders, plenty wide enough for cyclists, despite not being marked as bike lanes/routes.

An example of this is HWY7/12 in Port Perry - all new shoulders.

There is a tag: cycleway=shoulder, which gives me reason to think that we should be doing this.

What say you guys?

Update: Bike Ottawa has some guidance on the matter. I'll be using the cycleway=soulder tag for roads that have SMOOTH and WIDE shoulders that would work well for cyclists.

cross-posted from: https://psychedelia.ink/post/526072

My impression of Organic Maps immediately improved when I started driving. It talks! It knows exit numbers! It can tell you which lanes to use! Sure, it isn’t as polished as Google Maps, but all of the functionality is present. The UI is high-contrast and easy to read, although I wish the text showing exit numbers/street names was a little bigger. When you’re simply on the road and following directions, Organic Maps feels every bit as intuitive as Google Maps.

As my fiancee and I prepared to set off into the boonies, I plugged in the address of our hotel. About 45 seconds later, Organic Maps returned the 300-mile route to our destination. It can take a lot longer to calculate longer routes using your phone’s processor instead of a huge cloud server. It didn’t really bother me though; 45 seconds is nothing compared to the 6-hour trip ahead. If that’s the cost of using a maps app that doesn’t spray your personal data all over the internet, I’ll pay it.

It's a bit overwhelming. I see a lot of documentation, but it's a lot to read through for the average user.

Should I just download the surveyor app and start fixing things? Is there another community that's updating things?

A big issue I notice is that the building lines are all janky, which makes it annoying to use.