aweech's Comments
| Changeset | When | Comment |
|---|---|---|
| 108650711 | 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 highway=traffic_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 | 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 | Hi,
|
|
| 108532583 | Hi,
|
|
| 104537693 | Hi,
|
|
| 108351207 | Hi,
|
|
| 108349119 | Hi,
|
|
| 108348110 | Hi,
|
|
| 108347990 | Hi,
|
|
| 108347001 | Hi,
|
|
| 108346669 | Hi,
|
|
| 108144303 | Hi,
|
|
| 108326236 | Hi,
|
|
| 108327373 | Hi,
|
|
| 108211642 | Hi,
|
|
| 108079494 | Hi,
|
|
| 108000721 | Hi,
|
|
| 107979798 | Relations are discouraged for hotels and motels. Please see tourism=hotel for more information. There were at least 4 hotel/motels in Utah with more than one building that you missed this morning that I went and fixed. You can tell when a hotel/motel has more than one building based on the shape of the parking lot, the architecture of the buildings, and street level imagery. |
|
| 107990642 | This wasn't actually a survey. I meant to type "aerial imagery" but somehow "survey" ended up in there. |
|
| 107979798 | Hi,
|