node/5764070254 with a British Columbia phone number placed in Lima...

this appears substantially wrong, node/5764189153 with Saskatchewan address has been places in New York - possibly because street name is the same?!

Similar to changeset/44757848

List of problems with this changeset found by manual inspection of names

way/32255085 "Lane South Ascot West Earlsciurt" spelling
way/34116598 old_name "Lane West Avenue South Mcmaster" is assuredly not an official old name and in any case mis-capitalizes "McMaster"
way/69845176 "Lane West Spadina North Sussex Avenue" doesn't meet your usual scheme
way/23434369 "Lane West Hurron North susex Avenue" - this is actually west of Huron with one R, north of Sussex with two S, inconsistent use of "Avenue"
way/23434356 "Lane East Spadina South Susex Avenue" Sussex misspelled, inconsistent use of "Avenue"
way/7991745 "Lane East Spadina Susex Avenue" again Sussex
way/10070568 "Lane West Spadina South college" capitalization
way/83070954 "Lane North dundas East Augusta" capitalization
way/22795691 "Lane North dundas West Euclid" capitalization
way/5941217 "Lane North dundas East Markham" capitalization
way/10187165 "Lane North Qeen East Euclid Avenue" spelling
way/10070533 "Lane North Dundas West Denison Avenue" inconsistent use of "Avenue"

Please fix.

Hello,

Is this a joke?

Does Telenav do QA?

way/8095700 and way/8095686 "Lane South West Lisgar" when it should be "South Afton West Lisgar" after your scheme
way/26103731 "Lane North Alma eAST Dufferin"
way/8095682 "Lane North Queen East Northcore" which should be Northcote
way/462584208 "Lane East dufferin South Stonehouse" capitalization
way/149593024 "Lane North WQueen west Markham" capitalization, spelling
way/10187164 "Lane North WQueen west Markham" capitalization, spelling
way/22788372 "Lane 1 South dundas West Euclid" capitalization, not to mention there isn't a Lane 2 so why Lane 1?
way/22795625 "Lane South dundas West Manning" capitalization
way/8099875 "Lane East Crowford North Adelaide" spelling, it's Crawford
way/30840826 "Lane East Portland south Queen" inconsistent capitalization
way/118626499 "Lane East Bathurust North Wolseley" spelling
way/83327382 "Lane East Ohara North Maple Grove" spelling, the avenue name is "O'Hara"
way/81139241 "Lane North Queen East Ohara Avenue" spelling, use of "Avenue" inconsistent with your other format
way/81139375 "Lane 2 S Dundas E Palmerston" suddenly inconsistent format - why? because you copied from the "note" from initial CanVec import?
way/81139255 "Lane E Brock S Earnbridge" same
way/146987567 "Lane North Dundas West ritchie" capitalization
way/26140020 "Lane North Dewson west ossington" capitalization
way/26140018 "Lane South Hepbourne West ossington" capitalization
way/23225347 "Lane North Dundas east Golden" capitalization
way/26103808 "Lane SWest Dufferin South Florence" what is "SWest"

This is why we prefer to have local mappers do mapping! Your company is making a bad name for itself through these edits. Why are we doing QA for you? Why should I fix it for you rather than revert these descriptive names wholesale?

Hi,

Thank you for adding the Hunsing clinic.

Your edit also broke the map a bit (see in screenshots: https://imgur.com/a/YOroSuL ). I have now un-done the broken parts in changeset/60773787.

Cheers,
Jarek

in changeset/60696107 korrigiert

Hallo,

way/552943235/history landuse=residential fuer Herzberg/Vulkan/Siegfried/Josef-Orlopp-Strasse-Block? Erst nach 20 Jahren mehr Gentrifizierung...

Tippfehler?

Hi - you've added a business in Dallas, but placed it in a residential neighbourhood in St. Catharines, Ontario, Canada. I have removed it in changeset/59915755 - if you would like to re-add it, please make sure to put it in the correct spot in Dallas.

Hm, the best places I can think of for the discussion would be talk-ca mailing list https://lists.openstreetmap.org/listinfo/talk-ca or maybe tagging https://lists.openstreetmap.org/listinfo/tagging though then you have to account for worldwide usage

There is forum https://forum.openstreetmap.org/ but the Canadian section is dead and I don't see a good tagging section, and the wiki discussions always seem mixed at best...

But, the Lansdowne example showcases the problem, doesn't it?

When you draw a separate sidewalk without a crossing, on Lansdowne it means that crossing is not permitted or safe or sometimes physically possible. But your method would have the same tag of sidewalk without a crossing mean that crossing is allowed everywhere at Galley and Sorauren.

How could a router do this without a ruleset that specifies that for example tertiary roads can be crossed but secondary roads cannot? Such a ruleset would have to be Ontario-specific as elsewhere primary and trunk tags are used for the kind of road that we see on Lansdowne. (London, England has many narrow, slow streets tagged primary that are much safer to cross than the average Toronto avenue.) Isn't it easier to just use a tagging scheme that doesn't require routers guessing?

I also don't see a problem with mapping a perpendicular path to centerline, especially with the sidewalk is not mapped in the first place. Slip roads are mapped to centerline (way/23000751) without much controversy.

Yes indeed there are many different ways to map these. I assume you've seen osm.wiki/Sidewalks#How_to_map ?

My interpretation would be that the OSM way for these roads is symbolic anyway (it goes down the centre of the roadway, doesn't specify width, etc - Toronto doesn't use osm.wiki/Proposed_features/Street_area ), so adding symbolic sidewalk information (e.g. sidewalk=both, sidewalk:width=1 m) on the road ways in cases of "simple" sidewalks should be fine.

If I may: adding the new ways doesn't seem to me to add much value and creates some problems for routers having to guess where jumping between ways/crossing streets is possible, or guessing names of sidewalks from names of nearby street (to instruct "walk south on Sorauren Avenue" rather than "walk south on this unnamed sidewalk").

But of course if you're keen on continuing then do go on, it's an open project.

Hey Nate. Thanks for adding the detail. When you draw sidewalks, please take care to link them to the roads at intersections. The ways must cross and have a common node. Otherwise the routers get confused as to how people can go, and you get results like these: https://i.imgur.com/rSBmDUU.png

Hi! Thank you for following up on this and providing on-the-ground information for open hours. I amended the information slightly in changeset/58552581 as there exists a specific syntax that can encode the access in a computer-readable format - see OSM wiki opening_hours=* and osm.wiki/Conditional_restrictions - it's a bit complicated and not easy to find so no worries - getting the information in the first place is the hard part :)

Thanks again for helping with OSM!

Source is edits and comments of Gerard Butler, in particular changesets 58369377 and 57446369; see also note/590023 for back-story.

Hallo, crossing=zebra ist nicht im osm.wiki/DE:Key:crossing ?

Radstraße in changeset/56580647 wieder angepasst

Teraz chyba wszystko jest w porządku. Dziękujemy :)

Rico, na mapie way/277203729 nadal kiepsko wygląda - możesz spojrzeć jeszcze raz?

Hallo haudegen07,

mit der Radstrasse way/28757494/history ist etwas schlecht gegangen, oder?

Hello,

MAPS.ME is adding the points you create (e.g. "Allison and Jacy's House" in Salem) to the public map on the web at node/5331466721 - this one as a tourist attraction. I'm guessing their house isn't actually a public attraction. Can you double-check the MAPS.ME settings to see if it's possible to configure it not to submit these points to MAPS.ME?

Thanks,
--Jarek