Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem intrepreting kml files #32

Open
latot opened this issue Feb 10, 2021 · 1 comment
Open

Problem intrepreting kml files #32

latot opened this issue Feb 10, 2021 · 1 comment

Comments

@latot
Copy link

latot commented Feb 10, 2021

Hi hi, I found some issue regarding the kml format, at least in my very few testings:

  • The polygons and lines don't use the right color, I see all in blue even if they should be ones red and others green.
  • At least, the description tag is not detected, when I click a point and check the details, there is no description loaded from the kml
  • Polygons don't works right, while we can use points, so we click a point to see the description, when we have polygon, a surface, when we click it nothing happens, we need to click a point in a corner, but is hard to know what polygon we are clicking when they are several side by side.

With this type of error, maybe the kml format is not fully implemented, but is pretty useful anyway to can see the map, I think wold be great have all of this working.

Tested in 19.2 (363d)

Thx.

@activityworkshop
Copy link
Owner

Some of these reported issues come from a mismatch of expectations - GpsPrune isn't a general-purpose KML viewer / editor and doesn't try to support all of KML's features. GpsPrune is intended to view and edit coordinate data (like GPS tracks) and can load such data from KML as well as other data formats (like GPX, TXT, CSV, NMEA). So polygons can be shown as tracks, but areas and surfaces just aren't concepts which GpsPrune can represent with a series of points.

  • GpsPrune doesn't store the color of each point or line, so it will ignore these if they are specified in KML. Instead, GpsPrune has its own, flexible coloring rules based on segment, track, altitude or other criteria. You can find these under Settings -> Set colors, especially the "Point colorer" section.
  • Points can have descriptions, so depending on how they're stored these should be loaded. For example, the "description" of a "Placemark" is loaded and shown correctly. If this doesn't work for you, please attach an example.
  • GpsPrune doesn't have any concept of surfaces, just the points and the connecting lines between them (if they're in the same segment). So for sure these can be represented in KML files, but they are not supported by GpsPrune.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants