Zsolt Ero

@DamnWidget I've opened a separate ticket for 2.1.17 as it's a totally unrelated issue I believe. https://github.com/DamnWidget/anaconda/issues/632

I was thinking about it a lot. Advantages: - npm upgrade works without looking up releases in GitHub Disadvantages: - Why is NPM special, over PIP or Ruby gems or...

@bkmgit overpass turbo cannot return land-extracted polygons, as in GeoJSONs with boundaries on land, not water. Wambacher's website was the only one doing this, but unfortunately it is down, and...

I started making a new custom pipeline in https://github.com/hyperknot/osm-admin-extracts, which hopefully will be a replacement for Wambachers once it's ready.

Thanks for reporting this! I think we'll need to add a center override in a new file `fixes/center.json`, as dayline breaks the centroid function.

I added the change to the scoring rules here: https://github.com/hyperknot/igc-xc-score/blob/6bca0fe83ed608a09261b2eb8eab982f4ce5e167/scoring-rules.config.js#L124 My problem is that it's not doing the optimal calculation. The best point would not be on the track, but...

Sure, it's here: https://www.fai.org/sites/default/files/civl/documents/sporting_code_s7_d_-_records_and_badges_2022.pdf It's not an easy read, but I believe it's like on my drawing:

Yes. But for the turnpoints it makes no sense to make them cylinders, it's easier to calculate them as points. The trick is the start/end cylinder.

I think a straight 800 meter line is not optimal. The optimal solution would be a "buffer" operation around both polylines and then finding the furthest point on this polygon.

It's very close to optimal but not optimal. I don't know how much we want to optimise those few meters though. I made a Geogebra sketch. The left point is...