Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project creation workflow 1: Basic #1740

Open
spwoodcock opened this issue Aug 7, 2024 · 0 comments
Open

Project creation workflow 1: Basic #1740

spwoodcock opened this issue Aug 7, 2024 · 0 comments
Labels
effort:medium Likely a day or two enhancement New feature or request frontend Related to frontend code priority:high Should be addressed as a priority

Comments

@spwoodcock
Copy link
Member

spwoodcock commented Aug 7, 2024

Problem

As part of the process of overhauling the project creation we have two flows:

  • Basic with many defaults / pre-defined things.
  • Advanced with a lot more configuration options.
  • They should use the same project creation components, but just have a flag to advanced=true.

Solution

  • The first step to this is a splash page on project creation.
  • The user selects: Basic or Advanced mapper flow, with a brief description for each.
  • Clicking 'Basic' takes us to this flow

1. Project details

  • Possibly simplify this down a bit.
  • Combine the short and long description into one (ignore one of the fields).
  • Do not add configuration for TMS URL here (can be added later if needed).
  • Possibly remove the instructions field?

2. AOI

  • Remains the same.
  • Identify geometry type & ask if user wishes to merge multigeoms.

3. Category

  • Only allow selection of category.
  • No custom XLSForm upload?

4. Map Features

  • Only allow for import from OSM, based on the category.

    • If the category if of type linestring, do not clip the extract from raw-data-api.

    • If the category is of type polygon/point, clip the extract from raw-data-api.

      This should avoid issues like below:
      image

  • Display the feature count to the user:

    • Possibly add a warning if a huge amount of features present >5000 ?
    • Useful for the user to know if their project is appropriately sized.

5. Splitting

  • Keep the same.
  • The data extract for splitting is automatically downloaded (as we selected OSM data extract).

This issue is not final and should be updated
Ref: #1328

@spwoodcock spwoodcock added enhancement New feature or request priority:high Should be addressed as a priority frontend Related to frontend code effort:medium Likely a day or two labels Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort:medium Likely a day or two enhancement New feature or request frontend Related to frontend code priority:high Should be addressed as a priority
Projects
Development

No branches or pull requests

1 participant