Allison P's Comments
| Changeset | When | Comment |
|---|---|---|
| 134926803 | over 2 years ago | My bad... Made a bulk edit when I was new to OSM. |
| 134872875 | over 2 years ago | Well, turns out I didn't properly account for addresses I deleted between then and now and I readded them all. Oops! Still don't have a good way to account for them short of not touching the data at all. |
| 134872875 | over 2 years ago | Once a year seems pretty reasonable if it takes eight hours. Wonder how many street names will end up needing corrected. |
| 134817635 | over 2 years ago | Another good (widely used) option is to just create a node/point with a single house number and place it over the individual unit. One for each unit. |
| 134772070 | over 2 years ago | Oops, thank you for correcting. I was fixing the existing address but didn't realize I'd already duplicated it with the correct city. |
| 111164985 | over 2 years ago | Havre strikes me as a town, not a city node/151463250 |
| 134662259 | over 2 years ago | This edit has several errors and needs to be reverted |
| 130874910 | over 2 years ago | Salmon is not a city by OSM standards. Too small, lacks a commercial airport and major hospital, and so on. |
| 117101431 | over 2 years ago | Source is Google Maps. Unable to find any other source, likely a trap street. Needs to be redacted. |
| 134366372 | over 2 years ago | You'll want to use JOSM, create an Overpass query to download all unmarked crosswalks, and add the extra tag. It takes less than five minutes if you've done it before. |
| 134366372 | over 2 years ago | The preset for crosswalks got changed recently. I, PerplexingPenguins, and h551w had mapped a lot of them previously. I can go ahead and fix them in bulk if you'd like. It'd only take a few minutes. |
| 134364271 | over 2 years ago | I doubt anyone does, but you might try RapiD. https://mapwith.ai/rapid |
| 133914030 | over 2 years ago | A water hazard is a particular feature on a golf course. A river bordering a golf course is a natural feature tagged with river tags. The fact that golfers avoid it doesn't make it a golfing feature. Please don't get off topic. What I choose to do with my time isn't your business. I am not telling you my personal opinion, I am explaining the community's practices developed through years of editing. "Open"StreetMap doesn't mean "map things whatever way you like". It's not great that you knew this edit would be an annoyance and proceeded with it anyway. Such attitude is common among mappers using this software, and contributes to why we've tired of it. |
| 133914030 | almost 3 years ago | It is never okay to upload incorrect data to the database for any length of time, because consumers may grab it at any moment and use it for months. Fix your golfing app. It has been a headache for dozens of editors who've spent hundreds of hours cleaning up after people like you. |
| 81694137 | almost 3 years ago | There are a LOT of 0s and none seem to be valid from county data/parcel info. I was looking at the map here for ~10 seconds. 10 more seconds and I see at least a dozen more. Maybe do an Overpass query for all and mass delete, I think it is safe to assume they are all wrong. |
| 78939933 | almost 3 years ago | |
| 121222487 | almost 3 years ago | Still has not been corrected |
| 53937003 | almost 3 years ago | What exactly is the TIGER error here? Looks like a place=village to me, and legal classifications are irrelevant. |
| 17019290 | almost 3 years ago | I'm not sure that it's correct to tag ref=* on numbered streets in Grand Junction. I've never seen that done in any municipality. Do you have any insight? |
| 81694137 | almost 3 years ago | 0 Reece Street? node/7258911567 |