OracleMaker was too problematic.

Relevant xkcd: Duty Calls

Come with me, and you’ll see: a world of purely jubilation.

The capitalization for OsmAnd should be corrected. Please?

Which Adobe?

As long as the door can be opened/broken in case of fire (or other internal disaster, e.g. toxic fumes) or there’s some other egress nearby. Please don’t create a trap.

But if you accidentally typed a or i, press ESC first.

Ah, someone with experience with Solid Explorer. I’m hopeful you might be a power user.

Long ago, I looked into it, but was dissuaded because the details views therein seemed to waste vertical whitespace. An absurdly small font, close to the bottom of the icon to maximize empty vertical space, was used for details (at least datestamp, I think).

Is that still the case? Have they added a method to increase the font size of the details without also increasing (or perhaps simultaneously decreasing) the filename’s font’s size? I couldn’t find one when I tried it last.

If there’s an interview with the creators wherein they extol the virtues of vertical whitespace within an item, or if some reviewer has done that for them, I’d love a link or two to read about it, see what I’m missing.

I’m sure the functionality is great. It’s the presentation I didn’t like. But perhaps there are unintended consequences of a compact layout…

I’m not sure which editor you refer to as “the OSM editor”, but surely id has it, JOSM can specify it, and StreetComplete has numerous quests that are disabled by default for various reasons but can be enabled (with SCEE having even more).

As for routing priority, that depends on the routing profile used by the router; there are dozens of routing profiles among several routing providers, many of which probably don’t use smoothness but could. OsmAnd can — it targets some smoothness values like unpaved.

Possibly not “companion” per se, but Every Door is available for iOS and MapComplete can run in browser. Go Map!! can provide more detailed editing.

BRouter and other routing engines can use attributes like surface and smoothness (and probably width) to calculate routes.

Are you referring to smoothness=bad or a narrow width? (I’m guessing you’ve been using StreetComplete to specify each.)

Yes, OsmAnd: https://osmand.net/docs/user/navigation/auto-car/