Trip database list support for imported *polygons*
Originally from ticket #16184.
I imported property parcel polygons from a .kmz file so that I can avoid trespassing on private property. They show up on the map okay (in the default color), but could use just a simple, additional feature enhancement:
Please allow *polygons* to be listed, named, re-colored and deleted in the trip database interface, just like the waypoints and tracks.
Thanks!
-- Will Bain
-
Full disclosure: Not only do I *like* this, but I'm the guy who requested it.
I download county cadastral shapes in .kmz format and import them into BCN so that I can avoid trespassing on private property. BCN has lists for waypoints and tracks, which are great, and the polygons show up on the map, which is also great, but there isn't a separate list for them, and they don't seem to show up for me in the other lists, even as tracks. I would love to be able to manipulate them in a separate list. Just my 2¢.
In any case -- this is already the most *amazing* app one could have on a mobile device. Thanks!
0 -
I would also like to have a Settings Display option that allows me to turn off labels for polygons, just like waypoints and tracks. And, while you are at it, obey the fill color setting from the .KML file.
0 -
Well... me too!
Importing a "polygon" from Google Earth shows up after import, but the object does not show on the Tracks or Waypoint list.
Is there some way to work around this?
0 -
I second the motion and call the vote! Make it so.
To add to this FR, we need options to set OPACITY, WIDTH, and COLOR of the imported outlines. Currently, the import IGNORES the KML <line_width> tag and I discovered that the color parameters in the KML are INVERSE of what BCN wants. And BCN ignores the opacity/A value. IOW, KML defines color as ABGR (alpha, blue, green red), but BCN uses RGB. For example, a 50% red line in KML = 7F0000FF (hexidecimal values), where as BCN reads the 7F 50% alpha value as medium red and ignores the last hex pair of FF, which is the actual KML pure red color. Likewise, BCN sees a red line in KML as blue.
Related to this is the fact that BCN displays such imported polygon edges at 50% opacity (semi transparent), rather than 100% (solid) and with a VERY thin line that's actually made up of a row of jagged triangles instead of a solid, thick line. This makes the outlines VERY difficult to see, especially on satellite imagery-based maps.It would be nice, also, to have the option to scale and set opacity of the GPS Pointer, too, not just fill and outline color.
The NAMES of the polygons are nicely and smoothly rendered around the perimeter of the polygon, but are in black text that, again, is very hard to read on sat. imagery, SO an option for TEXT COLOR is needed for ALL labels (polys, waypoints, tracks, etc.).
0 -
Guess what? As of version 6.7.7 (released 5/4/2018), imported polygons/lines are now displayed in the Tracks List panel!!!! They can be enabled/disabled or selected and deleted, moved to another trip DB, etc.!!!
Yay to Nathan for adding this MUST HAVE management ability!
I created the complex polygon shapes of Class G and C airspaces in my "home region" surrounding Chattanooga, TN in KML format and imported to be an overlay on all the topo and sat. imagery maps! The US Airspace Sectional map provided by the FAA just isn't granular enough for the low and slow flying I do in my ultralight... I need the resolution that zoom 15:16 gives for roads and terrain available in the other maps. So now I have the outlines of the Class C airspace I fly under and Class G I fly over and in displayed on these higher rez maps.
0 -
Is there any plans to add polygon fill and transparency/opacity adjustment? Currently KMZ polygons only show as outlines.
0
Please sign in to leave a comment.
Comments
6 comments