-
Notifications
You must be signed in to change notification settings - Fork 89
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
Comments
Any chance you might be willing to replace the attached zip with a link to a gist? |
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. |
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. |
Found a smaller example file, uploaded to gist: |
Found out the real issue here is not supporting gx:Track elements (#37), closing this one. |
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
The text was updated successfully, but these errors were encountered: