JessAk71's Comments
| Changeset | When | Comment |
|---|---|---|
| 39724857 | almost 2 years ago | Hi Mateusz Konieczny! Yes certainly I think that change would be great. The poi may not be there anymore though but the change would be fine regardless, feel free to edit. |
| 102178223 | almost 3 years ago | Hi pabi12,
|
| 131060963 | almost 3 years ago | Ok great sounds good! |
| 131060963 | almost 3 years ago | Hi OneC! Ok I agree with your assessment that based on the access tag schema it can go in either direction with: 1) access=no and then specify each mode access; or 2) access=yes and then specify each mode access; and then lastly: 3) remove the general access tag entirely and just keep each mode access tag. I would say I am partial to option 3 here since its in line with how most roads of this class and access type are tagged currently and this keeps things consistent - for example any normal piece of limited access highway that does not allow pedestrians in the US - I787 for example here: way/25286557. Would something like option 3 work for you? On alerts, no I dont have any alerts set up for this area although there is a way to do so using a third party, I normally just use the history tab in the area to check out new things in the area from time to time since I am very familiar with this area. |
| 131060963 | almost 3 years ago | Hello OneC! Thanks for your edits. Wanted to check on your thoughts about the use of the general access tag here. On the wiki for the access tag here: access=* it says "Use the access=* key to describe a general access restriction that applies to all transport modes." and access=no would mean these roads in general for all modes have no public access except where specific modes have been designated, which looks like these roads have the correct mode designations set already e.g. foot=no. But it also says here: "If only specific transport modes are forbidden, for example, at a vehicle no-entry sign, use a more specific restriction like vehicle=no or motor_vehicle=no over the general key access." Since foot=no is properly labeled on these roads and restricts pedestrian usage of the roadways here, would it be best to follow the general schema here and remove the general "access=no" tag? the existing foot=no tag does the job of restricting pedestrians. It would also bring these roads in line with tagging of traditional limited access roadways like I787 here etc. Open to ideas on it. |
| 84017920 | almost 3 years ago | Hi DUGA, thanks for catching the issue of the flow direction! I was using Potlatch 2 back then when this was done and flow direction wasnt as intuitive as it now is as displayed on the ID UI, so yes as of ID use, the flow direction should more be accurate in my changesets on water flow. Thanks again. |
| 115276447 | almost 3 years ago | No worries at all! I have the same issue with ambiguous recreation land like these, I dont really have a preference in this case so I am happy to leave them as they are but feel free to change them as needed. Perhaps a extra tag for owner/operator if known or description would be helpful on these to add an extra piece of information for future mappers. |
| 115276447 | about 3 years ago | Hi ElliottPlack! thanks for the comment, agreed if they are designated as open space they should be marked as a park, I updated the tags just now in changeset changeset/130137750. I think at the time I was reviewing the City of Baltimore parks and rec open data and these areas had no official designation in the data but I agree with your assessment. Thanks again. |
| 129430615 | about 3 years ago | Hi BigBlueParadox!
|
| 127498452 | about 3 years ago | Hi pabi12,
|
| 126878385 | about 3 years ago | Hi pabi12,
|
| 126655292 | about 3 years ago | Hi pabi12, this is another case where the entire building is not the poi so its best to place the poi in a node instead and leave the building as is since there are apartments in the floors above the POI. I have fixed this case on the map for you. |
| 126657935 | about 3 years ago | Hi pabi12, this is another case where the entire building is not the poi so its best to place the poi in a node instead and leave the building as is since there are apartments in the floors above the POI. I have fixed this case on the map for you. |
| 126679476 | about 3 years ago | Hi pabi12, this is another case where the entire building is not the poi so its best to place the poi in a node instead and leave the building as is since there are apartments in the floors above the restaurant. I have fixed this case on the map for you. |
| 126878316 | about 3 years ago | Hi pabi12,
|
| 126654698 | about 3 years ago | Hi pabi12, this is another case where the entire building is not the poi so its best to place the poi in a node instead and leave the building as is since there are apartments in the floors above the restaurant. In addition this is a restaurant and not a bar. I have fixed this case on the map for you. |
| 126653587 | about 3 years ago | Hi pabi12, this is another case where the entire building is not the poi so its best to place the poi in a node instead and leave the building as is since there are apartments in the floors above the restaurant. I have fixed this case on the map for you. |
| 126653481 | about 3 years ago | Hi pabi12, this is another case where the entire building is not the poi so its best to place the poi in a node instead and leave the building as is since there are apartments in the floors above the shop. I have fixed this case on the map for you. |
| 126653397 | about 3 years ago | Hi pabi12, this is another case where the entire building is not the poi so its best to place the poi in a node instead and leave the building as is since there are apartments in the floors above the restaurant. I have fixed this case on the map for you. |
| 126652301 | about 3 years ago | Hi pabi12, this is another case where the entire building is not the poi so its best to place the poi in a node instead and leave the building as is since there are offices in the floors above the restaurant. I have fixed this case on the map for you. |