OpenStreetMap logo OpenStreetMap

Changeset When Comment
129126623 almost 2 years ago

FYI, something broke with your toolchain and the output made it into the website tag.

143626848 almost 2 years ago

Phone numbers in my area don’t have an area code or country code, but the correct format is to include both of those. Same idea for website URLs.

144202706 almost 2 years ago

Thanks for your note. Could you please expand what you mean by this comment? It’s not clear to me which edit you have a problem with and what that problem is exactly. Thanks.

143878554 almost 2 years ago

I’m not sure what the purpose of this comment was. Is there a request for an action to be taken?

143702413 almost 2 years ago

The bot isn’t arbitrarily adding a trailing /

143339729 almost 2 years ago

What?

143095406 almost 2 years ago

Hey vgeorge, thanks for the report.

The bot doesn't prepend "www" to any URL. It also doesn't add a trailing "/" to them either. If you look at a request to the previous URL, you can see what the website is redirecting people to:

$ curl -I http://virviramos.com.br
HTTP/1.1 302 Found
Date: Thu, 26 Oct 2023 15:20:32 GMT
Content-Type: text/html; charset=iso-8859-1
Connection: keep-alive
Location: https://www.virviramos.com.br//

I'm hesitant to make any assumptions and replace the erroneous "//" with a single "/" or even remove it altogether. What are your thoughts?

I did a query on this in my area and found dozens of websites that redirect to https://www.example.com//, so it is far from uncommon.

142807797 almost 2 years ago

“You can please some of the people all of the time, you can please all of the people some of the time, but you can’t please all of the people all of the time”.

― John Lydgate

I've tried it both ways (few changesets with many changes, and many changesets with few changes) and someone always complains about it. Sorry, I'm going to stick with it as it is. I wish it wasn't something people complained about.

141943305 almost 2 years ago

Can you look at osm.org/node/685284562 ? It got messed up during your change and I'm not sure what the cleanest way to fix it is. Maybe you could help?

67448659 almost 2 years ago

osm.org/node/5899284188 has a broken website link. I'm not sure what it should be. Someone should either fix it or delete it.

141225581 almost 2 years ago

Can you take a look at osm.org/way/384638461? It seems to zig-zag and cross all over itself, and that goes against basic mapping rules. If you could clean that up, it would be appreciated. Thanks.

123870140 almost 2 years ago

It looks like you've duplicated every fairway (and maybe other features) on this golf course. For example: osm.org/way/703510295 and osm.org/way/907234897 are the same polygon. There should only be one polygon. Could you go back through and clean up your dupes? Thanks.

141913182 almost 2 years ago

Hi there Chris, I'm trying to clean up all the golf courses and I see you are making "less-than-ideal" edits that I eventually come around to and spend a lot of time "fixing". I'm not saying they are outright errors, but if I could get you to do them in a different way, it would save a lot of headaches.

Take osm.org/way/1211821702 for example. You are marking the boundary of the bunker with two polygons in order to not map the center rough(?) island. What should really be done is to first map the rough outline, then the bunker, and then select both areas (shift click) and then combine them in a "multipolygon" relationship by pressing the "C" shortcut in iD. The same style of mapping should be applied to fairways that span multiple holes. If they butt up against each other, they should be drawn as one large boundary and then "combine" them with the "inner" features like tees, greens, bunkers, water hazards, etc.

If you could do this going forward, that would be immensely helpful to me in my clean-up. If you have any questions, feel free to reach out. Thanks.

140239303 about 2 years ago

Depends on what is meant by "North". If it is in Lane County, then yes, I'll get around to it at some point. I usually remember as our monthly dinner meetup approaches.

137841095 about 2 years ago

Great. Good to know. Thanks Chris. I just figured it would be unusual for someone to replace a pool with a putting green, so I wanted to make sure it wasn't someone armchair mapping without knowing what is currently on the ground and picking the wrong sat imagery. (And yes, comments/replies on changesets generate email notifications.)

137841095 about 2 years ago

Do you know this course personally? I find it hard to believe they would tear out a pool to put in a putting green. The Bing imagery shows construction of what would become the pool. Can you please go back and correct this? (osm.org/way/1185318810)

138160727 about 2 years ago

Hi there. OpenStreetMap is not the place to draw in course routes for temporary events. Sidewalks already exist and you're adding duplicate information which shouldn't be done. I'll be deleting this community walk wherever I see it.

There are other tools for drawing your own map for private use. Try looking up umap.

Thanks.

130307846 about 2 years ago

The name of this road (osm.org/way/1123750989) isn't really "Road Closed", right? I was going to delete the tag or change it to something more appropriate, but I wanted to check with you first.

137657184 about 2 years ago

Hi there, can you look over your edits over the past few days and make sure you don't have the boundaries of identical areas overlapping with other boundaries of the same type? I see a lot of natrual=woods that look like polygon Venn diagrams. They should be combined into single areas where appropriate. Thanks.

134283422 over 2 years ago

While I commiserate with the dilemma of reverting objects that have been further changed, I just don't know how your request can reasonably honored. How exactly am I suppose to know about every possible data error that I shouldn't be making "minor" fixes to? Is there a list somewhere? Your request is chilling and makes me think I should never make another edit to the map lest it might make a future revert difficult.