barefootstache @barefootstache@qoto.org

#DailyBloggingChallenge (231/250)

Another typical example are railings or fences along a path. Since one barely ever knows which direction the way is going, thus a safer approach is to use the cardinal directions to denote a one-sided barrier.

Caveats are more obvious cases like steps, where usually `incline=up` aligns with the way's direction. In this case `left|l` and respectively `right|r` are used.

#DailyBloggingChallenge (230/250)

The first shorthand note are the cardinal directions denoted as `n`, `e`, `s`, and `w`.

These can be combined together to create more concrete directions like `ne`, `se`, `sw`, or `nw`. Or even more specific `nne`, `een`, `ees`, `sse`, `ssw`, `wws`, `wwn`, `nnw`.

An use-case is to denote more specifically where an object should be positioned relative to a way or an area. So if e.g. a path does not exist yet which branches off the current path and it is not perpendicular to the current path, then these directions can help to map the initial path head.

Hint: make sure to add the `fixme` key at the path's tail to check if the path continues. The most simplest value is `continue?`.

#OpenStreetMap

#DailyBloggingChallenge (229/250)

In the past, I already wrote a blog on how to create _quick actions_ in #OsmAnd: https://bf5.eu/post/osm/how-to-quick-map-with-osmand/ and for the next couple of entries regarding shorthand note system (that I use), the notes are created in such a way that a quick action cannot replace it.

That being said, kind of wish OsmAnd had quick action presets, so that one can quickly ease the sorting of the quick actions when in various situations. Like in urban terrain fire hydrants and street cabinets are more frequent, where as in comparison in rural terrain the frequency of hunting stands and feeding places are higher.

#DailyBloggingChallenge (228/250)

In the past, I uploaded the notes to the server and have (an outdated) note interpreter for my shorthand notes: https://www.openstreetmap.org/user/barefootstache

Though these days, I only push notes if they are obvious and/or I am using a specific app that does not permit offline notes. Like being a bit too fast with floors or type of building in #StreetComplete, though the new buildings overlay should take care of this issue in the past.

#DailyBloggingChallenge (227/250)

Onto the in person mappers comes the goal factor. This means is the goal just _to map_ or is the goal _to get to a specific destination_.

If it's the latter then one needs to manage between achieving the goal while mapping on the fly. For such cases there are many apps that can achieve the _updater_ aspect without losing too much time mapping. To name a few #StreetComplete or #EveryDoor.

In the _manager_ aspect the mentioned apps can help or #SCEE or #OsmAnd or #Vespucci.

Though many times one doesn't have enough time to navigate through the apps to accomplish the desired outcome. Thus jotting a note down or taking a photo can quickly save the details and later when more allotted time exists they can be updated.

#OpenStreetMap

#DailyBloggingChallenge (226/250)

One is usually a combination of the three kinds of mappers: creators, updaters, and managers.

Typically, one starts as an updater. Then once one is comfortable of knowing which objects exist, one adds creator to the mix. And finally once even more confident of the correct data format, one adds manager.

#DailyBloggingChallenge (225/250)

When doing #OpenStreetMap in person, there are typically three kinds of mappers: creators, updaters, and managers.

A _creator_ is a mapper who creates new objects. Predominantly by adding amenities like POIs or more specifically: benches, waste bins, fire hydrants, street cabinets, etc.

An _updater_ is a mapper who updates existing objects by adding missing data to complete the object. Most of #StreetComplete quests fall into this category.

A _manager_ is a mapper who edits existing objects. This means that at least one key-value pair is incorrect. A typical example is that the opening hours are outdated. Other cases are updating highway or other line based objects like waterways, or updating land covers.

#DailyBloggingChallenge (224/250)

Got to try out the new building overlay feature on #StreetComplete. It quickens the choosing of the building values and eases the option of updating them as well.

IMO, the icons of the buildings feel a bit small and could use the white space better.

#DailyBloggingChallenge (223/250)

One issue that I have experienced with the mirroring is that the repositories were not syncing up. Tried resolving it with refreshing tokens/keys and playing around with the configs.

In the end, the easier option is just to manually push to a different remote repository.

#DailyBloggingChallenge (222/250)

There are plenty of options to choose from when mirroring and one that makes sense is to only mirror the main branch after a successful pull request. This reduces resources and access to broken code.

Additionally, #Vercel only builds off of the main branch, so there is really no need to have a duplicate of all other branches.

#DailyBloggingChallenge (221/250)

An alternative option is repository piggy-backing. The means take one of the permitted repositories and mirror one's own repository to it.

A nice side effect of this is that the code is now at two locations.

#DailyBloggingChallenge (220/250)

One downside of using #Vercel is that it does not integrate directly with #Codeberg.

https://vercel.com/docs/deployments/git

Thus there exists the Vercel CLI tool.

#DailyBloggingChallenge (219/250)

The #MyRuckClub project uses #Vercel as its cloud frontend. This has the benefit of getting the app up and running fairly quickly.

As an #IndieDev the goal is to get the product as fast as possible to future users, so that one can iterate over versions quicker.

#DailyBloggingChallenge (218/250)

How damaging is it sharing gibberish online?

Considering most things are just opinions that can be factually or subjectively true, it is the reader's duty to question if the information presented creates any reaction.

This is what #qoto is all about.

#DailyBloggingChallenge (216/250)

Two other noticeable differences is the amount of smoke and the heat.

The teepee method generally is cooler and produces more smoke. The coolness is due to the lack of air flow and smoke amount from the amount of obstruction between the flame and the sky/top.

On the other side, the self feeding method generally is hotter and produces less smoke, since it is the opposite of the teepee method.

#DailyBloggingChallenge (215/250)

The main difference between the teepee method and self feeding method is the direction the coals travel and/or the location of the fuel source in the second phase.

With the teepee method the coals stay at the bottom and the fuel is from above.

Whereas with the self feeding the coals start at the top and slowly burn its way to the bottom and taking the fuel initially from the bottom and later from the sides.

#firemaking #bushcraft #survival

#DailyBloggingChallenge (214/250)

There are three general phases when creating a fire.

The phases being:

1. The initial lighting phase until the first coals appear.
2. Initial coals exist though still have initial kindling and/or need be fed consistantly to keep the fire going.
3. No real knowledge or attention needed to keep the fire going. Just occasionally add fuel and ignore for awhile.

#firemaking #bushcraft #survival

#DailyBloggingChallenge (213/250)

The only #firemaking technique I was taught by my father was the teepee method and it seems like the standard that most people (only) know.

When showing such people the top down method aka the self feeding method, they excuse it with "it is impossible" or "that is not how fire physics works".

#bushcraft #survival