Exporting GPS track problems

It seems to be fixed now.
If you run into this issue in future, you can also convert FIT files to GPX here: http://www.gpsvisualizer.com/

I can't get any activities to export since I started trying on Friday (I think). I have tried in Safari and Chrome and get this same message.

Two of three new tracks generate Tomcat errors

I've just synched my Edge 605 and uploaded three tracks, I can export the second one but the first and third generate tomcat errors
type Exception report

message

description The server encountered an internal error that prevented it from fulfilling this request.

exception

java.lang.NullPointerException
com.garmin.connect.service.download.activityexport.provider.ActivityGpxSerializer.buildDocument(ActivityGpxSerializer.java:73)
com.garmin.connect.service.download.activityexport.provider.ActivityGpxSerializer.serialize(ActivityGpxSerializer.java:36)
com.garmin.connect.service.download.activityexport.provider.ActivityProvider.writeTo(ActivityProvider.java:38)
com.garmin.connect.service.download.activityexport.provider.ActivityProvider.writeTo(ActivityProvider.java:21)
com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:306)
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1448)
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1360)
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1350)
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:538)
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:716)
javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
org.springframework.security.oauth.provider.filter.ProtectedResourceProcessingFilter.onValidSignature(ProtectedResourceProcessingFilter.java:87)
org.springframework.security.oauth.provider.filter.OAuthProviderProcessingFilter.doFilter(OAuthProviderProcessingFilter.java:168)
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:214)
org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:177)
org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:262)
com.netflix.hystrix.contrib.requestservlet.HystrixRequestContextServletFilter.doFilter(HystrixRequestContextServletFilter.java:53)
note The full stack trace of the root cause is available in the Apache Tomcat/7.0.57 logs.

Hi,

I have a GPS track at https://connect.garmin.com/modern/activity/1388462985. I cannot export them; they either crash the Apache browser or simply don't work. Is there a way I can extract this data.

Thanks

Worked for me.

One error I notice when I export to KML format is a bug that causes the first two point to land somewhere in the sea near the middle of Africa. I have to delete these points in Google Maps.

Worked for me.

One error I notice when I export to KML format is a bug that causes the first two point to land somewhere in the sea near the middle of Africa. I have to delete these points in Google Maps.

Mostly likely because you started recording the activity before the a full GPS lock was established (regardless of what your watch indicated). In those cases the file on the watch doesn't record any lat/long coordinates, and for some inexplicable reason the export to GPX function on Garmin Connect converts this lack off lat/long into 0,0 coordinates which is just off the west coast of Africa.

One work around is to use Garmin's Basecamp software which will ignore those data points, but you then lose any other data recorded in those points (ie, temp, heart rate, etc).