aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2023-03-28fix import orderDaniel Schadt
2023-03-27use fietsboek.ini as default configDaniel Schadt
This makes it easy to use the scripts without always having to specify -c. The error message could be a bit better if fietsboek.ini is not found and -c is not given, maybe we can fix that later.
2023-03-27profile: add longest and shortest trackDaniel Schadt
2023-03-27profile: move cumulative stats to helper classDaniel Schadt
The reason for that is that we want to add "longest track"/"shortest track" soon, and the profile() function is getting a bit long
2023-03-25add documentation about DockerDaniel Schadt
2023-03-25add an initial DockerfileDaniel Schadt
2023-03-25first integration of hittekaart into fietsboekDaniel Schadt
This makes it a bit easier to generate heatmaps, but at the moment, it only works manually. The "long-term" goal is to have fietscron generate heatmaps on a regular basis.
2023-03-25profile: take into account all tracksDaniel Schadt
With the previous logic, we only counted those that the user themselves uploaded.
2023-03-25use own i18n strings for profile pageDaniel Schadt
2023-03-25add number of tracks to profileDaniel Schadt
2023-03-25profile: show first base layer per defaultDaniel Schadt
Otherwise it does look very empty when you open the page.
2023-03-25add docstringsDaniel Schadt
2023-03-25show heatmap on profileDaniel Schadt
So far, fietsboek does not generate them, but if you happen (by accident) to have hittekaart output a heatmap to the right location, the profile page will now show it.
2023-03-25first scaffolding for profilesDaniel Schadt
2023-03-25rename profile to user-dataDaniel Schadt
This is not really a profile page, but rather a page to change your personal data, so it should be named accordingly (in preparation for real profiles). Additionally, we use POST requests to deal with the data change.
2023-03-25fix eslint CI jobDaniel Schadt
Turns out you need to supply an actual empty array. While we're playing with the CI configuration, we also move the deprecated global image/cache/before_script sections into the "default" section.
2023-03-25run eslint on the CIDaniel Schadt
2023-03-25ignore compiled js and css files in linguistDaniel Schadt
2023-03-24move (most of the) JavaScript code to TypeScriptDaniel Schadt
Yay, types! (And a lot of escape hatches)
2023-03-23rewrite fietsctl to use clickDaniel Schadt
This makes it consistent with the other scripts (fietsupdate, fietscron), and makes the argument parsing setup a bit nicer to read.
2023-03-22add documentation about SASS and JSDaniel Schadt
2023-03-22use sass for the CSS filesDaniel Schadt
2023-03-22use npm to manage Javascript librariesDaniel Schadt
I'm not the biggest fan of combining many package managers, but the JavaScript libraries (Bootstrap, Bootstrap-Icons, later the @types modules and Leaflet) are easy to get via npm, so maybe we can use that to our advantage and have npm at least download them.
2023-03-08bump version to 0.6.0v0.6.0Daniel Schadt
2023-03-08update dependenciesDaniel Schadt
2023-03-08update changelogDaniel Schadt
2023-03-08adjust release checklist for Python 3.9Daniel Schadt
2023-03-07wait until accordion is expandedDaniel Schadt
Currently, the test seems flaky on CI due to playwright._impl._api_types.Error: Clicking the checkbox did not change its state Maybe this is the change that will fix it?
2023-03-07tests: use .check() instead of .click()Daniel Schadt
This gets the intent across clearer
2023-03-07disable cache for transformer testsDaniel Schadt
2023-03-07fix duplicated importDaniel Schadt
2023-03-07update changelogDaniel Schadt
2023-03-07Merge branch 'transformers'Daniel Schadt
2023-03-07switch order of expect & assertDaniel Schadt
While it shouldn't change the outcome of the test, it might make the test less flaky, as the expect call will wait until the page is loaded - which also indicates that the data is updated. Without this, the test depends on the backend being "fast enough" with applying the transformation.
2023-03-07fix typo in log messageDaniel Schadt
2023-03-07add some documentation about transformersDaniel Schadt
2023-03-07also test transformers when editing a trackDaniel Schadt
2023-03-06implement rollbacks on the data directoryDaniel Schadt
This helps if the upload/editing process fails, so that we don't end up with orphan data directories (probably the most important change!), or superfluous image files.
2023-03-04fix deprecated SQLAlchemy functionsDaniel Schadt
Getting ready for SQLAlchemy 2.0!
2023-03-04add tests for the new transformerDaniel Schadt
2023-03-04transformers: de-duplicate fixup codeDaniel Schadt
2023-03-02FixNullElevation: also take into account slopeDaniel Schadt
For some reason, I have GPX tracks that have the first two points be ~100 meters apart in elevation, but only ~20 meters apart in distance. This is quite unrealistic and produces pretty bad height plots (almost as bad as the zero elevation). Since the issue is very related, and the fix is pretty much the same, I thought it would be a good idea to adapt the FixNullElevation transformer to handle this case as well. For reference, "the internet" says that the maximum slope for a MTB is ~15% to ~35%, depending on the conditions - with 35% being pretty steep. I think it's fair to throw away elevations that exceed 100% (basically a 45° angle upwards), especially since we only discard them at the start and end.
2023-03-02fix lintDaniel Schadt
2023-02-21rework transformer parameter UI logicDaniel Schadt
I don't like interweaving the HTML code into the business logic, so now we can have that in the Jinja template. Ideally, the list of definitions would be generated automatically from the model attributes.
2023-02-15try to avoid parsing the GPX more than onceDaniel Schadt
2023-02-15properly rebuild cache after changing transformersDaniel Schadt
2023-02-15implement null-elevation-fix transformerDaniel Schadt
2023-02-15actually save transformed GPX after uploadDaniel Schadt
2023-02-15Merge branch 'max-tile-connections'Daniel Schadt
2023-02-14remove {abc} tile server prefixDaniel Schadt
Those prefixes mainly exist to help browsers with their per-domain connection limit [1]: > Subdomains are used to help with browser parallel requests per domain limitation For us, we don't care about that limit, because we do not implement it (server side at least). It's even better to not have those domains, as otherwise our new connection limitation will get confused. We might think about adding them back if the tile proxy is disabled, but for now they seem to serve no purpose for us. [1]: https://wiki.openstreetmap.org/wiki/Raster_tile_providers
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 00:28:37 +0000