aweech's Comments
Changeset | When | Comment |
---|---|---|
109479476 | almost 4 years ago | Hi,
|
109425075 | almost 4 years ago | Hi,
|
109425075 | almost 4 years ago | Hi,
|
109425654 | almost 4 years ago | Hi,
|
109389238 | almost 4 years ago | Hi,
|
109164476 | almost 4 years ago | Hi,
|
109160548 | almost 4 years ago | Hi,
|
108913719 | about 4 years ago | Hi,
|
108905573 | about 4 years ago | Hi,
Thanks again for you contributions in the Amherst/Nashua area, all the POIs you added look good! |
108842390 | about 4 years ago | Hi,
You also asked for a review on the changeset where you added the Spring House trail. We actually are allowed to use the Strava Heatmap to map things currently, so I improved the trail using that. One last thing, on the Lewey's Loop trail, you added the extra " - Foot Traffic Only" bit to the name. That info was already saved by the bicycle=no tag that you added, so I removed it. Thanks again for your contributions, and let me know if you have any questions! |
108650711 | about 4 years ago | Hi,
Regarding the ATSPM tags, I still haven't figured out what they mean. Creating new tags is totally fine, though, as that Wiki page says, they should be documented in the Wiki :) I'm guessing that the ATSPM tags might have something to do with the signed direction that the state route goes? If so, it is true that there isn't a widely accepted way to tag that yet. However, this summer we (as a United States community) have been discussing a scheme that would handle that, documented (as a draft) here: osm.wiki/User:Minh_Nguyen/Route_directions. If that is the sort of thing that you mean, I can talk to other mappers in Utah and see if there is interest in converting our state routes to this scheme. |
108833541 | about 4 years ago | The Girl Scout Camp is a great example of a business that should be on the map. They have a website where they advertise and rent out the place (before COVID). It was even properly tagged with access=private, meaning that only the GSU and their invited guests can visit. The Bonanza Flat Conservation Area is under fee ownership of Park City, so the ownership=private tag wouldn't be correct here. The easement does allow Park City to regulate access to the public land, and any place that has been signposted as closed should be tagged with access=private or access=no depending on if city employees/contractors use those areas. However, it is a matter of accuracy and safety that any trail that someone can see on the ground belongs in OpenStreetMap with the proper tags. If people are using trails that have been closed, I recommend that the City put signs up on the ground saying those trails are closed. Adding accuracy to names and regulations is much appreciated as oftentimes those get overlooked and have likely changed since the area became public land. There's a lot to do to improve the map in this area. Clumsy deletion of popular trails and access roads doesn't help. |
108833541 | about 4 years ago | Hi,
|
108696883 | about 4 years ago | Fixed in 108777770 |
108650711 | about 4 years ago | Hi,
First, the Wiki page for connectivity relations (osm.wiki/Relation:connectivity#How_and_when_to_use_connectivity_relations) says that they should be used for more complex intersections, so I don't think they should be used for these simple intersections. At the very least, I've never seen them used before like this. They're really not necessary unless there's many intersections in quick succession. Second, you've been adding a lot of duplicate stop light nodes. Please see osm.wiki/Tag:highway%3Dtraffic_signals#How_to_map for some instructions on how to map them, but, as it says, ideally each stop light would be mapped exactly once. In a simple 4-way intersection, that can be the intersection node. Where some of the streets are split, stop light nodes can go on the stopping lines with the proper direction tag (forward/backward). Third, you've been splitting ways at the stopping lines, and I can't figure out why. It'd be one thing if the tags were the same on each side of that split, but you've been setting them to different values, which isn't good intersection modeling. OSM tries to use a 1D data model in a 3D world, and there are some compromises we have to make because of it. Fourth, turn lanes should only be tagged where there is a turn lane. You've been tagging them hundreds of feet in either direction. I think that you've gotten better at not doing that over time though. Fifth, you've been using some older imagery. As I'm sure you know, this road has seen a lot of construction in the last few years, and lanes and layouts have changed. It's worth checking newer layers like Esri World Imagery or Maxar Premium to make sure the most up-to-date information possible is being saved. Sorry if this feels like a lot. You have been doing quite a bit here, and I wanted to catch it so that your future edits can be the best they can be :) |
108532583 | about 4 years ago | As the Wiki says, they should be tagged according to what sort of building it is. The building tag reflects the original use, so purpose-built hotels should be tagged with building=hotel. Hotels that are repurposed from other things (like a church or a house), would have a building tag like building=church or building=detached. If you don't know the history of the building, then building=yes is totally fine. |
108508964 | about 4 years ago | Hi,
|
108532583 | about 4 years ago | Hi,
|
104537693 | about 4 years ago | Hi,
|
108351207 | about 4 years ago | Hi,
|