ZeLonewolf's Comments
Changeset | When | Comment |
---|---|---|
111707765 | almost 4 years ago | Hey, just curious if there's documentation somewhere about what "old-style multipolygons" are, how to identify them, and what the fix is? |
111150595 | almost 4 years ago | Mapping things that you actually know are there is hardly a new concept. Especially when your data source is a smart watch GPS under tree cover and roughly in the same location as an existing trail. Please, do not make things up and map what you know to be actually there. |
111150595 | almost 4 years ago | We are not asking you to exclude "this particular trail" We are asking you to stop mapping trails from Strava heat map which are not visible on imagery and you haven't personally surveyed. |
111150391 | almost 4 years ago | Have you surveyed these trails or are you just assuming that there are parallel trails? GPS bounce is very common in the woods. |
111150595 | almost 4 years ago | Have you surveyed this trail to confirm that what you're seeing isn't just GPS drift? |
110322762 | almost 4 years ago | Thanks! |
104720717 | almost 4 years ago | Hey, uh... what the heck happened here? |
103197199 | almost 4 years ago | Thanks! |
111084904 | almost 4 years ago | Hello, you have left a gap in the Chandler boundary, are you able to fix it? |
103197199 | almost 4 years ago | Hello, you have left a gap in the Spanish Fork boundary, are you able to fix it? |
110322762 | almost 4 years ago | Hi, I'm not sure if you're aware of this, but you've broken a significant number of boundary relations, which have a missing "role". |
110902314 | almost 4 years ago | All edits reverted and spam account reported to DWG. |
110834788 | almost 4 years ago | I have deleted your recent edits. Please stop spamming SEO links. |
110808775 | almost 4 years ago | Hello, This appears to be an attempt to circumvent the blocks listed below with new user accounts and new referral domains. This type of behavior will not be tolerated by the US mapping community, and we will swiftly revert and report future attempts to bypass community standards of behavior. Please stop spamming referral links. It is a waste of everyone's time including yours. |
110763543 | almost 4 years ago | Whoops, put that on my own changeset :-D |
110763543 | almost 4 years ago | Hello, This appears to be an attempt to circumvent the blocks listed below with new user accounts and new referral domains. This type of behavior will not be tolerated by the US mapping community, and we will swiftly revert and report future attempts to bypass community standards of behavior. Please stop spamming referral links. It is a waste of everyone's time including yours. |
110756661 | almost 4 years ago | Hi, can you explain the use of `website` on hotel POIs? This is not the typical usage of that key. Also, are you working on behalf of a company? |
99332180 | almost 4 years ago | Hello, can you explain why you've drawn many tiny building fragments in this way? |
109587503 | almost 4 years ago | For background, and the reason Moira is asking, is that there is an emerging consensus in the US to tag highway classification based on the importance of roads (rather than by their physical attributes). This is consistent with global usages of that tagging. A recent talk-us discussion on this topic can be found here: https://lists.openstreetmap.org/pipermail/talk-us/2021-May/021018.html In short, mappers in various states have been collaborating to develop more consistent definitions for highway classes. We invite you to join this collaboration, with most of the discussion being on the OSM US Slack (https://slack.openstreetmap.us/) at the channel #local-alabama The new standards we've been developing, with links to state-by-state highway classification definitions, can be found at the following wiki page: |
110199187 | almost 4 years ago | Hi @Chris Lawrence. Regading "promoting residential streets and dirt roads", I don't see any of that in this changeset. If you could comment on the changeset that has the problem, it would be more helpful for the community to understand where there might be a problem. |