ZeLonewolf's Comments
Changeset | When | Comment |
---|---|---|
165443528 | 3 months ago | This edit is being discussed here:
Please join the discussion. |
86589334 | 4 months ago | Hi aduxas. I mapped what I hiked back in 2020, but that was five years ago! My GPS data is here:
We attempted to follow the trail as best we could as it was marked on the ground at the time. However, the trail alignment has changed at times over the years, so I would not surprise me if it's different now. RIGIS also has a trail layer here:
It looks like it is indeed showing a more northerly route along the pond. So if you've hiked this section and followed the signs, then by all means make the corrections! |
159938084 | 5 months ago | I think that needs a community discussion that's worth opening a thread. There's several folks I can think of off the top of my head that ought to weigh in. Sub-municipal boundaries can be a controversial topic and I don't think there's a strong community consensus. Therefore I don't feel qualified to state a recommendation unilaterally! |
159938084 | 5 months ago | The geometries were broken in various ways. Not in boundary relations, not connected to adjoining boundaries, and so forth. They are also not listed in Virginia's entry on osm.wiki/United_States_admin_level which suggests no community discussion occurred to add an admin level above 8. For these reasons I deemed them too broken to fix and deleted them. |
162028704 | 6 months ago | Should be change to boundary=statistical + border_type=census_designated_place. This was after I curated the CDP list to match the census bureau. |
160228441 | 7 months ago | Thank you! |
160228441 | 7 months ago | Good catch. Sometimes this happens after an edit conflict. I'm not quite sure how to make that OP query work in JOSM though to delete them |
161683740 | 7 months ago | Thanks for aligning the boundaries! |
161614548 | 7 months ago | Reverted pending ongoing discussion |
161612693 | 7 months ago | This topic is being discussed here, please join the discussion before editing this node: https://community.openstreetmap.org/t/gulf-of-america-gulf-of-mexico |
161402791 | 7 months ago | Also check out this project, where I maintain validator findings: https://github.com/ZeLonewolf/wikidata-qa |
161402791 | 7 months ago | Best explanation here:
|
161077676 | 8 months ago | Thanks! Should it be marked with an access tag? See the documentation here:
|
161077676 | 8 months ago | Hi, and welcome to OpenStreetMap! I see that you added Soar Way, what is the source for that name? |
160852235 | 8 months ago | Ok, everything should be set now. I reverted this changeset and re-created it correctly in osm.org/changeset/160888051. Please confirm that everything looks as expected. |
160852235 | 8 months ago | Whoops, must have fat fingered the wrong key. Thanks for alerting me |
102877282 | 8 months ago | If Towson East is a "real" boundary (by whatever definition of real makes sense in Maryland), it should get converted to a boundary relation. |
123783762 | 8 months ago | Please review this orphan boundary fragment: |
160376042 | 8 months ago | Intended changeset description was to update the Jennings boundary and conflate it to the FL/GA boundary |
152826629 | 8 months ago | A few years back there was some drama with the neighborhood association where it was murky about the roads were private (and therefore the residents allowed to post things like the no trespassing sign). However, the 2023 document seems to resolve that as far as I can tell (am not a lawyer). |