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

No way to detect 'No geometries found' errors #35

Closed
hyperknot opened this issue Mar 24, 2016 · 5 comments
Closed

No way to detect 'No geometries found' errors #35

hyperknot opened this issue Mar 24, 2016 · 5 comments

Comments

@hyperknot
Copy link
Contributor

On the attached file, fastkml throws a warning message: 'No geometries found' from Placemark / from_element.

At the moment, there is no way to detect this error scenario, so a gpsbabel cleaning could run. It'd be important to raise an error and not just log a warning in such case.

kml.zip

@IanLee1521
Copy link
Contributor

Any chance you might be willing to replace the attached zip with a link to a gist?

@hyperknot
Copy link
Contributor Author

That's a 200 kb, 5000 line long file, if you'd really like I can put it up, but I'm not sure it's a good idea.

@hyperknot
Copy link
Contributor Author

I did a PR which allowed me to detect the parsing error, might not be the thing you'd like in the library, but at least it signals that the file isn't working in fastkml.
#36

@hyperknot
Copy link
Contributor Author

Found a smaller example file, uploaded to gist:
https://gist.github.com/hyperknot/2fc06a3fecb98f07f761

@hyperknot
Copy link
Contributor Author

hyperknot commented Apr 16, 2016

Found out the real issue here is not supporting gx:Track elements (#37), closing this one.

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