Changeset When Comment
191669428

Why did you change way/1043631564 from steps? That appears correct: https://www.mapillary.com/app/?lat=-36.91305727844087&lng=174.9074687178893&z=18.575360348671403&pKey=602237969404642&focus=photo&x=0.7894516985627483&y=0.5597321566057835&zoom=1.216520650813517

Also why did you change way xxx from a footway to a path, footway appears correct, see: https://www.mapillary.com/app/?lat=-36.91969611479999&lng=174.90134261000003&z=17&pKey=1381876466062865&x=0.3689643754965941&y=0.6872357219377963&zoom=0.47617536221023476&focus=photo

191539451

Please use descriptive changeset comments
---

Published using OSMCha: https://osmcha.org/changesets/191539451

191540173

Of course, you should always be using all available sources.

191540105

Why did you downgrade the crossing? There are signals here, see Mapillary
---

Published using OSMCha: https://osmcha.org/changesets/191540105

191540173

There is no crossing here, see Mapillary imagery

186681162

Wrongly changed name of The Breakfast Club cafe

191486846

Why did you remove the highway=footway tag?

191491476

Why did you down grade this from traffic signals to marked? The signals are visible in the LINZ aerial imagery and the use of lines as the markings indicate it is a signalised crossing

190782250

These appear to be driveways and not residential streets. What was the source for the name? Why is the way tagged layer=1, it does not appear to be above anything. The road way you added also connects to the street lamp which appears to be wrong, additionally you have a dangling end to the way past Ash Street
---

Published using OSMCha: https://osmcha.org/changesets/190782250

190373459

The crossings you have added in this changeset have the following problems:
1) Crossing ways not connected to footpaths making them no good for routing
2) Crossings connected to land areas etc. making maintenance difficult
3) Crossing nodes tagged at one end of crossing nodes as well as at the (existing) mid point

Also once again you did not use a descriptive changeset coimment

190675479

You have created two "Lewis Mortimer" POIs within a very small distance
---

Published using OSMCha: https://osmcha.org/changesets/190675479

190670665

You have changed the name of node/6211947921 without changing the website or other contact details, are these still correct?
---

Published using OSMCha: https://osmcha.org/changesets/190670665

190672516

Why did you change node/4706086955 from a traffic table? According to the LINZ Aerial Imagery (which you list as the source) it appears to be a table

190342340

All of your edits look to be an attempt to record locations of personal events. OSM is for recording public, verifiable geographic data.

182097941

Because there is literally no crossing here but the footpath links to the road. There is no loss of information but a correction. This was confirmed by a visit to the location on 29 July. I use various OSM routers for foot based routing a lot and the proliferation of non existant crossings makes for exceedingly misleading directions

189034516

Please note that OSM is an international project, I doubt shop=dairy has the meaning you intended, see osm.wiki/Tag:shop%3Ddairy
---

Published using OSMCha: https://osmcha.org/changesets/189034516

189085290

You have changed the tags of a footpath and land use area which is not correct. Was this a mistake or a bad case of SEO spam vandalism?
---

Published using OSMCha: https://osmcha.org/changesets/189085290

184893729

This changeset has created a series of POIs with names "Level 1 - *". Is this the actual name as on the ground or an attempt to indicate the POI is on level 1? If the later "Level 1 - " should be removed form the name and level=1 tagged instead. See osm.wiki/Key:level

187909528

What is your source for this? To the best of my knowledge flock does not operate in NZ
---

Published using OSMCha: https://osmcha.org/changesets/187909528

186958834

Review as requested: Looks good apart from a couple of minor issues:
1) There is already a node for address 1A, you could have edited that instead
2) The phone number does not follow ITU-T E.164 format, see osm.wiki/Key:phone
---

Published using OSMCha: https://osmcha.org/changesets/186958834