OpenStreetMap logo OpenStreetMap

Changeset When Comment
71572325 over 6 years ago

node/4011537688 was moved by this change and that altered the boundary of the Arc Dome Wilderness Area, which now has an irregular shaped boundary that crosses over itself. I'm not sure what the proper way to fix this is since I don't know which boundary was more accurately placed. Do you?

72120925 over 6 years ago

I don't do a lot with drawing roads and specifying lanes, but I'm pretty sure there should only be one way here instead of the three that go out to the street. The single way could specify the number of lanes and how many of them are in one direction and how many of them are in the reverse direction.

71804558 over 6 years ago

way/700982938 is drawn in a way that it overlaps with itself and creates three areas. Is that what is intended? If so, the way needs to be drawn in such a way that it doesn't intersect itself.

71995676 over 6 years ago

I try to think of it like a navigation router would. It would look like an intersection at that point and you could have a choice of directions you could go. Clearly not the case with a slide where "down" is your only option.

I've made it my mission to fix any ways in the US that cross over themselves improperly. So I find these all the time and do my best to fix them. The hardest are some of the crazy rollercoasters that are out there. Those keep me awake at night. :)

71637129 over 6 years ago

The correct category for this business is "Law Office".

71475534 over 6 years ago

Do you have any suggestions on how to identify "garbage data"? What if the bot didn't touch anything recently created in order to give a chance to anyone/anything cleaning up first? I doubt avoiding anything done based on frequency of additions in a short period or a certain type of object within the boundaries of another type would be very effective. (Looking for business inside a parking lot would catch this but would miss other edits considered "garbage".)

Thanks for any additional feedback you can provide.

71241439 over 6 years ago

The address of this business doesn't match the nearby roads. Are you sure that this was placed correctly?

71001114 over 6 years ago

I'm jealous, but I fixed the rotation of the creek any way. ;-)

71062762 over 6 years ago

FYI, this changeset didn't actually do anything (it's empty), because the node was already gone when the bot came around to examine and delete it.

71001114 over 6 years ago

This is the node that broke things: node/293838964

71001114 over 6 years ago

Thanks, but Yakima River still looks messed up (way/32663694). Do you want me to take a stab at fixing it?

71001210 over 6 years ago

Hello MastaDLo,

Can you take another look at the following ways:

way/40178868
way/40178871
way/40178896
way/40178841

The changes that you made to them caused them to be oddly shaped and cut across themselves. I'm sure that wasn't what you intended to happen and I'm guessing you didn't notice it when it happened.

If you need any help, please let me know.

Thanks.

71000288 over 6 years ago

Hi there Tblecptn, I've deleted one of your ways that appears to be very broken. Check out the change below.

changeset/71054799

If I have done this in error, please let me know how and I'll help you restore the road as you intended it (or will help you correct what I believe are the mistakes).

71001114 over 6 years ago

Hi Adam,

Please check out the following nodes that were moved out of place in your change:

node/5142323597

node/293838964

They pull the river out of alignment and I'm not sure what the intended change is supposed to be.

63933413 over 6 years ago

Well, it was 7 months ago, so I'm going to have to plead ignorance on whether or not it warned me on this particular case. I've found historically that JOSM does remarkably well handling existing relations when splitting long ways.

Was it my split that broke something, or was it possibly an earlier modification?

70975972 over 6 years ago

Thanks for the contributions. I've made a few changes to the POI.

1. The opening_hours was changed from "Mo-Sa: 10:30 to 20:00, Su:6:00 to 23:30" to "Mo-Sa 10:30-20:00; Su 11:30-18:00". Note the dash instead of "to", and the groups of days separated with a semi-colon, and the lack of a colon between the days and hours. YoHours (http://projets.pavie.info/yohours/) is a really good tool that will help you "draw" out the times and show you the correct format.
2. Street names aren't allowed to be abbreviated. So I changed it to be "Saint Nicholas Avenue". You can always click on the nearby street to verify the proper spelling/fullname of the street.
3. I changed the POI type from "Address" to "Jewelry Store" as the given website indicates it is.
4. Key names should be lower case, so I changed "Phone" to "phone".

70944568 over 6 years ago

I also cleaned up the opening hours format a little bit. The groups of times should be separated by semi-colons (;) instead of commas (,) and the times should be written as 24-hour time including leading zeros (so 8:00 becomes 08:00).

70944568 over 6 years ago

Thanks for the contribution. I have changed the type of node from "Address" to "Restaurant" and added "barbecue" and "breakfast" to the types of cuisines.

The hashtags you added to the change aren't attached to the actual point of interest (POI), so they will essentially be lost over time. They don't hurt anything, but don't do much good there.

Everything else looks great. Thanks.

69805005 over 6 years ago

The imagery I was using had the buildings in them (at some zoom levels) and your outline of the buildings was off by 30 degrees. It looks like someone came along a few days ago and corrected the orientation of the buildings in changeset/70845877.

70685464 over 6 years ago

You got it set correctly to "restaurant". I further refined it by setting it to "pizza restaurant". Thanks for the addition.