Some of this is because of how the GPS is collecting data. If someone goes out and makes a route and the route says '20 miles' it might only be 17 or 18. Something else to be aware of is user defined data. When they change hands or get divided or donated, it's up to the local authorities to get that info into the databases, and that would be entirely on them as far as speed of that. But the privately owned lands are a different story. This is why sometimes you might see a data lag when adding a layer to your basemap.īoundaries tend to be a lot more stable, such as those for National Parks and National Forests. Again, this is very similar to how I work, at least part of the time. I'm not in the app side of the business, but from how I work with the same data, I can just about be sure that what is going on is that the data is being pulled per user and added as a layer. So that means if you are viewing data a few months old, some gates may be locked that were not, trails are now closed, or some new ones are open. I'm not entirely sure how often they are updated, but lets just toss out 'once per year'. I have (well, you as well) access to all the NF MVUM routes, for instance. The data is only as good as how it is collected and updated.

However, I've been doing this professionally since 2004 and have seen how much of this has progressed.Ī lot of this overlay data is freely available from different US Federal and state organizations and then incorporated into a basemap on various GPS apps. Now, bare in mind, I am talking in very general terms so this is not 100% across the board. I want to expound on what something that Catastrofe mentioned and 1Louder has described.

Download onx backcountry