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

Hello MastaDLo,

Can you take another look at the following ways:

osm.org/way/40178868
osm.org/way/40178871
osm.org/way/40178896
osm.org/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.

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

osm.org/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).

Hi Adam,

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

osm.org/node/5142323597

osm.org/node/293838964

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

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?

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".

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).

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.

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.

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

This doesn't appear to be in the right location. At the very least, it might not be a business that people would visit, so it probably shouldn't be at that location.

Ugh. Sorry about the massive bounding box. Didn't notice the Home Depot change until it was too late.

You might want to double check your import. There are some really contorted buildings like 691728535 that are getting through.

I was expecting to see something basketball related being mapped, not golf. ;-)

It might help to draw in the benches with either a node or a way to make it clear that there is something that is separating two adjacent pedestrian sections. Right now it isn't clear that you can't walk from one pedestrian section to another and someone will want to edit it to join them all into one larger pedestrian area.

Thanks @sannkc!

Thanks for the contribution @Lhooq2. The point you drew was in the middle of a parking lot though instead of on top of a building. Would you say the Dollar Tree is in the building next to the Parkrose Hardware building, or next to Good World Chinese Food?
Thanks.

Hi @grid1811plan, I was looking at this edit and it seems overly complex. I'm assuming you've been there, so maybe you have a lot more on-the-ground knowledge than I do looking at it from a satellite.

It seems that there are many pedestrian areas that are almost touching and overlapping each other. Is there something that prevents a person in one of these areas from getting to the next area? Maybe a small fence of some sort? If not, is there any reason that the pedestrian areas can't all be combined into one?

See for example the following three, very small pedestrian areas:
osm.org/way/684936393
osm.org/way/684936390
osm.org/way/684936391

Any insight you can provide would be appreciated.

Thanks.

@Robbie, do you know where KY94 changes from "East" to "West"?

Hi Robbie.

First question, does AT&T use OSM for figuring out where people's addresses are?

I've fixed up the node you created to be a house with properly formatted data. That is the first step. The second will be to make sure the geocoders (software that can translate an address like "123 Main Street" into an location on a map) will do the right thing. I'm not an expert on that aspect, but will hit up some other people and see if they can help.