It would also be helpful if you mapped where you live.

boopington please stop removing features in the map. That appears all that you are doing. That is not mapping. You also need to add more information in your changeset comment than removal.

`This mapper is removing stuff all over the US.

You deleted a bunch of my work. It would be nice if you would include more of a discussion than removal. Why did you you remove all the buildings in a plant nursery?

Do you have some site documenting the name, "Phoenix Trail"? I ask because the signage all the way up to AZ Loop 101 has Valley Path as the name of the path. You can see the sign here in this Mapillary image. https://www.mapillary.com/app/?lat=33.59760332151898&lng=-111.99199106085686&z=17&pKey=Lulir1jVVAPHqvhwqSr3FA&focus=photo&x=0.43165201244769014&y=0.42224225925007813&zoom=3

I cleaned up the false edits to the area.

Hey SuperDupes. We map real things in OpenStreetMap. There is no park called Open Door Park at this location. This is a church not a park. Please don't make fictitious edits for Pokemon go.

Thanks for fixing the overlap issue. I did not think of that when trying to get the building to render.

@clay_c Yes OSM is collaborative. OSM changed building:entrance to the entrance scheme. I already told you that I have been eating my own dog food. I found that the use of the name tag for street crossings has limitations. The crossing information is only for search. I am using the alt_name tag for that purpose. Crossings are obvious from a visual review of the map. They do not need to be spelled out. The real benefit is the NextRide number. The number can be observed at the same time that the crossing information can be observed. You are not listening. It is not just the train route in question here. The whole bus system including the train route has been tagged with the NextRide number for years. You want to blow away years of work because you have armchair mapped what you think a rider needs. You ignore local knowledge and continue to refuse a reasonable explanation why the stops in the whole system are tagged the way they are keeping the transit rider in mind. Please be humble enough to understand that you are engaging in an edit war against local knowledge. Please stop. You are taking time away from my other editing.

Thanks,
Greg

@clay_c You don't work here. You don't live here. You don't survey here. You do not use the transit system here. That is armchair mapping. The problem is that you are embarrassed that you were caught doing it.

@clay_c I am just a volunteer. Sometimes all I have time for is to add one node to the map each day. That does not mean I am selectively responding to your private messages. Moreover, in private messages you have come across as bulling. In changeset/82472573 several mappers disagreed with your arm chair mechanical edits. You had to rollback many of these changes. You are impacting local knowledge and edits from local mappers.

1. I presented the tagging scheme and its usefulness in August 2018 to the #bus osm.us slack channel. The channel was just started in May 2018. I also presented the information to the #general slack channel September 2018. Yet again the edits were presented in the slack channel #imports September 2018.

2. The scheme was developed with another local transit rider TheDutchMan13. Note that Phoenix has a dynamic population. It is hard to build an active core of mappers because of the movement of people.

3. Valley Metro Org has their own webpage and rider app. No one depends on the tagging other than a couple of transit users that eat their own dog food. The existing data consumers have no trouble using the data. I still add minimal PT version 1 tags to enable this. Moreover, it is often the case that wiki page names or Q codes do not match the actual on-site information. The name tag and the wiki tag name can be completely different.

4. More than five years ago I surveyed transit system mapping across the US. They were all version 1 and largely incomplete. I am using version 2. What I found out in practice and use as a local transit rider is that the name tag as it was being used did not actually add any value to using the osm data. All the name tag gives you is a way to search for a cross street. Hence, when I have time I go and survey the stops for both bus and rail adding both the alt_name tag for search and the NextRide number for the name. The NextRide number is more useful when you are trying to catch a train or bus. It is obvious what the cross streets are when you look at a map. It is not obvious what the NextRide numbers are. Burying the NextRide in the ref tag adds no value. However, after survey I add the NextRide number into both the name and ref tags. Valley Metro Org is a massive system. That means that it takes time to drive every route with Mapillary to survey all the stops. The name tag being used for searches lead to abbreviated messes all over the map. The tagging scheme does allow for evolving to an improved use for data consumers.

As I said before, I both live here, use the transit system, and map here. You are coming off as real demanding as an arm chair mapper.

I ride the transit system. If you text 10009 to 22966, then you will see the next time the train will arrive. Hence, the cross streets are not useful as the name. The cross name was placed in the alt_name tag.

Stop 10009Rt. Valley Metro Rail East Gilbert Rd/Main St @ 07:25 PM, 07:45 PM, 08:05 PMRt. Valley Metro Rail East 44th St/Washington @ 07:15 PM, 07:37 PMRt. Valley Metro Rail West 19th Ave/Dunlap @ 07:19 PM, 07:39 PM, 07:59 PM

I ride the transit system. If you text 10009 to 22966, then you will see the next time the train will arrive. Hence, the cross streets are not useful as the name. The cross name was placed in the alt_name tag.

Stop 10009Rt. Valley Metro Rail East Gilbert Rd/Main St @ 07:25 PM, 07:45 PM, 08:05 PMRt. Valley Metro Rail East 44th St/Washington @ 07:15 PM, 07:37 PMRt. Valley Metro Rail West 19th Ave/Dunlap @ 07:19 PM, 07:39 PM, 07:59 PM

A mass edit list this across a large area is never good!

I appreciate the passion of this change. However, you edited out local knowledge. I left comments about my last change in the hopes that other mappers would understand that my public transportation network is different. I am removing your edits.

Dude. I have contacted the data working group. At this point you do not understand that you are making bad changes to the map. The can be improved. However, now you are resorting to childish vandalism of surveyed data.

Dude. I have contacted the data working group. At this point you do not understand that you are making bad changes to the map. The can be improved. However, now you are resorting to childish vandalism of surveyed data.

Dude. I have contacted the data working group. At this point you do not understand that you are making bad changes to the map. The can be improved. However, now you are resorting to childish vandalism of surveyed data.

GREGMAP1 there are routes that depend on existing ways. You damage existing work by deleting the ways that are there. You are not adding back information that was already there. If you make these changes, then make them fully. I am having to come behind you and fix your work.

I don't understand your changes. You have doubled up crossing information at major intersections on Scottsdale Road and removed traffic lights. Please stop these changes.