OddlyAngled's Comments
| Changeset | When | Comment |
|---|---|---|
| 171144386 | no problem at all, just update the hours and upload - the same process you followed for this change - they are immediately published. reviews are after the fact and best effort by the community. I have a feed setup in osmcha for changes in Kings Canyon and usually take a peek within a few days or weeks. others do something similar. anyhow welcome to OSM and thanks for your contribution :-) |
|
| 171144386 | are the hours correct on the Grant Grove Visitor center? the website says 8-5 in the summer https://www.nps.gov/seki/planyourvisit/visitorcenters.htm
|
|
| 171101221 | Hi, welcome to OSM. Aside from adding comments or sending a message there isn’t a way of suggesting a change- when you change the map it takes effect immediately. Applications that use the OSM database typically update much less often. It will take weeks to months (or sometimes years) for a small change like this to get propagated everywhere. For example Caltopo does an update 2-4 times a year. Gaia used to do it every couple weeks but has slowed down significantly. So be patient. Generally speaking it is often better to use access tags (like access=no) and lifecycle prefixes (closed:highway=path) to prevent a way from being used and showing up on a map. In this case deleting it is probably fine though but a discussion on the original changeset changeset/59557696 would have been a good place to start. The author has been working on tagging climbing routes and is pretty active. Thanks again for the contribution and let me know if I can help with mapping trails around the park |
|
| 170797500 | are these ranks defined somewhere?
|
|
| 170503642 | if this alternate isn't an official trail (like a ducked route around snow) please add informal=yes and a sac_scale= (if suitable). thanks for the update!
|
|
| 170587849 | for meadow restoration consider using the `closed:highway` lifecycle prefix and/or tagging access=no. the old trail will show up on satellite and gps heatmaps for many years and often get mapped as new trails again and again when they are deleted.
|
|
| 170637090 | hi! the trail updates look to be a bit further off than the current Strava heatmap + 3DEP LiDAR data implies. was there an issue on the ground with the existing path? satellite is often misaligned around this part of the park
|
|
| 170452844 | if the distinction matters, these are often used for days or more as a base camp for day rides, and subjectively much less often (if at all) as a temporary overnight stop on a longer packing trip. |
|
| 170452844 | the ones I am familiar with are normal car camping campgrounds with paddocks in the vicinity. there are more of these in Inyo NF too. maybe a camp_site=stock tag would be appropriate? there has been some effort to standardize on this key for different types of camps |
|
| 170311734 | I made an attempt to clean up the relation and associated way tags. This is a common problem around here. |
|
| 169178489 | this tool doesn't work properly for waterway relations, e.g. relation/14901375 should have gotten the wikidata tag instead of way/291349401 and Mine Creek was already tagged relation/16718618. it would be awesome if the tool could be fixed to deal with river and stream relations
|
|
| 167597224 | thanks for the contribution - a couple suggestions: access=no will exclude horses (and bicycles). removing access= and adding vehicle=no might be better here. consider adding barrier=debris (or another barrier= value) to a node where the dozer pile is located
|
|
| 167501705 | until trails disappear from most recent satellite imagery and gpx heatmaps it is usually better to use the access tags or a closed: lifecycle prefix on the highway tag. in Yosemite it is pretty common for deleted paths to come back to life by helpful armchair mappers.
|
|
| 165248255 | looks like this inadvertently tagged all of Mariposa as a swimming pool way/33207307 |
|
| 166490310 | could you try to add more descriptive comments to these changesets in the future? it helps a lot with reviews and saves us all time. thanks for the consideration and happy mapping!
|
|
| 166713957 | please take a look at osm.wiki/Hiking - hiking routes should be official trails (not use trails), and the relation members should use defined roles like "main" or "approach". I'm not sure what "path" and "way" mean. some relation validator will flag these. also make sure to keep the informal=yes tag, it looks like it was removed. this helps with many renderers and routers. it also looks like the gps data was imported and could use some clean up. I find that a combination of LIDAR data (Yosemite has great coverage in 3DEP) and aggregated GPS tracks, like Strava, in combination with my own tracks helps quite a bit with determining the true path on the ground. thanks for the contribution.
|
|
| 166544887 | I updated the operator tags |
|
| 166544887 | I updated it to the JMT Conservancy since it seems more accurate, but there is no single authority. originally the trail was sighted north to south, starting in Sequoia. more traditionally it is hiked starting in Yosemite. four different organizations can issue permits for travel along the JMT, five if you include the portion that overlaps with the PCT. but no permits are JMT specific - they set entry trailheads, with few exceptions on which trails can be hiked or where you can camp. |
|
| 166544887 | there is also the JMT Conservancy https://jmtwilderness.org/. aside from the portions of the PCT that coincide with the JMT I don’t know if the PCTA is the most specific organization in charge, if one is at all
|
|
| 161218949 | Hi, natural=wood is all that is needed to mark an area as a forested area. The name tag should only be used if the forest has a specific name - otherwise add additional detail to the description or note tags. Thanks for the contribution! |