Add GTD-Inspired Functionality for Enhanced Workflow and Dataset Management

[JLZIMMERMANN]

Description

I’d like to propose the addition of a Getting Things Done (GTD)-inspired feature set to uMap to improve its usability for task-oriented workflows, particularly when managing and comparing geographic datasets. This functionality would streamline processes like reviewing, updating, and tracking the status of geographic objects, making uMap a more powerful tool for both individual users and collaborative projects.

Proposed Features

1. Quick Status Toggle for Geographic Objects

• Description: Allow users to change the status of geographic objects (e.g., points, lines, polygons) with a single click, without needing to manually edit properties.

• Implementation Ideas: -Add predefined status options (e.g., "To Review," "In Progress," "Done") accessible via a dropdown or clickable button directly on the object’s popup or sidebar. -Reflect status changes visually through automatic updates to color, fill opacity, or icons (e.g., red for "To Review," green for "Done"). -Enable batch status updates for multiple selected objects.

• Use Case: When comparing an old dataset (e.g., outdated OSM data) with a new one (e.g., updated business records), users could mark objects as "Verified" or "Needs Update" with minimal effort.

2. Dataset Comparison Tool

• Description: Provide a built-in way to overlay and compare two datasets (e.g., old vs. new, OSM vs. proprietary data) with visual differentiation and status tracking.
• Implementation Ideas: -Add a "Compare Mode" where two layers (e.g., "Old Dataset" and "New Dataset") can be displayed side-by-side or overlaid with distinct styles (e.g., color or transparency). -Highlight differences automatically (e.g., new objects in green, removed objects in red, unchanged in gray). -Link this to the status toggle feature, so users can flag discrepancies for action (e.g., "To Verify").
• Use Case: A municipality could compare its internal records of sports facilities with OSM data to identify missing or outdated entries, toggling statuses as they review.

3. One-Click Property Filling

• Description: Allow users to populate predefined fields with default or context-based values with a single click, reducing manual input.
• Implementation Ideas: -Add a "Fill with Defaults" option in the object editor, using configurable templates (e.g., setting a "Last Checked" field to today’s date or a "Source" field to "OSM"). -Integrate with the status toggle (e.g., setting "Status: Done" also fills "Completed By" with the user’s ID).
• Use Case: When auditing OSM data against a business dataset, users could quickly mark an object as "Confirmed" and auto-fill metadata like "Verified On" or "Source" without typing.

4. Task List View

• Description: Add a sidebar or panel showing a list of objects with their statuses, filterable and sortable for task management.
• Implementation Ideas: -Display all objects in a table with columns for status, name, last modified date, etc. -Allow filtering (e.g., "Show only 'To Review' items") and sorting (e.g., by priority or date). -Link table entries to map objects, zooming to them on click.
• Use Case: A team updating OSM data could assign and track tasks like "Add missing parks" or "Verify building updates" directly within uMap.

Benefits

• Efficiency: Reduces repetitive manual edits, aligning with GTD’s focus on quick capture and processing of tasks.
• Collaboration: Simplifies workflows for teams by making status tracking and dataset comparisons more intuitive.
• Flexibility: Supports a wide range of use cases, from individual hobbyists to professional GIS workflows comparing OSM with proprietary data.

Additional Suggestions

• Integration with External Tools: Allow exporting the task list or status data (e.g., as CSV or JSON) for use in project management tools like Trello or Notion.
• Custom Status Templates: Let users define their own status categories and associated visual styles (e.g., "Urgent" in orange).
• History Tracking: Log status changes with timestamps and user info for accountability in collaborative projects.

Example Workflow

1.Import two datasets: "OSM Parks (2023)" and "City Parks (2025)". 2.Enable "Compare Mode" to see new/missing parks highlighted. 3.Click a park to toggle its status to "To Verify," changing its color to yellow. 4.Confirm it matches the city data, toggle to "Done" (turns green), and auto-fill "Verified On: 2025-02-21". 5.Review all parks in the Task List View, filtering for "To Verify" items.

Technical Considerations

• Build on existing layer and property management features in uMap.
• Leverage Leaflet’s capabilities for dynamic styling based on status.
• Store status and metadata in the GeoJSON properties of each object, ensuring compatibility with exports.