I have been playing around with the OnXMaps android app and noticed a discrepancy between boundaries published by the Utah Division of Wildlife Resources (UDWR) and the boundary in the OnX app. I contacted UDWR and as it turns out the UDWR boundary is correct. While an issue like this could be resolved by OnX; it is a reminder of why I really like the flexibility in BCN. In BCN I have the ability to import the correct boundary and only the boundaries I want.
Now here's the rub with BCN, I have had a feature request into BCN for a while to have the ability to turn on and off user created layers and/or boundaries. As it stands right now, if I import a boundary into a trip file I cannot delete that boundary. Rather I have to create a new trip file and transfer waypoints and tracks into the new trip file. Then I have to delete the old trip file. While this work around is functional, I look forward for the ability to turn on and off and delete user created layers/boundaries in BCN.