Skip to content

Add Locate Features project type#86

Open
frozenhelium wants to merge 3 commits into
mainfrom
project/locate-features
Open

Add Locate Features project type#86
frozenhelium wants to merge 3 commits into
mainfrom
project/locate-features

Conversation

@frozenhelium

@frozenhelium frozenhelium commented Mar 25, 2026

Copy link
Copy Markdown
Contributor
  • Implement Locate Objects project type
  • Fix tutorial (vector tile layer) for Completeness project type
  • Update project list card
    • Add project type badge
    • Make the image cover the designated area
    • Add background color to the image

@frozenhelium frozenhelium force-pushed the project/locate-features branch 4 times, most recently from 61dee86 to 6cd05da Compare March 26, 2026 02:49
@frozenhelium frozenhelium force-pushed the project/locate-features branch from 6cd05da to 0c18156 Compare March 27, 2026 10:50
@frozenhelium frozenhelium marked this pull request as draft April 7, 2026 05:02
@kopitek8 kopitek8 marked this pull request as ready for review May 5, 2026 09:01
@frozenhelium frozenhelium force-pushed the project/locate-features branch from 7c07cc0 to 473b7ef Compare May 17, 2026 03:30
@frozenhelium frozenhelium changed the title Locate Features Project Add Locate Features project type May 17, 2026
Comment thread src/utils/buildTasks.ts
taskY: y,
taskZ: Number(project.zoomLevel),
taskId: `${project.zoomLevel}-${x}-${y}`,
taskId_real: `${project.zoomLevel}-${x}-${y}`,

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is taskId_real used for? It contains the same value as taskId, is that intentional?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's needed because for tutorials, task_id doesn't represent real tileX and tileY but for completeness project tutorial (vector) needs the real tileX and tileY

Comment thread src/views/ProjectView.vue Outdated
const optionsTemp = this.project?.customOptions ?? this.project?.answerLabels;
const options = optionsTemp
? [...optionsTemp].sort((a, b) => compareNumber(a.value, b.value))
: undefined;

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems this will sort options by value across all project types? Not sure if this is a good idea, as it means that "No" comes before "Yes" in many cases (as opposed to the current behaviour, where "Yes" usually comes before "No"). That seems a little counter-intuitive.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, I'll move this sorting to the Locate project scope

- add project type tag to cards in ProjectsView
- make project card images cover their container
- rename "LocateFeatures" project type to "Locate Objects"
- sort answer options inside LocateFeaturesProject instead of ProjectView
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants