OpenStreetMap logo OpenStreetMap

Changeset When Comment
161156668

It looks like this changeset included a larger area than you might have meant. :-) Unless all of these changes were fixing the East Coast Greenway?

161186754

Oh I'm so glad you did this. I'd been seeing these out of date buildings on the map every time I'd go to Mahoney's, and kept forgetting to actually go and fix them. Much thanks for resolving my note and getting that done.

161186584

Thanks for adding these! In the future, to link notes and changesets, you can put the whole URL, that way it will be clickable. (It'd be nice if changeset #123 was clickable, but that hasn't been implemented yet.)

160949044

Ah, there's no need to revert the change on the bench -- assuming it was correct, it's fine. The issue is just that the changes were together in one changeset, and there's nothing to be done about this one; it's just something to watch for in the future. If you change the settings in StreetComplete to upload only when you tell it to, that can help.

160922236

Ah, that makes a lot of sense! Check on man_made=embankment for an existing tag that might work. And if it doesn't, feel free to make up a new tag that isn't used yet and just apply it yourself.

160922236

Looks like this was fixed by another editor in changeset/160942436

160949044

As you might have noticed, it looks like StreetComplete accidentally included changes on both sides of the Atlantic in this changeset. I'm sure you already know to avoid this, but just in case: osm.wiki/Changeset#Geographical_size_of_changesets

160933198

As you might have noticed, it looks like StreetComplete accidentally included changes on both sides of the Atlantic in this changeset. I'm sure you already know to avoid this, but just in case: osm.wiki/Changeset#Geographical_size_of_changesets

160922236

I think this changeset broke the coastline, due to the unconnected ways tagged with natural=coastline. I'm confused about what you were intending here?

159666897

Oh that's a *WONDERFULLY* useful resource -- I'll add it to the (newly created) wiki page: osm.wiki/Woburn,_Massachusetts . And it makes sense about the sign getting hit and not replaced yet.

153552465

All good -- sometimes things get moved by accident. Thanks for all your work surveying and adding details around Woburn!

160494442

Oy. That's a lovely 'feature'. Good to know!

160883543

No worries -- thanks for adding the townships at all ; it prompted me to look into them, which was fun.

160883543

And it should be fixed now (I hope!)

160723183

That makes a lot of sense! If/when you get a chance, updating the wiki with the above notes would be great. For now, I've linked this changeset on the talk page.

160883543

I'm working on fixing this, and discussing it here. I have to take a quick break for dinner, but will try and do the rest of the fixes tonight. https://community.openstreetmap.org/t/tagging-of-iowa-townships/121070/11

160888721

Ah, it was adding this node: node/12467967215 (thanks https://resultmaps.neis-one.org/osm-change-viz for being one of the few changeset viewers that can handle large bboxes!)

160888721

Whoops, along with the good changes in Stratford, it looks like this changeset accidentally included at least one change over in Easton, PA, USA! It's best to try and avoid this, as it confuses monitoring tools. You can see more about this on osm.wiki/Changeset#Geographical_size_of_changesets

160494442

Heh, with just two changes so far apart, it would have been nice to put them in separate changesets to avoid a cross-Atlantic bounding box. In any case, thanks for fixing the typo.

160664598

Please try to avoid large changeset bounding boxes like this. It helps others in tracking changes. You can see more details about this in the section
"Geographical size of changesets" on
osm.wiki/Changeset