How to use the custom quest file option?

[joshinils]

What file format do I need to create custom quests?

I want to survey non-existent things to import them into OSM.

I had previously devised a workflow with Vespucci, but it is very fiddly indeed.
I've written about it in my OSM diary, in German: https://www.openstreetmap.org/user/cyton/diary/401534

In principle, I'm open to writing a python script to convert my .osm files to this quest format, so I can use them in SCEE, and upload directly from there without using JOSM again as intermediary.

The only potential Issue I see with this is too many tags on one thing, or not wanting to upload things which I'd —in the past— edited in JOSM before uploading. Things like location of trees, benches, etc.

But I guess this is also possible to do in SCEE anyway.

How in-depth can I design these custom quests? Can I use tags to fill-in-the blank in questions?
Can I specify answerable options?

I don't want to first upload non-existent data to then remove it afterward.
I also don't want to spam notes on OSM with links to images of where exactly a single tree or lamp is located.

[Helium314]

In the csv file you can add messages for a specific element in the format type,id,message (e.g. NODE,1234,check position).
Alternatively you can use latitude,longitude,message to specify a location instead of an element.
You can edit the element (if specified), and remove the custom quest.

When the message starts with addNode you will get an option for adding a node, e.g. addNode amenity=restaurant,wheelchair=no,diet:vegetarian=yes

That's all this feature can do.

[joshinils]

Aha, ok.
So I'll have to add all tags the element shall finally have on OSM on one line, and the pre-made question is whether it exists there or not.

The following file does not load for me, or at least there is no quest marker shown at that place (there is no tree and a big area of grass, so no possible other quests);

52.633806,13.291105,addNode natural=tree,circumference=2.92,diameter_crown=17,genus=Platanus,genus:de=Platane,height=25,operator=Land Berlin,ref=045,source=Geoportal Berlin / Baumbestand Berlin / Straßenbäume,source:date=2024-06-06,species=Platanus acerifolia,species:de=Ahornblättrige Platane,start_date=1915

[mnalis]

52.633806,13.291105,addNode natural=tree,circumference=2.92,diameter_crown=17,genus=Platanus,genus:de=Platane,height=25,operator=Land Berlin,ref=045,source=Geoportal Berlin / Baumbestand Berlin / Straßenbäume,source:date=2024-06-06,species=Platanus acerifolia,species:de=Ahornblättrige Platane,start_date=1915

That line works for me, but (after doing Settings / Data management / Load custom quest file / Provide and choosing a file, of course), I had to fully quit the SCEE (i.e. remove it from recent app list in Android), and then restart it.

Then the custom quest shows:

See SCEE FAQ: Some settings don't seem to change the behaviour

Does that help?

[joshinils]

I had to fully quit the SCEE (i.e. remove it from recent app list in Android), and then restart it.

Why didn't I think of that? Oh well. Of course, when I started it now it showed up immediately, sure.

[Helium314]

Hmm, I'm pretty sure it did reload when i implemented the quest. Looks like it broke somewhere along the way

[mnalis]

maybe those Compose changes?

[Helium314]

I don't think so. Until yesterday, adding a custom quest file was done in the last part of the settings using the "old" view system.