Xvtn's Comments
| Changeset | When | Comment |
|---|---|---|
| 137936234 | Hi, and welcome again to OpenStreetMap! Your edits look good overall, but since you've asked for review, here are a couple of tips:
As always, thanks for your contributions! |
|
| 137938399 | Also, welcome to OSM!! :) |
|
| 137938399 | Just a tip, when drawing rectangular features in iD you can press "Q" to square up their corners. This makes them look much better when rendered. |
|
| 137815375 | Nice, thanks!! And that makes sense for the stop number. I agree that it should be what's marked on the sign. |
|
| 137815375 | That bus stop path by the Family Life building is new enough to not be on some satellite imagery, or maybe they really did tear it out!? (right on the highway there) |
|
| 137802448 | For my own use of that ivm resource in the future, is there some way to know on there whether a road is publicly accessible or private access only? Or maybe local knowledge, street-level images, etc. are required too like you say... |
|
| 137802448 | Got it. Thanks for the detailed explanation! I had no idea such huge swaths of technically USFS-included land were privately owned. I knew there are some public rights-of-way through private chunks, but didn't know the scale of it. |
|
| 137792304 | Nice catch!
|
|
| 137802448 | These are mostly on forest service land, right? I was under the impression that most FS land is at least accessible by foot or horseback. Or does the pipeline have something to do with it? |
|
| 136515198 | Sorry for the duplicate questions. See my comment on your other changeset. |
|
| 136608576 | Gotcha, thanks for clarifying. I think that would be good to specify that somehow in the future, if you aren't already done bringing them in. Also, doesn't the lack of tags like fuel:octane_86 imply an "unknown" status without having to explicitly say it's unknown? |
|
| 136515198 | Do you have a link to this import discussion page? What's the source on this data? |
|
| 136608576 | What's the source for this import? Can you link to the required automated edit discussion page? |
|
| 137347089 | Oops, sorry for the huge bbox!! I normally put a lot of thought into preventing that from happening. |
|
| 136192657 | There is already a node for CAL Ranch here, but it's a shop=country_store. I think shop=clothing could make sense too though. |
|
| 136106403 | I've updated the instructions to include a QA step and a more specific list of changeset tags to use. https://github.com/lint3/cachevalley-address-import-osm#readme) |
|
| 136106403 | You're right - that's my mistake. `import:merge` is a tag I was using internally for items where I was unsure if they could be merged with existing features using only assumptions made based on geometry/location. (The vast majority of features can be merged based on that assumption.) I should have removed that tag before uploading. I'll fix that asap. Also, I'm not sure how I missed the fact that I'm supposed to be linking to the documentation. It definitely makes sense to do that and I'll include it in future changesets. Documentation is here: osm.wiki/Utah/CacheValleyAddressImport |
|
| 135977767 | Oh no! They were my comments!! Sorry, I thought this was more of the previous type of edits combining prefix, etc. Thanks for reviewing this past work!! |
|
| 135977767 | These changes you've made are reversing work done toward following this standard: osm.wiki/Utah/Naming_Conventions What comments are you referring to as your source? ***These roads are signed on the ground without any directional prefix.*** Both the way locals refer to the streets, and the way they are signed in real life is "1000 North", etc. |
|
| 135749085 | Are you sure about these changes? I was here a while ago and talked to a nearby resident, they said public motor vehicle traffic is not allowed in that whole area. Has something changed? |