When I use the Outdooractive web page to export a route to GPX file, the Hammerhead dashboard fails to import this file.
That is because the file includes an 11-line </metadata> block. I have to manually delete the 11-line metadata block before Hammerhead will accept the GPX file.
GPX is based on XML -- the eXtensible Markup Language. So Hammerhead import should not fail just because Outdooractive have eXtended the Markup Language implementation to provide a new custom tag. Hammerhead should quietly ignore unfamilar tags, and continue with the import as best it can.
Ask for help, find useful guides, or help others out with their issues.
1 post • Page 1 of 1