ElliottPlack's Comments
| Changeset | When | Comment |
|---|---|---|
| 158630742 | its gone, unfortunately Bark Social is out of business https://barksocial.com/blogs/news/bark-social-one-of-the-nation-s-largest-and-most-beloved-dog-bars-is-closing-its-doors |
|
| 159467875 | Hello Nater Kane, welcome to OSM and thank you for your contributions around PVSP. I am interested in your work in the park as it relates to access, closed trails, and related matters. Myself, park rangers, and the FPVSP developed a means of auditing all OSM trails within the park a few years ago and speaking for myself, I'd love to have you continue with the torch. If it is easier I'd be happy to set up a call or meeting and I'm always happy to review any issues you find where they related to on-ground conditions and what is on OSM. Warm regards, Elliott Plack |
|
| 159469294 | Nater, thanks for trying to help here. Have a look at way/175902858 Something went awry there. |
|
| 159151067 | Greetings. What is the source of these boundaries named as orders? Is that name (the changeset name) something that can be observed on the ground, on a sign. If you could amend the boundary with sources, we'd appreciate it. Elliott Plack
|
|
| 152917505 | Yes, there are roads on military based that are open to the public but this is the exception rather than the norm. Garrison commanders can raise the FPCON at any time and limit the accessibility of the base (in areas behind the gates). What I don't want to see is you (or anyone) make general edits to military installations without checking conditions. There have been a number of DWG cases lately where people make edits to bases over access, only to be reverted. Their reasoning is around being unable to route their [insert delivery app name] there. That is a software problem however. Routers can permit access over private routes if the developer desires to allow this. |
|
| 152917505 | Agreed, all roads on the base, any US DOD installation should be access=private. You can make them private=military although that is still under active discussion on the forum. Think of it like this, say you’re out jogging and approach the gate of an installation. You ask a guard hey can I go in there and run around? Of course, the guy at the gate will probably say GFY especially at bases around here like Fort Meade. Permitted access tagging in OSM is for things where the public and generally get the permit. Joining the military or obtaining a secret security clearance does not meet that bar. |
|
| 102947554 | Henry, Good find, I think you're exactly right. I was aware of the little stub being public and am not sure why I changed it to private. I've been down there many times as my parents lived nearby until just recently. I've just edited it back though I did not merge it so as to preserve history. changeset/158918234 |
|
| 157302727 | Robert, one improvement is to be sure to connect any sidewalks to an adjacent roadway for routing. you can add a crossing, even if unmarked, at any intersection. |
|
| 157564716 | Hi there, nice work on tidying up. Please do consider something more descriptive in your comments beyond "update". Also, regarding disassociating nodes from buildings, e.g., at Walgreens, it is fine to leave them merged. I will take care of that. Not everyone enters at the entrance. You can map the entrances though if you like. |
|
| 145094255 | Hi there. Elliott here from the DWG. In this changeset some bus stops were misattributed from the Charm City Circulator to the Maryland Transit Adminstration. These services run indepentently and often utilize different stops. Could you look back at this changeset at ones that moved the operator to MTA from CCC? https://overpass-api.de/achavi/?changeset=145094255 Example: node/1994082203 In the example, the MTA does not serve the Harbor Point area. |
|
| 158088258 | Hi! Elliott here from the forum. Regarding tiger cleanup I recommend clearing all those tags as a symbol that someone has cleaned it up. Some argue keeping those tags but at this point they are some 15 years removed from the TIGER dataset. The community forum will always have something to say on this topic. My approach is to clear all of them and then set the surface. Since the surface isn't in the import and it often either asphalt or concrete, it is an easy way to say someone has been here and looked at it. |
|
| 24901059 | Hey there, thanks for doing that! |
|
| 153404972 | Thanks for doing this but please report these sorts of things to DWG so we can take it up with the user. In this case they have gone on to make more bad edits (which you can feel free to revert if you'd like) |
|
| 153313375 | Hi there, Elliott here with the OSMF Data Working Group. How exactly was this speed limit field verified? According to the Maryland SHA, the entire beltway is 55 MPH: https://data-maryland.opendata.arcgis.com/datasets/maryland::mdot-sha-roadway-posted-speed-limit-signs/about Additionally much of this area is under a speed limit reduction for a temporary work zone, where speeds are dropped lower than 55 during construction. In other changesets you've set the DC beltway to 70 MPH yet it is also 55. Why did you do this? |
|
| 151166796 | Aaron! I love to see that you're back mapping. How are you doing? I'd love to catch up sometime. -Elliott |
|
| 153752243 | thanks for the corrections while working on the import! |
|
| 153746640 | Review: 1. If you know this to be paved in asphalt or concrete, please do specify that the surface is one of those options. "paved" is generic. 2. try to vary your changeset comments a bit, such as noting when you have noticed the change or what is unique about one road or another. |
|
| 153746595 | Thanks for adding your local knowledge to the map! |
|
| 153751846 | Welcome, thanks for adding this school! |
|
| 48603942 | Hi there, someone recently deleted this park. Please discuss: changeset/153750960 |