We will soon be coming out with a feature that will let you accomplish this. I don't have an ETA for you on it, but we've been testing it in the office and it is a pretty handy feature. I can say that we are currently planning to release that update sometime this summer, barring any unforeseen obstacles in the development process.
Your current waypoints won't be affected by any upgrades to your onX Membership. If you choose to go to an Elite Membership, your Colorado waypoints will not be affected.
At the present moment, there is not.
I understand the pre-caution, but the dataset that is now being relied upon appears to be quite inaccurate. The disappointing part is that the data used to be quite good and provide mostly accurate data in terms of access, yet blatant mistakes like these are detrimental to the trust in all data put forth by the application. I've attempted to use Mapbox's correction form and it is more frustrating finding these errors and having to go to the alternative data sources for confirmation. I know that the official data sources are to be verified for access, but seeing these more easily verifiable errors is troubling, MT HWY 360 for example appears in a simple Atlas. For the bit about influential landowners, South Bench Road access to the Little Snowy Mountains is peculiar with forest service access signs giving direction to it, and previously being on ONX. It was removed prior to changes in datasets and doesn't even appear as a "Private" road, thankfully the forest service has it marked from both directions.
Right now, we are at least two months out from Android Auto being ready to go. It could potentially be later than late July-early August, depending on how all the development and approval goes, but it is not likely to be available before that timeframe. Our goal is to have it ready before most hunting seasons kick off this fall. Probably not the response you were hoping to hear, but I want to give you as realistic of a timeline as possible.
Thank you for the further information and the context herre. That is very helpful. I've passed this along to our Mapping Team so that they can investigate further and see what they can do to better improve our roads data moving forward.
The data from my first post did get resolved, so submissions to the Mapbox website appears to have a positive result.
So everyone who has the app and a tablet, please download it on your tablet as well if you haven’t already. Landscape mode would be soooo helpful when sitting on the couch “watching tv” with the wife.
I would echo Shandon's concerns about road/trail data. I've hunted many areas in ND, MT, SD where the app showed a two track trail that wasn't there or showed a trail that was not open to public travel (non-motorized area or illegally established trail). Because it's shown on the map, people think it's GTG for public travel. In North Dakota, illegal motorized travel is a huge issue, not just in non-motorized areas, but on public land in general. I believe our local USFS office (Dakota Prairie Grasslands) has said they intended on discussing this issue with you folks to look for a solution, but I've never heard if they followed through with it. But it would help tremendously if there was confidence in OnX trail/road data being accurate. Has there been any discussion about changing symbology to show roads that are closed or not open for public travel and more effort towards QC to ensure the road data is accurate in terms of legal travel?
Aren't roads/trails and closures dictated by travel management plans and made available to the public via MVUMs? If there is an MVUM there has to be spatial data.
Yes and no. The USFS, for example, typically has very good data, and we have an MVUM layer within the app that shows that data. The BLM, however, does not have a similar dataset currently. We are hopeful that the funding coming from the MAPLand Act will help to get all of that data digitized and made publicly available so that we, and others, can build out much more detailed and accurate road maps in the future. (You can read more about the MAPLand Act here: https://www.trcp.org/mapland/) We are already starting to see some of that data come out. The first batch that we have received, and is now available to onX users is the Forest Service easement data. We're not able to dictate which data get's digitized and made available first, we just have to take the new datasets as they come in. The process of digitizing the data is quite labor intensive, and as such, the MAPLand Act gives agencies until 2026 to have that data digitized and made available to the public, so we expect it to take a few more years before we have a complete dataset for these roads and trails.
That discrepancy is most likely an issue with the county data that we received. To get this remedied, use the error reporting feature in the app to report this to our Mapping Team so they can investigate. For the steps to report an error, check out this article from our help center: https://onxmapssupport.zendesk.com/... the map feature that,button on the far right.
We definitely recommend using Chrome, and there are a couple of things to do to improve performance on your end. First, try clearing your cache and browser history. That can often improve performance. You can also make sure hardware acceleration is turned on. To do that, please follow the steps below.
Still a bit laggy but a million times better. I’ll keep messing with it and write to you guys if it doesn’t work out. Thank you!
