DUGA's Comments
Changeset | When | Comment |
---|---|---|
98514398 | almost 4 years ago | It is really hard to say what kind of mapping for the service road in the gas station is better, especially the station is at the corner as a triangle area. But when you make them too detailed, it will create an issue for the routers because they cannot tell whether you are on this road or that road (they are both in the gas station) because they are really close to each other. And thinking about how drivers receive TTS. When they get into the gas station, do they really desire unwanted turn voices? I've updated them based on my test drives. |
110484737 | almost 4 years ago | Yes. Feel free to CC me in any relevant discussions. |
110484737 | almost 4 years ago | "traffic_signals=signal" is a vague term as it does not clearly define what kind of "signal" it is. |
110484737 | almost 4 years ago | |
110484737 | almost 4 years ago | This is really weird. I've tagged like this for hundreds of times as it is shown in the iD "Type" dropdown. |
107993779 | almost 4 years ago | I've extracted all merchants based on iD warnings. If you feel like it is an error, please revert. |
85964609 | almost 4 years ago | Seriously speaking, you should check your own data before importing them. I really wish to delete all your previous imports and then draw the water on my own, because there are too many dated data were added with offset issues. |
110769754 | almost 4 years ago | Please check osm.org/node/158395844#map=19/39.69508/-79.15114 |
57815042 | almost 4 years ago | When there is no physical barrier, it should not be mapped as a separate way. |
110736536 | almost 4 years ago | May I ask for the reason drawing the road area here? |
83559966 | almost 4 years ago | I've removed this stop sign because there is no such thing. You only need to stop when pedestrians are present, but that's common sense. |
78946560 | almost 4 years ago | I don't think the Meadow Park has such a detailed boundary along Big Elk Crk and I've removed them. |
98867606 | almost 4 years ago | Please ensure to enable relevant layer while mapping. You added a duplicate of osm.org/way/61339194 as osm.org/way/904857590. Moreover, avoid using dated sources to map Maryland. |
105517807 | almost 4 years ago | Would you please check osm.org/way/948324225/? Is it an invalid data? |
89777871 | almost 4 years ago | Please do not reinvent an existing landuse feature for logistic grounds. |
64746292 | almost 4 years ago | I don't have any issue with anyone. What I originally wrote was pretty simple: How about...? It is your choice to "yes/no/whatever". I cannot do anything for you. Checking the source is very important because it not only reduces errors but also saves time of everyone else. Let's stop this conversation here. |
64746292 | almost 4 years ago | You cannot win this time. How about verifying the building I mentioned there and see who is correct? It is still "in" the ESRI clarity, why not adding back if I'm wrong? 3 years ago you added something from 10 years ago, that does not sound OK to justify your local knowledge, right? |
110806812 | almost 4 years ago | Yes they are really cosmetic. What I’ve done is adding the full name of the garage and drop TIGER tags of 2 streets after aligning them. |
104825478 | almost 4 years ago | Please avoid attaching any park area with road segments. |
87727326 | almost 4 years ago | How about learning road type first? You created a mess here, literally make the data unusable. |