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

Upload Scenarios as GeoJSON - confusion about feature properties #905

Open
danbjoseph opened this issue Aug 16, 2023 · 1 comment
Open

Comments

@danbjoseph
Copy link
Member

  • Why is "id" a required property? It doesn't seem to be used in the tutorial creation process, is it a GeoJSON spec thing?
  • Is there a way to allow the user to set the order in the dashboard, instead of defining the order via the "screen" property on the GeoJSON features?
  • Is there a way to allow the user to set the correct answer in the dashboard, instead of defining the correct answer via the "reference" property on the GeoJSON feature? (Also, this property doesn't seem to be used right now for the validate tutorials, see tutorial should only advance on correct answer mapswipe#815)
  • Help text should mention the required GeoJSON property fields.
@tnagorra
Copy link
Contributor

  • The "id" is not a GeoJSON spec thing. I am not entirely sure if the "id" property is required. We were looking at the sample data for footprint and the examples had "id" property. https://raw.githubusercontent.com/mapswipe/python-mapswipe-workers/master/mapswipe_workers/sample_data/footprint/wsf_validation_tutorial_tasks.geojson
  • It should be possible to set the order in the dashboard. Although, we would need to add some UI elements to make that possible.
  • It should also be possible for the users to set the correct answer from the dashboard. The last time we checked, the reference property was indeed being used. Is the unexpected behavior specific to a type of project tutorial?
  • It should be trivial to show the required geojson property fields. Although, we should discuss how we can show this information to the user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

2 participants