Dawarich, a self-hosted web application offering an alternative to Google Location History, is experiencing significant issues with data import stability, particularly from Google Timeline and GPX files, as evidenced by recent user reports and open issues.
Recent issues highlight persistent challenges with data import functionality. For instance, #221 reports a critical error during Google Timeline JSON imports, while #220 notes incomplete date imports from Immich. These issues suggest underlying problems in handling diverse data formats or large datasets. Additionally, feature requests like #216 for distance unit preferences indicate ongoing efforts to enhance user experience.
Summary
Quantified Reports
Detailed Reportspundit and chartkick.The development team, led by Evgenii Burmakin, is actively working on feature enhancements and bug fixes, with a notable focus on export functionalities and UI improvements.
| Timespan | Opened | Closed | Comments | Labeled | Milestones |
|---|---|---|---|---|---|
| 7 Days | 12 | 6 | 8 | 12 | 1 |
| 30 Days | 30 | 21 | 48 | 30 | 1 |
| 90 Days | 79 | 58 | 239 | 77 | 1 |
| All Time | 99 | 75 | - | - | - |
Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.
| Developer | Avatar | Branches | PRs | Commits | Files | Changes |
|---|---|---|---|---|---|---|
| Evgenii Burmakin |  |
2 | 11/10/0 | 68 | 158 | 6029 |
| dependabot[bot] |  |
1 | 16/17/2 | 16 | 1 | 144 |
| sunstep |  |
1 | 1/1/0 | 1 | 1 | 2 |
| Max Stockner (bluemaex) | 0 | 0/1/0 | 0 | 0 | 0 | |
| Ikko Eltociear Ashimine (eltociear) | 0 | 1/0/0 | 0 | 0 | 0 | |
| None (ChemicalNRG) | 0 | 0/0/1 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The recent activity on the Dawarich GitHub repository indicates a vibrant development environment with 24 open issues. Notably, several issues revolve around data import failures, particularly with Google Timeline and GPX files, suggesting potential challenges in handling large datasets or specific file formats. Additionally, there are discussions about performance issues related to memory usage during imports and reverse geocoding tasks.
A recurring theme among the issues is the difficulty users face when importing data from various sources, with many reports of incomplete imports or errors during processing. This highlights a potential area for improvement in the application's data handling capabilities. Furthermore, there are feature requests aimed at enhancing user experience, such as adding support for distance units and improving the interface for managing imported points.
Issue #221: Error: NoMethodError: undefined method 'each' for nil:NilClass when trying to import a Google Timeline json
Issue #220: Running Immich Import isn't pulling in all dates
Issue #219: Only the actual year after Google import
Issue #216: Feature Request: Distance Units preference
Issue #213: Import "created at" date format isn't consistent with other views
Issue #159: Unable to start on Synology with docker-compose (Edited 2 days ago)
Issue #155: Distance calculation is sometimes wildly inaccurate (Edited 7 days ago)
Issue #151: Exports fail if no 'exports' folder exists and no folder is created by default (Edited 3 days ago)
Issue #139: Run Dawarich in a subdirectory (Edited 2 days ago)
Issue #162: Export to GPX (plus, bonus app compatibility option) (Edited 2 days ago)
The issues indicate that users are experiencing significant challenges with data imports, particularly from Google services and other applications like Immich and OwnTracks. The prevalence of errors related to data processing suggests that the application may require better error handling and user guidance during import processes.
Moreover, feature requests for improved functionality, such as customizable distance units and enhanced point management capabilities, reflect user interest in tailoring the application to their specific needs. The active engagement from users in reporting issues and suggesting features demonstrates a strong community interest that could be leveraged for further development.
Overall, addressing these concerns could enhance user satisfaction and broaden the application's appeal as a viable alternative to existing location tracking solutions.
The analysis of the pull requests (PRs) for the Dawarich project reveals a mix of feature enhancements, bug fixes, and dependency updates. The project is actively maintained, with a significant number of recent PRs indicating ongoing development and community engagement.
PR #223: chore: update index.html.erb
PR #200: Miles
DISTANCE_UNIT environment variable and updates JavaScript to support both kilometers and miles, enhancing user experience. PR #153: Add OpenTelemetry
PR #138: Default to today in maps page
PR #209: Export to GPX
PR #208: Add resource limits to docker-compose.yml file and fix Immich import bug
PR #206: Bump data_migrate from 9.4.0 to 9.4.2
data_migrate gem, ensuring compatibility with recent changes in dependencies.PR #205: Bump pundit from 2.3.2 to 2.4.0
pundit gem for authorization, improving security and functionality.PR #204: Bump chartkick from 5.0.7 to 5.1.0
PR #203: Bump rswag-specs from 2.13.0 to 2.14.0
PR #202: Bump rswag-ui from 2.13.0 to 2.14.0
PR #199: Map settings
... [Additional PRs follow similar patterns of feature additions, bug fixes, or dependency updates.]
The pull requests reflect a vibrant development cycle within the Dawarich project, showcasing a blend of new features, bug fixes, and routine maintenance through dependency updates.
Several PRs focus on enhancing user experience and functionality:
A notable number of PRs address bugs or enhance stability:
The project shows an active approach towards managing dependencies:
sidekiq, pundit, rspec-rails) illustrates a proactive stance towards maintaining a healthy codebase.The presence of contributions from various developers suggests a healthy community around Dawarich:
While most PRs are merged promptly, there are instances where contributions were not merged (e.g., PR #128). This could indicate either a need for further refinement or misalignment with project goals at that time.
In conclusion, Dawarich is positioned as an actively developed project that not only addresses immediate user needs but also looks towards future scalability and performance enhancements through thoughtful feature additions and robust dependency management practices.
Recent Contributions:
Collaboration: Primarily worked independently but merged contributions from other developers (e.g., dependabot) and collaborated on pull requests.
In Progress Work: The GPX export feature appears to be in the final stages of development, with recent commits indicating ongoing adjustments.
Recent Contributions:
Collaboration: All contributions were automated dependency updates with no direct collaboration noted.
Overall, the development team is actively enhancing the Dawarich project with significant contributions focused on feature development, bug fixing, and dependency management.