Betreff: Extracting the metadata in a useful format

on ‎04-18-201902:36 PM

@dzeek Sure, the initial post of this thread covers how I built my setup. I am not a golang developer and had almost no idea what I was doing, so it's very chaotic and probably not the best approach. Also, many thigs have changed since then. My current setup is:

%USERPROFILE%\go\src\github.com\

There I have a folder for each of the github accounts I use dependencies from: juanirache, stilldavid, paulmach and so on. Within each of those folders are the repos I depend on, and my own repo.

%USERPROFILE%\go\src\github.com\paulmach\go.geo

I currently use the VSCode text editor for other stuff and some of its plugins manages the imports the repo needs automatically. Not sure if that'd be easier to setup than doing it manually from my instructions. I didn't know Github either, back then, so it's pretty embarrassing to read my post now. But I guess that might make it understandable to noobs like I was.

I still use whatever dependencies are listed in my repo, hadn't noticed that one was deprecated.

Re: Extracting the metadata in a useful format

on ‎05-12-201903:42 AM

Thanks, glad you like it :).

The negative height occurs because the raw height data is not based on sea level. Negative vertical speed is normal, it just means you were going down (quite fast apparently, although the peak speeds often are exaggerated by small inaccuracies).

I would like to adjust the heights to sea level at some point, but for now my priority for the little time I can spare would be refactoring the tools in JavaScript. I'm not a Golang developer, so every new feature is painful to add and my implementations are not ideal.

So if anyone here has experience working with binary data in JavaScript, their help is very much welcome. Once we solve this, new features should be much easier to implement.