0.9.7

Fixed

• Name of background job to calculate visits

Full Changelog: 0.9.6...0.9.7

0.9.6

Fixed

• Map areas functionality

Full Changelog: 0.9.5...0.9.6

0.9.5

Added

• A possibility to create areas. To create an area, click on the Areas checkbox in map controls (top right corner of the map), then in the top left corner of the map, click on a small circle icon. This will enable draw tool, allowing you to draw an area. When you finish drawing, release the mouse button, and the area will be created. Click on the area, set the name and click "Save" to save the area. You can also delete the area by clicking on the trash icon in the area popup.
• A background job to calculate your visits. This job will calculate your visits based on the areas you've created.
• Visits page. This page will show you all your visits, calculated based on the areas you've created. You can see the date and time of the visit, the area you've visited, and the duration of the visit.
• A possibility to confirm or decline a visit. When you create an area, the visit is not calculated immediately. You need to confirm or decline the visit. You can do this on the Visits page. Click on the visit, then click on the "Confirm" or "Decline" button. If you confirm the visit, it will be added to your timeline. If you decline the visit, it will be removed from your timeline.
• Settings for visit calculation. You can set the minimum time spent in the area to consider it as a visit. This setting can be found in the Settings page.
• POST /api/v1/areas and GET /api/v1/areas endpoints. You can now create and list your areas via the API.

⚠️ Visits functionality is still in beta. If you find any issues, please let me know. ⚠️

Fixed

• A route popup now correctly shows distance made in the route, not the distance between first and last points in the route.

What's Changed

• Bump tailwindcss-rails from 2.6.1 to 2.6.3 by @dependabot in #136
• Bump turbo-rails from 2.0.5 to 2.0.6 by @dependabot in #135
• Areas and visits by @Freika in #131

Full Changelog: 0.9.4...0.9.5

0.9.4

Added

• A popup being shown when user clicks on a point now contains a link to delete the point. This is useful if you want to delete a point that was imported by mistake or you just want to clean up your data.

Fixed

• Added public/imports and public/exports folders to git to prevent errors when exporting data

Changed

• Some code from maps_controller.js was extracted into separate files

Full Changelog: 0.9.3...0.9.4

0.9.3

Added

• Admin flag to the database. Now not only the first user in the system can create new users, but also users with the admin flag set to true. This will make it easier to introduce more admin functions in the future.

Fixed

• Route hover distance is now being rendered in kilometers, not in meters, if the route distance is more than 1 km.

First user in the system will receive the admin flag upon the application start after an update to 0.9.3. You can also make any other user an admin using this instruction: https://dawarich.app/docs/tutorials/FAQ#how-to-make-a-user-an-admin

What's Changed

• Admin flag and closing sidekiq interface by @Freika in #130

Admin users will see a shining star next to their email in the navbar:

Full Changelog: 0.9.2...0.9.3

0.9.2

Fixed

• Hover over a route does not move map anymore and shows the route tooltip where user hovers over the route, not at the end of the route. Click on route now will move the map to include the whole route.

Full Changelog: 0.9.1...0.9.2

0.9.1

Fixed

• Fixed a bug where total reverse geocoded points were calculated based on number of imported points that are reverse geocoded, not on the number of total reverse geocoded points.

Full Changelog: 0.9.0...0.9.1

0.9.0

Added

• Background jobs page. You can find it in Settings -> Backgroun Jobs.
• Queue clearing buttons. You can clear all jobs in the queue.
• Reverse geocoding restart button. You can restart the reverse geocoding process for all of your points.
• Reverse geocoding continue button. Click on this button will start reverse geocoding process only for points that were not processed yet.
• A lot more data is now being saved in terms of reverse geocoding process. It will be used in the future to create more insights about your data.

Changed

• Point reference to a user is no longer optional. It should not cause any problems, but if you see any issues, please let me know.
• ⚠️ Calculation of total reverse geocoded points was changed. ⚠️ Previously, the reverse geocoding process was recording only country and city for each point. Now, it records all the data that was received from the reverse geocoding service. This means that the total number of reverse geocoded points will be different from the previous one. It is recommended to restart the reverse geocoding process to get this data for all your existing points. Below you can find an example of what kind of data is being saved to your Dawarich database:

{
  "place_id": 127850637,
  "licence": "Data © OpenStreetMap contributors, ODbL 1.0. http://osm.org/copyright",
  "osm_type": "way",
  "osm_id": 718035022,
  "lat": "52.51450815",
  "lon": "13.350110811262352",
  "class": "historic",
  "type": "monument",
  "place_rank": 30,
  "importance": 0.4155071896625501,
  "addresstype": "historic",
  "name": "Victory Column",
  "display_name": "Victory Column, Großer Stern, Botschaftsviertel, Tiergarten, Mitte, Berlin, 10785, Germany",
  "address": {
    "historic": "Victory Column",
    "road": "Großer Stern",
    "neighbourhood": "Botschaftsviertel",
    "suburb": "Tiergarten",
    "borough": "Mitte",
    "city": "Berlin",
    "ISO3166-2-lvl4": "DE-BE",
    "postcode": "10785",
    "country": "Germany",
    "country_code": "de"
  },
  "boundingbox": [
    "52.5142449",
    "52.5147775",
    "13.3496725",
    "13.3505485"
  ]
}

What's Changed

• Added Caddy instructions to reverse proxies doc by @tylwright in #116
• Added Discord badge to README instead of link by @tylwright in #117
• Update README.md with a link to Google Maps Timeline wiki page under Ho… by @tylwright in #119
• Background jobs by @Freika in #114

New Contributors

• @tylwright made their first contribution in #116

Full Changelog: 0.8.7...0.9.0

0.8.7

Changed

• Added a logging config to the docker-compose.yml file to prevent logs from overflowing the disk. Now logs are being rotated and stored in the log folder in the root of the application. You can find usage example in the the repository's docker-compose.yml file. Make sure to add this config to both dawarich_app and dawarich_sidekiq services.

  logging:
      driver: "json-file"
      options:
        max-size: "100m"
        max-file: "5"

Fixed

• Visiting notifications page now marks this notifications as read

Full Changelog: 0.8.6...0.8.7

0.8.6

Added

• Guide on how to setup a reverse proxy for Dawarich in the docs/how_to_setup_reverse_proxy.md file. This guide explains how to set up a reverse proxy for Dawarich using Nginx and Apache2.

Removed

• MAP_CENTER env var from the docker-compose.yml file. This variable was used to set the default center of the map, but it is not needed anymore, as the map center is now hardcoded in the application. ⚠️ Feel free to remove this variable from your docker-compose.yml file. ⚠️

Fixed

• Fixed a bug where Overland batch payload was not being processed due to missing coordinates in the payload. Now, if the coordinates are missing, the single point is skipped and the rest are being processed.