We get our unit boundary data directly from FWP every spring, so I would suspect that the data they are sending us is showing the pre-2013 river channel as well. I'll pass this along to our geospatial folks and see if they can reach out to FWP to see if they have a more up to date boundary for...
Apologies for the trouble there! We have heard some reports from other users of the black screen issue you experienced there. The dark screen issue does not seem to be caused by tracking or any actions you undertook on your end. Our engineers are working on fixing that issue as soon as possible.
It sounds like that import may have been affected by inconsistent Wi-Fi. We recommend giving us a call, that will be the best way to diagnose the root cause of the issue and get everything straightened out. Our number is (406) 540-1600
Unfortunately, we've run into some unforeseen issues with Android Auto and the Google approval process. At this time, it does not look like we'll be able to release Android Auto for this hunting season. We're as disappointed in this as as you are. We are still committed to getting Android Auto...
I would recommend reaching out to our Customer Support Team, they will be able to go over the options available to you. Their email is [email protected] and phone number is (406) 540-1600.
We have reached out to Fort Riley in the past to try to acquire that hunting unit/safety zone information, but they have been unable to provide it to us. If/when they make the data available to us, we will be sure to get it included in the onX map.
We will try to send another request to see if...
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...
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...
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...
We would love to be able to confidently label all roads as public or private, but unfortunately, there is not currently a good, reliable data source that exists to show whether a given road is public or private. Oftentimes, government agencies are not able to tell for sure which roads are public...
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.
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...
As @WapitiBob has mentioned, the new imagery options are only available on the Web Map at this time, but we are working to make them available on iOS and Android as well.
As some folks have noticed here, we have recently come out with a couple of new imagery options. Imagery on Demand, which is currently being released allows onX users to order a custom, high resolution image for a particular area. This is an image that only the user that ordered it has access to...
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.