New Feature Ideas

This is a continuation of #59, since that was getting too long.
Please feel free to post new feature ideas in the comments on this issue. I would love to have some other thoughts about what should be included in this app (no guarantee that I will include them, but I will consider each idea). No idea is a bad idea here, worse case I may say that I will not include it in Trail Sense (but who knows, if it is a really good idea, I or someone else may work with you to build it into a separate app). I should also mention, that I am not averse to the idea of having separate companion apps to Trail Sense with specific niches if a good feature does not meet the goal of Trail Sense.
Some set in stone goals of this app:

Trail Sense must not use the Internet in any way, as I want the entire app usable when there is no Internet connection
New features must provide some benefits to people using the app while hiking, in a survival situation, etc.
New features should make use of the sensors on a phone rather than relying on stored information such as guides
New features must be based on peer-reviewed science

For reference, some things I have considered in the past and removed were:

"Survival blueprints" (recipes for making items while in survival situations)

There are a lot of other resources out there and it is best presented in a book format

Survival guide

There are a lot of other resources out there, including this awesome app

Animal behavior

I can't say there is enough science / supporting evidence behind Solunar theory for me to make accurate predictions of animal behavior in general, though if someone provides strong evidence I will consider it

Heart rate sensor

I don't want Trail Sense to move into the medical sector, there are increased regulations on that in Google Play and not something I'm willing to provide support for.

@kylecorry31 the fusion of these two awesome apps would be great

@vkuehn is that in reference to the heart rate tool and Trail Sense?
If so, I don't plan on merging the two (see the reasoning here: https://github.com/kylecorry31/Trail-Sense/issues/59#issuecomment-1672355144), but I could maybe use this as one of the plugin experiments (shows up in Trail Sense if the second app is installed)

@Z3NOX thanks - I provided some details in #1908 regarding this feature.
I've also fixed the first post here - no idea where the rest of that sentence went :)

Hi, would be nice to have a Garmin IMG reader to use as Google maps offline,
there is already a lot of work in each country developing this kind of maps for old GPS devices

@lucahttp thank you, I've updated #604 to include that format.

Hi Kyle, thanks for Trail Sense, it's a great app!
I was going to suggest export/import of settings.  It wasn't that big a deal until I started creating Packing Lists and realized that the data is trapped.  But then you beat me to it, adding backup/restore.  Thanks!  Would still be nice to have a way to share individual lists, but that's rather less critical.
I played with Tides a bit, but found it rather tedious to get set up.  It would be handy to be able to enter a station ID and have that station set up or updated from NOAA Tides & Currents.  But of course that violates the "No Internet" rule (which I value).  Then I saw the tide provider plugin idea in #1540.  Beat me again.  Only thing to add is that such a plugin could operate in a couple different modes:  Use the plugin to preconfigure select stations for later use offline, or use the plugin online to find and display the tide for the nearest station.
But I think you haven't beat me to all of these, for Photo Maps:

Keep PDF maps in a vector format for better zooming.  Or at least (perhaps optionally) rasterize at a higher resolution.  #1345 would certainly help here.
You mention that Photo Maps supports Geospatial PDFs, such as those from CalTopo.  I have tried using Geospatial PDFs from USGS Map Locator, such as Block Island, but for some reason they are not recognized.
Ok, here's the fun one:  Those USGS PDFs contain layers (Optional Content Groups, in PDF lingo), not all of which are turned on by default.  It would be great to be able to easily turn different layers on and off while viewing the map.  Among the layers are a shaded relief layer and an orthoimage (offline satellite view!) layer.

@diggernet thank you for the suggestions!
I agree that the Tides tool isn't ideal without being able to load from the Internet. In addition to #1540 I also have https://github.com/kylecorry31/Trail-Sense/issues/1102 and https://github.com/kylecorry31/Trail-Sense/issues/1104 which should help with this.
Here's new issues to track the map features:

https://github.com/kylecorry31/Trail-Sense/issues/1988
https://github.com/kylecorry31/Trail-Sense/issues/1989
https://github.com/kylecorry31/Trail-Sense/issues/1990

I'm looking for help around improving the messaging on devices without a compass. If anyone wants to help with some ideas, I would really appreciate if you add a comment to this issue: https://github.com/kylecorry31/Trail-Sense/issues/2010

Provide an emergency function
(This is how I think of it, not the technical details of Android) Android has an emergency button and apps can provide a hook to it and get started in an emergency/panic situation.
TS could provide a hook and start the whistle, the screen and the flashlight sending SOS. For saving battery there could be something like "stop after e.g. 15 minutes and give signals again at every full hour or every full and half hour for five minutes".
F-Droid supports such a function in the setting. Maybe you can reuse source from there?!
This also touches https://github.com/kylecorry31/Trail-Sense/issues/1471

@JensKorte thank you, I've added this issue to track this feature request: https://github.com/kylecorry31/Trail-Sense/issues/2027

A good feature would be a sound level meter
Something like the metal detector layout looks perfect for this.
Check out OpenNoise on the Play Store and on Github

@ojppe thank you for the suggestion. Can you suggest some use cases for a sound level meter that fit within Trail Sense's use cases?
I believe someone had suggested that in the past, and at the time I couldn't find any use cases (I can't seem to find the conversation around that - might have been through email or is lost in the old "New Feature Ideas" issue).

Determine the loudness of things in the environment (thunderstorm, volcano, waterfall, generator, aircraft, train, music, gunfire) to protect hearing

@ojppe while I think that would be a useful app, I don't think that will fit within Trail Sense's use cases

I don't see why not, Trail Sense has become my digital swiss army knife and a sound and speed meter are the only things missing (I can think of) that use most phones' sensors. But you know best!

@ojppe I apologize, I should have stated my reasons more clearly. I know a lot of the tools in Trail Sense can be used outside of hiking, but I'm trying to limit the scope of what I include in the app to keep it pretty focused. There's general criteria for new features in the first comment of this issue and the use cases wiki, but here's the specifics for a decibel meter:

I don't believe hearing protection falls into the supported use cases of Trail Sense: hiking, camping, backpacking, and geocaching. I believe a decibel meter would fit much better into a health, concert, or safety regulation app. The cases where this might come into play while hiking are very rare, and most people who find themselves in this situation will likely not have hearing protection with them.
I don't think this tool would get much use in the hiking space, but it would be time consuming to develop and support.
The microphone permission is not something I want to add at this point unless there's a feature which will provide a clear benefit in the hiking space for the majority of users.

As for the speed meter, the speed is shown on the Navigation tool in Trail Sense (GPS by default), and also available on the Pedometer tool (based on steps).
If there's something that can be predicted / identified using sound that is beneficial while hiking, I could add this in with that (more of an indicator that it is picking up audio), but as of right now I don't know of anything that falls into this case other than #1143

Thank you for the clarification

I have an idea for a "pairing" feature on this app, it may sound unappealing but it's something you might want to consider for later.
I'm thinking of this feature as being able to allow Trail Sense app users (2 or more people) to pair their coordinates or maybe a 'special location code' via gps that can be monitored offline. (You know, maybe it's like a bluetooth pairing between connected cell phones and being able to share each device's camera).
It's just that this uses a gps code base that is specifically used in the use of this application only, maybe it could be by scanning a special barcode or giving a special mark in this application. (hope you can understand what I mean)
Well, your app is very useful so far, I will always wait for future updates.

I have an idea for a "pairing" feature on this app, it may sound unappealing but it's something you might want to consider for later.
I'm thinking of this feature as being able to allow Trail Sense app users (2 or more people) to pair their coordinates or maybe a 'special location code' via gps that can be monitored offline. (You know, maybe it's like a bluetooth pairing between connected cell phones and being able to share each device's camera).
It's just that this uses a gps code base that is specifically used in the use of this application only, maybe it could be by scanning a special barcode or giving a special mark in this application. (hope you can understand what I mean)
Well, your app is very useful so far, I will always wait for future updates.

Thank you for the suggestion. I do have a similar feature planned as part of the Trail Sense Comms plugin - no timeline yet for that though. I hope to do some experimentation on the plugins in 2024, because I think they would be pretty cool and open a lot of possibilities. https://github.com/kylecorry31/Trail-Sense/issues/1540

I would love to see other tools have Android Quick Action tiles alongside Pedometer and TrackBack, like Flashlight, screen flashlight, whistle, etc.

I would love to see other tools have Android Quick Action tiles alongside Pedometer and TrackBack, like Flashlight, screen flashlight, whistle, etc.

Thank you for the suggestion, I will get more added. Here's an issue to track them: https://github.com/kylecorry31/Trail-Sense/issues/2120

Hi Kyle,
It would be nice to have an automatic "night-light" timer, where the app theme changes from the user-selected default, which used during the daytime, to the Night theme after sundown.
This would be useful in situations where you don't want your phone to automatically brighten when you check it during the night, both to preserve your night vision (in an astronomy context) and to avoid spooking animals if you're hunting. Hopefully this should be easy to implement given that Trail Sense automatically determines sundown times anyway.
Thanks for the app,
Lefty

Hi Kyle,
It would be nice to have an automatic "night-light" timer, where the app theme changes from the user-selected default, which used during the daytime, to the Night theme after sundown.
This would be useful in situations where you don't want your phone to automatically brighten when you check it during the night, both to preserve your night vision (in an astronomy context) and to avoid spooking animals if you're hunting. Hopefully this should be easy to implement given that Trail Sense automatically determines sundown times anyway.
Thanks for the app, Lefty
EDIT: I realize now there is a Sunrise/Sundown function. However, I still would like to be able to customize the specific theme to be used during the day and night. Apologies if this FR is redundant.

Thank you for the suggestion! I created the following issue to track that feature: https://github.com/kylecorry31/Trail-Sense/issues/2192   (it is not redundant and would be cool is Trail Sense let you choose which theme to use during the day and night)

This surprisingly doesn't exist in any OSS app but I think it would fit in nicely with the existing featureset:
An alarm that goes off when my location approaches a destination.
Example 1: You sleep on the bus, and it goes off when you're close to your destination.
Example 2: Alarm goes off when you get home/work reminding you to do something
Maybe it would make a bit more sense as part of a map app, but naturally when hiking this would be useful

Thank you for the suggestion, that feature is planned as part of https://github.com/kylecorry31/Trail-Sense/issues/1908 (or https://github.com/kylecorry31/Trail-Sense/issues/2159)

I don't believe this has been requested, so I'll put it out there: can you add a feature that allows the user to hide tools they don't need? It would be helpful to reduce clutter in the tools menu as I have dedicated apps for many of the offered features, for instance the unit converter QR code scanner, and the battery, and the astronomy and navigation tools can be accessed directly rather than through the tools menu. Of course, this is not to say that these features should be hidden by default since they aid in feature discovery, but rather the user should have the option to either hide them entirely or at least banish them to the bottom of the tools screen so they don't clutter the rest of the interface.

I don't believe this has been requested, so I'll put it out there: can you add a feature that allows the user to hide tools they don't need? It would be helpful to reduce clutter in the tools menu as I have dedicated apps for many of the offered features, for instance the unit converter QR code scanner, and the battery, and the astronomy and navigation tools can be accessed directly rather than through the tools menu. Of course, this is not to say that these features should be hidden by default since they aid in feature discovery, but rather the user should have the option to either hide them entirely or at least banish them to the bottom of the tools screen so they don't clutter the rest of the interface.

Thank you for the suggestion, I will consider adding it here: https://github.com/kylecorry31/Trail-Sense/issues/2255
My thought process on the current tools tab was that the user can pin the tools they use often rather than disable tools they don't use. I figured that there would be about 4-5 commonly used tools, and the rest would either only be used in specific cases (infrequent) or never used (there as a backup in case needed). I'll do more research into allowing tools to be hidden and the implications of that (#2046 is why navigation, astronomy, weather were added to the tools tab).

Hi there, as I wrote in my Google Play review, I really like this app, thank you so much for working on it! ✨ I was wondering if adding local photos (and perhaps notes or files) to the packing list would be possible in the future, please? I struggle with memory loss so every packing is quite stressful. I currently use Bring me for the packing purpose as it has photos (they help me remember which item I meant to bring with me/I own), but with this feature I could use only yours app (I love the weight option!) by itself. Bring me doesn't feel as intuitive and even tho it's obviously a great app, I prefer Trail Sense and it's other features.
Thank you once again, I hope you're having a wonderful day ^^

@ojppe while I think that would be a useful app, I don't think that will fit within Trail Sense's use cases

I think it might be helpful for people with hearing disabilities, if it could also detect things like the sound of water, thunder, cars etc. Or maybe even recognise what kind of sound it is, I'm not sure if that's possible? ^^ But I completely understand the microphone permission thing and that it maybe isn't necessary for survival. 🤔 And it might be too difficult to create. :// (Also, I use earplugs often due to my sensory sensitivities and often can't hear certain sounds that aren't as loud, but might be important, so this would be another case of use as well?)

@ojppe while I think that would be a useful app, I don't think that will fit within Trail Sense's use cases

I think it might be helpful for people with hearing disabilities, if it could also detect things like the sound of water, thunder, cars etc. Or maybe even recognise what kind of sound it is, I'm not sure if that's possible? ^^ But I completely understand the microphone permission thing and that it maybe isn't necessary for survival. 🤔 And it might be too difficult to create. :// (Also, I use earplugs often due to my sensory sensitivities and often can't hear certain sounds that aren't as loud, but might be important, so this would be another case of use as well?)

Hm, that's very interesting - I will need to give more thought into the sound identification portion (or sound amplification of certain frequencies) - it would be tricky, but is doable. I could see that being useful in a hiking situation (getting closer to cars/waterfall/thunderstorm).

Hi there, as I wrote in my Google Play review, I really like this app, thank you so much for working on it! ✨ I was wondering if adding local photos (and perhaps notes or files) to the packing list would be possible in the future, please? I struggle with memory loss so every packing is quite stressful. I currently use Bring me for the packing purpose as it has photos (they help me remember which item I meant to bring with me/I own), but with this feature I could use only yours app (I love the weight option!) by itself. Bring me doesn't feel as intuitive and even tho it's obviously a great app, I prefer Trail Sense and it's other features.
Thank you once again, I hope you're having a wonderful day ^^

Thank you! I think that's a great idea, I'll plan on adding that in a future release: https://github.com/kylecorry31/Trail-Sense/issues/2297

As I continue to bring in packing lists into Trail Sense for later I have found some more features I would like to see.
Considering last time you ended up splitting my post up into separate posts anyway I will just bunch them all together here.
More annotation
Giving packing lists descriptions would be very helpful.
Add an "optional" checkbox to an item's details to specify that it is not necessary to bring. These wouldn't contribute to the packed percentage and would be visibly shown to be optional somewhere in the packing list.
Custom Categories
Ability to add/remove custom categories. Then items could be added to these categories. "Other" would be a default category if the item's old category is deleted.
Tapping on an item's category in the packing list should open the dropdown to select a new category. This is mainly to make reassigning categories easier.

As I continue to bring in packing lists into Trail Sense for later I have found some more features I would like to see. Considering last time you ended up splitting my post up into separate posts anyway I will just bunch them all together here.
More annotation

Giving packing lists descriptions would be very helpful.
Add an "optional" checkbox to an item's details to specify that it is not necessary to bring. These wouldn't contribute to the packed percentage and would be visibly shown to be optional somewhere in the packing list.

Custom Categories

Ability to add/remove custom categories. Then items could be added to these categories. "Other" would be a default category if the item's old category is deleted.
Tapping on an item's category in the packing list should open the dropdown to select a new category. This is mainly to make reassigning categories easier.

Thank you for the suggestions, here are some issues to track these features:

https://github.com/kylecorry31/Trail-Sense/issues/2409
https://github.com/kylecorry31/Trail-Sense/issues/2410
https://github.com/kylecorry31/Trail-Sense/issues/730
https://github.com/kylecorry31/Trail-Sense/issues/2411

So I have been thinking and it might be possible to put an small LLM inside trail sense. I have been playing around Phi3 mini and it fits in a fairly small amount of space.
https://ollama.com/library/phi3
You could add Llama.cpp inside the app and then ship a AI assistant that works completely offline. What would be even more cool would be tweaking the model to be good at outdoor and camping related tasks. For instance, it could be tweaked to do plant recognition and cooking. You could process images with llava as llava can use any text based model.
https://github.com/ggerganov/llama.cpp
https://github.com/haotian-liu/LLaVA
Of course there would be some serious potential issues. First off, if the app started shipping a language model it would make the install size be huge. Even with a model under 2.5gb it still would be taking up a lot of space. You could have a button to download it after the app is installed but I think that would violate the no internet access policy. The other issue would be ram. Newer phones have plenty of ram so they will run it just fine but I have a 2019 phone with 3gb of ram. Theoretically it could work but it would be very tight. Running something so computationally intensive would also drain battery.
So in summary this would be cool but it would also be very hard to get right. I don't think this is immediately viable but I figured I'd drop it here as something to consider. Thank you for your time and development of this app.

I am incredibly wary of taking safety-critical instructions from a ML model, given how they work.
In that respect, I am not sure how well it fits in with the rest of the very carefully vetted tools.
Is there a specialized problem space you envision it for?

So I have been thinking and it might be possible to put an small LLM inside trail sense. I have been playing around Phi3 mini and it fits in a fairly small amount of space.
https://ollama.com/library/phi3
You could add Llama.cpp inside the app and then ship a AI assistant that works completely offline. What would be even more cool would be tweaking the model to be good at outdoor and camping related tasks. For instance, it could be tweaked to do plant recognition and cooking. You could process images with llava as llava can use any text based model.
https://github.com/ggerganov/llama.cpp
https://github.com/haotian-liu/LLaVA
Of course there would be some serious potential issues. First off, if the app started shipping a language model it would make the install size be huge. Even with a model under 2.5gb it still would be taking up a lot of space. You could have a button to download it after the app is installed but I think that would violate the no internet access policy. The other issue would be ram. Newer phones have plenty of ram so they will run it just fine but I have a 2019 phone with 3gb of ram. Theoretically it could work but it would be very tight. Running something so computationally intensive would also drain battery.
So in summary this would be cool but it would also be very hard to get right. I don't think this is immediately viable but I figured I'd drop it here as something to consider. Thank you for your time and development of this app.
Edit: you also could use Tinyllama
https://ollama.com/library/tinyllama
https://github.com/jzhang38/TinyLlama

Hi, thank you for the suggestion. While it would be interesting to have an offline hiking-related LLM, I agree with all @Saijin-Naib 's concerns.
While I don't plan to add it to Trail Sense as a tool, if there's an open source app which has an offline LLM that you think would be useful, I can evaluate it an potentially list it as a recommended app if it performs well, has appropriate disclaimers, and is useful in the wilderness. Personally, I prefer the Offline Survival Manual for any information regarding wilderness survival - but I don't have a good recommendation for a plant ID app (I use Seek, but it isn't open source - and doesn't always perform well).

PlantNet is a FOSS tool and database for plants I use which has offline capabilities.

PlantNet

Thank you, I will take a look!

I think it would be useful for completing a variety of tasks. For a safety perspective you could simply have a disclaimer with a warning about bad information.
I already run a model on my laptop which works pretty well. I connect my phone to my laptop. It is pretty much a glorified search engine that can create things from scratch. For instance, the other day I asked it to give me ideas for using some left over ingredients. I ended up making a curry recipe that it suggested. I had to slightly tweak it but it worked fine. There is very much a danger of bad information so you do need to be careful.
I am not that surprised that you are not really interested in adding this. Maybe this could be something to reevaluate after the LLM tech as had a chance to cool down a bit.

I think it would be useful for completing a variety of tasks. For a safety perspective you could simply have a disclaimer with a warning about bad information.
I already run a model on my laptop which works pretty well. I connect my phone to my laptop. It is pretty much a glorified search engine that can create things from scratch. For instance, the other day I asked it to give me ideas for using some left over ingredients. I ended up making a curry recipe that it suggested. I had to slightly tweak it but it worked fine. There is very much a danger of bad information so you do need to be careful.
I am not that surprised that you are not really interested in adding this. Maybe this could be something to reevaluate after the LLM tech as had a chance to cool down a bit. Right now there are no known apps that do this which makes sense as it is very hard to run locally for the reasons I listed above.
Thanks for your time

Thank you for providing more information - I will consider adding it as a plugin if LLMs (or whichever technology ends up replacing them) get more reliable and are shipped on more phones out of the box.

I would love to see, if possible, the ability to use sensor fusion to enable GPS+Magnetometer blending for heading.
In many cases (especially on lower-end devices), it can be much more robust and stable to have a GPS-based heading, especially once you have a few seconds of movement.
ArduPilot uses this in the EKF3 filter as a settable parameter, if that helps when investigating this:
https://github.com/ArduPilot/ardupilot

I would love to see, if possible, a way for Photo Maps and Beacons to become more integrated.
Right now, I have downloaded and calibrated trail maps for the County where I live. I also collect Beacons for each Feature on the map that I encounter.
It would be excellent if I were able to view the Beacons in the same location as the Photo Map they are associated with, so I can say oh, Shelter Orange is part of Park Blue, and is associated with the Features map.

I would love to see, if possible, filter results for Beacons and Photo Maps also match/highlight on the Group/Path for the object.
This would make a result for a PhotoMap named Trails under Country\State\County\Municipality\Park Blue when I search for Blue.
Currently, I have to name my PhotoMaps something like Trails - Park Blue to find them by where they belong to.

I would love to see the ability to have a ReadMe.MD at the root level of a Group in Photo Maps that could contain whatever local-only markdown content (so no remote images).
One could use this to hold information about that Park or Trail that isn't on the Photo Map itself, for instance.
NextCloud Files handles this pretty neatly, though it could just be hidden under a collapsed header at the title or a tab, perhaps.

@Saijin-Naib thank you for the suggestions. Here are some issues which I think summarize all of them:

#2455
#2456, #1300, #1254
#2457
#2458

Please let me know if I got any of those wrong.

I think it would be great to have, in Astronomy, the Solicitists and the Equinoxes dates marked 😀

I think it would be great to have, in Astronomy, the Solstices and the Equinoxes dates marked 😀

Thank you for the suggestion. Here's an issue to track that: https://github.com/kylecorry31/Trail-Sense/issues/2460

Thank you for the suggestion. Here's an issue to track that: #2460

Thanks :)

I would love to see the ability to see Estimated H/V accuracy while recording Points and Tracks.

I would love to optionally have the ability to record points using GPS Averaging/long baseline sampling to improve accuracy of recorded points, especially in challenging areas.
UX could be, when enabled, tap to sample/stop, long press to instant mark.
It would require preferences to enable, the desired accuracy to stop on, the desired max sample time/count (1/s assumed).

@Saijin-Naib thank you for the suggestions

Can you clarify how you would want to see the horizontal / vertical accuracy of beacons and paths? Do you want to see them on the radar compass / map or just see the accuracy as text?
I believe the feature you are looking for is GPS Smoothing, this is experimental, so you can enable via Settings > Experimental > GPS Smoothing. It works by averaging the readings (using a kalman filter), so the GPS will "improve" over time. I say improve in quotes, because from my research Android already performs GPS smoothing under the hood. As for the accuracy stop, here's an issue for that #2461

Accuracies: Just as text when recording or reviewing them, I think. On the radar or AR, inaauracy circles might feel cluttered?

Smoothing: Almost, yes, but specifically for recording Points, like how GPS Point does, which significantly improves accuracy if you can wait.

https://gpspoint.app
Garmin mapping-grade GPS also can do this, and it rocks.

Accuracies: Just as text when recording or reviewing them, I think. On the radar or AR, inaauracy circles might feel cluttered?
Smoothing: Almost, yes, but specifically for recording Points, like how GPS Point does, which significantly improves accuracy if you can wait.

https://gpspoint.app
Garmin mapping-grade GPS also can do this, and it rocks.

Thank you for the clarification.
I agree, it would be too cluttered to show accuracy on a map view. Here's the issue to track that: #2463.
Thank you for the examples, I'll take a look. Here's an issue to track that #2464

It would be amazing if the import of PDFs for Photo Maps would have a control (scrub bar + direct numeric input?) for choosing which page to input from a PDF after switching to and previewing it.
User story:
Municipalities here often have multipage park feature and trail maps that do not always have the map on the first page, necessitating using other tools to split out pages from the PDFs.

It would be amazing if the import of PDFs for Photo Maps would have a control (scrub bar + direct numeric input?) for choosing which page to input from a PDF after switching to and previewing it.
User story: Municipalities here often have multipage park feature and trail maps that do not always have the map on the first page, necessitating using other tools to split out pages from the PDFs.

Thank you, this will be implemented in #913

I would love to be able to jump to PhotoMaps that I am currently navigating on, or located on, from the compass, like how we can get to Beacons with the UI button.

I would love a way to refine calibration on PhotoMaps after initial calibration.
Say we are navigating on the PhotoMap and notice our location is off from the map, we could enter a refine mode where we drag/drop our current position marker to the right spot and the projection gets transformed to better fit.

@Saijin-Naib thank you for the suggestions

Have you tried the "Open Photo Map" quick action? I've been trying to prefer quick actions over additional UI elements since they are more customizable.
Would this be different from the ability to recalibrate a photo map (menu > calibrate)? Unfortunately, photo maps only supports 2 calibration points, so if you are looking to have a non-linear warping, then I'm afraid I may not be able to support that

Hi!

Yes, I have it on the bottom, but I need to drill down to the map(s) each time through my organization structure (Country/State/County/Town/Park/Maps) and find the map. I have 36 maps currently, adding more each week.

Hmm... in that case, I guess it must not be different if we are only able to do two-point...

Hi!

Yes, I have it on the bottom, but I need to drill down to the map(s) each time through my organization structure (Country/State/County/Town/Park/Maps) and find the map. I have 36 maps currently, adding more each week.
Hmm... in that case, I guess it must not be different if we are only able to do two-point...

Just to confirm, there are two photo maps quick actions - one to open the photo maps quick action tool (Tool: Photo Maps), and another to open the active map (Open Photo Map), which factors in your current location and the destination beacon. Can you confirm you are using the "Open Photo Map" variant of the quick action?

Ah, no, I am using the bottom navigation area to switch between compass and photo map:

Ah, no, I am using the bottom navigation area to switch between compass and photo map:

In that case, my suggestion is to use the "Open Photo Map" quick action to open the active map. You can enable this in Settings > Tools > Quick actions, and when you long press the bottom navigation bar you will see the quick action there.
Are you looking for a button on the Photo Maps tool to open the active map in addition to that quick action?

Hmm, that could be very useful, or perhaps also with a UI marker on the photo maps lists (breadcrumb/dot) to show what folders/maps are currently where you are?

Hmm, that could be very useful, or perhaps also with a UI marker on the photo maps lists (breadcrumb/dot) to show what folders/maps are currently where you are?

Thanks, that is a good idea:

https://github.com/kylecorry31/Trail-Sense/issues/2488
https://github.com/kylecorry31/Trail-Sense/issues/2489

There's a nice feature in an open source app called "Sundroid". It's called "tracker" and it actually displays the sun and moon tracks on the compass. It's very useful, and I guess not hard to implement, since it's open source:
https://github.com/davemorrissey/sundroid
https://play.google.com/store/apps/details?id=uk.co.sundroid.free

Barometer calibration is a welcome new feature in the latest release. Thank you for that. All my phones are now calibrated to my local METER station, and it will be easier to determine which sensors on which phones are the most stable. Previously they were all giving wildly disparate readings. Only my S8 was reading close to the true pressure.
As far as comms go, how practical would it be to encode morse code using the flash, and perhaps read it from a distance with the camera? How about an integrated morse code trainer?
A widget that links directly to the SOS beacon might be useful if one become incapacitated.
And how about a barograph widget for the homescreen?

As far as comms go, how practical would it be to encode morse code using the flash, and perhaps read it from a distance with the camera? How about an integrated morse code trainer?

See #1612

Barometer calibration is a welcome new feature in the latest release. Thank you for that. All my phones are now calibrated to my local METER station, and it will be easier to determine which sensors on which phones are the most stable. Previously they were all giving wildly disparate readings. Only my S8 was reading close to the true pressure.
As far as comms go, how practical would it be to encode morse code using the flash, and perhaps read it from a distance with the camera? How about an integrated morse code trainer?
A widget that links directly to the SOS beacon might be useful if one become incapacitated.
And how about a barograph widget for the homescreen?

Thank you for the suggestions - as @michaelblyons mentioned, that issue should cover morse code with the flash.
For the SOS widget:

https://github.com/kylecorry31/Trail-Sense/issues/2499
https://github.com/kylecorry31/Trail-Sense/issues/347 (updated to include SOS)

For the barograph widget:

https://github.com/kylecorry31/Trail-Sense/issues/347 (will include a snapshot of the weather from TS)

There's a nice feature in an open source app called "Sundroid". It's called "tracker" and it actually displays the sun and moon tracks on the compass. It's very useful, and I guess not hard to implement, since it's open source: https://github.com/davemorrissey/sundroid https://play.google.com/store/apps/details?id=uk.co.sundroid.free

Thank you, I believe that this ticket will address that: https://github.com/kylecorry31/Trail-Sense/issues/1920

An option to use "lunitidal interval" to set up the tide tables. Many of the simpler Casio tide watches use this method. Various values can be found online, for example this page from the UK
https://ntslf.org/about-tides/tide-clocks-watches

Is there any way to use the accelerometer to detect if the device is dropped? It could sound an alert, or flash a light to aid recovery.

@leavenode thank you for the suggestions, here are some issues to track them:

https://github.com/kylecorry31/Trail-Sense/issues/2510
https://github.com/kylecorry31/Trail-Sense/issues/2511

It would be cool if you could import OpenStreetMaps data for photo maps (though not as much of a photo) - if you export a PDF from OSM and import it to TrailSense, it gets compressed too much sometimes ..

It would be cool if you could import OpenStreetMaps data for photo maps (though not as much of a photo) - if you export a PDF from OSM and import it to TrailSense, it gets compressed too much sometimes ..

Thank you for the suggestion, I am planning on eventually adding OSM tile support: https://github.com/kylecorry31/Trail-Sense/issues/604

add a small side panel for galaxy users,not shure if trailsense needs to be distributed through galaxy store to make it work tho

add a small side panel for galaxy users,not shure if trailsense needs to be distributed through galaxy store to make it work tho

Thank you for the suggestion, just to confirm, is that the feature on Samsung phones where you can open on the right side of the screen from anywhere? This:

feature request: allow calibrating the map with multiple known locations/beacons weighted by the given location's uncertainty/accuracy. I believe this could be done using least squares or something similar.

feature request: allow calibrating the map with multiple known locations/beacons weighted by the given location's uncertainty/accuracy. I believe this could be done using least squares or something similar.

Thank you for the suggestion. I thought I had an issue logged for that, but I couldn't find it so I created https://github.com/kylecorry31/Trail-Sense/issues/2534 to track it (if I do find it, I'll update this comment and delete the new issue)

Apologies if these have been requested, I didn't see anything in the search (except survival guide, which I see you mentioned but I wanted to chime in my support for including it in this app as well)

Wim hof breathing guide. I think this would be useful for someone in extreme cold, the wim hof breathing method has great results for helping people manage cold and I think having functionality in the app to take you through each step/stage of the method is really helpful. An example is https://inner-breeze.app/. More research is needed, but there are reports of the technique being useful for reducing acute mountain sickness https://www.healthline.com/health/wim-hof-method
Mushroom ID (with many warnings to only eat mushrooms you're certain of the identity of!), for example shroomify. It has a simple id set up where you can select different traits of the mushroom you have, and it will give you a list of mushrooms it might be, as well as warn of dangerous lookalikes. I can understand why you wouldn't want to include this due to the risk of poisonous mushrooms though.
todo list, with the ability to set a time to remind you of a list or list item
Survival guide such as the guide you linked to. I think this would be important to include in trail sense because people may not know about those apps/resources, but if they find themself in a survival situation without internet, they won't be able to look up those guides or download them. This could be solved by adding a warning to the app description to tell people to go download those too, but I think the best solution would be to simply include it in trail sense. Alternatives already exist for many of the tools included in trailsense, but they are still included anyways since they're so useful for survival/hiking situations (e.g. flashlight, pedometer, photo maps, level, clinometer, clock, timer, notes, packing lists, unit converter, and white noise), so I think it would make sense to include some guides as well. I think this justification also applies to the wim hof breathing tool and mushroom id ideas, yes there are other apps for those things but people may not know about them or think they don't need them.

Thanks for your time, consideration, and the great app!

Apologies if these have been requested, I didn't see them when I searched (except survival guide, which I see you mentioned but I wanted to chime in my support for including it in this app as well)

Wim hof breathing guide. I think this would be useful for someone in extreme cold, the wim hof breathing method has great results for helping people manage cold and I think having functionality in the app to take you through each step/stage of the method is really helpful. An example is https://inner-breeze.app/. More research is needed, but there are reports of the technique being useful for reducing acute mountain sickness https://www.healthline.com/health/wim-hof-method
Mushroom ID (with many warnings to only eat mushrooms you're certain of the identity of!), for example shroomify. It has a simple id set up where you can select different traits of the mushroom you have, and it will give you a list of mushrooms it might be, as well as warn of dangerous lookalikes. I can understand why you wouldn't want to include this due to the risk of poisonous mushrooms though.
todo list, with the ability to set a time to remind you of a list or list item
Survival guide such as the guide you linked to. I think this would be important to include in trail sense because people may not know about those apps/resources, but if they find themself in a survival situation without internet, they won't be able to look up those guides or download them. This could be solved by adding a warning to the app description to tell people to go download those too, but I think the best solution would be to simply include it in trail sense. Alternatives already exist for many of the tools included in trailsense, but they are still included anyways since they're so useful for survival/hiking situations (e.g. flashlight, pedometer, photo maps, level, clinometer, clock, timer, notes, packing lists, unit converter, and white noise), so I think it would make sense to include some guides as well. I think this justification also applies to the wim hof breathing tool and mushroom id ideas, yes there are other apps for those things but people may not know about them or think they don't need them.

Thanks for your time, consideration, and the great app!

FYI there is already a nice open source, small, and totally offline app for this: https://github.com/ligi/SurvivalManual

I know, I brought up a few reasons why I think it makes sense to include in trailsense anyways

Apologies if these have been requested, I didn't see them when I searched (except survival guide, which I see you mentioned but I wanted to chime in my support for including it in this app as well)

Wim hof breathing guide. I think this would be useful for someone in extreme cold, the wim hof breathing method has great results for helping people manage cold and I think having functionality in the app to take you through each step/stage of the method is really helpful. An example is https://inner-breeze.app/. More research is needed, but there are reports of the technique being useful for reducing acute mountain sickness https://www.healthline.com/health/wim-hof-method
Mushroom ID (with many warnings to only eat mushrooms you're certain of the identity of!), for example shroomify. It has a simple id set up where you can select different traits of the mushroom you have, and it will give you a list of mushrooms it might be, as well as warn of dangerous lookalikes. I can understand why you wouldn't want to include this due to the risk of poisonous mushrooms though.
todo list, with the ability to set a time to remind you of a list or list item
Survival guide such as the guide you linked to. I think this would be important to include in trail sense because people may not know about those apps/resources, but if they find themself in a survival situation without internet, they won't be able to look up those guides or download them. This could be solved by adding a warning to the app description to tell people to go download those too, but I think the best solution would be to simply include it in trail sense. Alternatives already exist for many of the tools included in trailsense, but they are still included anyways since they're so useful for survival/hiking situations (e.g. flashlight, pedometer, photo maps, level, clinometer, clock, timer, notes, packing lists, unit converter, and white noise), so I think it would make sense to include some guides as well. I think this justification also applies to the wim hof breathing tool and mushroom id ideas, yes there are other apps for those things but people may not know about them or think they don't need them.

Thanks for your time, consideration, and the great app!

Thank you for the suggestions.

I'll look into this: https://github.com/kylecorry31/Trail-Sense/issues/2537
As you mentioned, there's risk involved in mushroom foraging (or any foraging) and for that reason I don't want to be the source of that in Trail Sense. I'll look into adding Shroomify as a recommended app (I have it on my phone). https://github.com/kylecorry31/Trail-Sense/issues/2538
I have plans to add this: https://github.com/kylecorry31/Trail-Sense/issues/542 and https://github.com/kylecorry31/Trail-Sense/issues/1974
This is a difficult one. I personally would like to include a survival guide in Trail Sense, but there are a variety of reasons why I will likely not do that in favor of recommending the Offline Survival Manual. 1) I don't have the time or skills to create and maintain a full survival manual, so I would be looking to embed a guide if I add this 2) the license of the Offline Survival Manual is not compatible with embedding it into Trail Sense, even with attribution (GPL 3). If there's a survival guide that you know of that has a permissive open source license, I'll definitely look into embedding that into Trail Sense and maybe look into making it more recommended to download the Offline Survival Manual. Here's an issue to track potentially embedding a guide: https://github.com/kylecorry31/Trail-Sense/issues/2539

That's a bummer that the license is incompatible. I'll keep an eye out if I come across any that are open source or public domain
Adjacent to the wim hof breathing idea, there could also be panic button with a guided meditation or breathwork to reduce anxiety, especially if someone has found themself in a really bad position or gotten lost? Might be able to see if sam harris (from the waking up guided meditation app) would be willing to record one oriented towards a survival situation? I know in the waking up app they have a couple "in case of emergency" guided meditations oriented towards people going through really difficult moments like loss of a loved one.
And then adjacent to that and the white noise feature, there are guided sleep meditations I've found really useful when I had trouble sleeping, and there's also yoga nidra / non-sleep deep rest (nsdr) which I've had good experiences with when I've been super tired but didn't have time to take a nap, and could be good for someone who wasn't able to get a good nights sleep while in the backcountry and it's impacting their ability to do what they need to. Huberman has a 10 minute and 20 minute guided nsdr, not sure what if any specific licensing applies to it though. https://www.hubermanlab.com/topics/nsdr-meditation-and-breathwork
For guided meditations like these, it may even be possible to use TTS to avoid having to store big sound files. I'm sure it wouldn't be as calming as a pre-recorded one, but for the purposes of trail sense it might be good enough

That's a bummer that the license is incompatible. I'll keep an eye out if I come across any that are open source or public domain
Adjacent to the wim hof breathing idea, there could also be panic button with a guided meditation or breathwork to reduce anxiety, especially if someone has found themself in a really bad position or gotten lost? Might be able to see if sam harris (from the waking up guided meditation app) would be willing to record one oriented towards a survival situation? I know in the waking up app they have a couple "in case of emergency" guided meditations oriented towards people going through really difficult moments like loss of a loved one.
And then adjacent to that and the white noise feature, there are guided sleep meditations I've found really useful when I had trouble sleeping, and there's also yoga nidra / non-sleep deep rest (nsdr) which I've had good experiences with when I've been super tired but didn't have time to take a nap, and could be good for someone who wasn't able to get a good nights sleep while in the backcountry and it's impacting their ability to do what they need to. Huberman has a 10 minute and 20 minute guided nsdr, not sure what if any specific licensing applies to it though. https://www.hubermanlab.com/topics/nsdr-meditation-and-breathwork
For guided meditations like these, it may even be possible to use TTS to avoid having to store big sound files. I'm sure it wouldn't be as calming as a pre-recorded one, but for the purposes of trail sense it might be good enough

I think for guided meditations, I would prefer a recommended app rather than bake that into Trail Sense, as that is starting to stray outside of the supported use cases. If you have recommendations, I would be happy to research them and list them in the guide. I'm also planning on making the white noise have custom audio files, which may allow you to upload meditations of your choice.

I like the idea of custom audio files and then having a list of different meditations people could download and load. Couldn't white noise be generated on device without needing a file though? As well as other noise colors like pink and brown?

I like to orient my solar panels in the evening to catch the early hours of sun the next morning (especially when I'm car or RV camping and I sleep in the next day).
It would be great if the solar panel aligner allowed using a different time than the present to help with panel alignment, so I could align them to catch the first few hours in the morning.

Feature request: Reduce clicks needed to use solar panel aligner
I use the solar panel aligner a lot (frequently every few hours in a day to re-orient my panels), so even a few extra clicks add up over time. It would be great to have an option to reduce the number of clicks I need to use it.
Ideas:

Ability to disable the "Place your phone on the face of the solar panel..." dialog that opens when entering the solar panel aligner.
Show the small GPS and Compass statuses on the alignment page, just as they are displayed on the Navigation page, so I can make sure they have good status to allow accurate panel alignment. (I frequently have to calibrate my compass before aligning the panels because it looses calibration inside my car or RV.)
When selecting a different duration of charge from today, perhaps the ability to add a one or more presets as buttons on top of the page where selecting the button doesn't bring up another dialog for a custom time.

Thanks again for Trail Sense! It's one of the most useful open source projects IMHO!

Feature request: Add more entries to the Bottom Navigation Bar for devices that display more.
On my phone, I think at least one more icon slot could fit comfortably, maybe two. Maybe let the user decide how crammed full they would like it.

@Stormwind99 thank you for the suggestions, here are some tickets to track them.

https://github.com/kylecorry31/Trail-Sense/issues/2564
https://github.com/kylecorry31/Trail-Sense/issues/2565
https://github.com/kylecorry31/Trail-Sense/issues/2566
https://github.com/kylecorry31/Trail-Sense/issues/2567
https://github.com/kylecorry31/Trail-Sense/issues/2568

I think a rangefinder could be useful if there's any way to pull that data... I know most cameras that autofocus have an IR rangefinder to facilitate that, but idk exactly how it works, so there's a chance it's just not useable...

I think a rangefinder could be useful if there's any way to pull that data... I know most cameras that autofocus have an IR rangefinder to facilitate that, but idk exactly how it works, so there's a chance it's just not useable...

Thank you for the suggestion, I have added it to https://github.com/kylecorry31/Trail-Sense/issues/1911#issuecomment-2411622454

Support mapforge offline maps..
Similar to this
https://github.com/OpenTracksApp/OSMDashboard
Much better then photo maps, or tile maps, always updated. Very small size. Community driven, free as in free beer.

Support mapforge offline maps.. Similar to this https://github.com/OpenTracksApp/OSMDashboard
Much better then photo maps, or tile maps, always updated. Very small size. Community driven, free as in free beer.

Thank you for the suggestion, I have plans to add other map formats eventually, including MapsForge: https://github.com/kylecorry31/Trail-Sense/issues/604

Get location by triangulation of mountain peaks.
Use a peak finder app like
https://github.com/woheller69/PeakOrama
Then use the camera and onboard compass to mark known peaks (more would give better accuracy) and use the peak details and a vector map (like mapforge maps) to draw lines from peaks via compass bearing and where the lines intersect is where you should be in the map.
I have never seen any app do this but it really should not be hard i don't think. Most everything you need is already open source.
Peak details and data base
Compass and camera info
Mapforge map display.

Location via star map and camera+compass.
With the correct time (or pretty close) a star chart and a data base you could use the camera+compass to give a general location similar to how they used to use a sextant to do.
There are some sextant apps but i don't know if an open source one.  There are many sky maps that are very accurate and if you even know the general location (ie what state you are in) you could use the camera to fine tune a sky map(with major constellations only) to a very accurate location.
A cool tool that should work on land or sea. And educational.

Get location by triangulation of mountain peaks.
Use a peak finder app like https://github.com/woheller69/PeakOrama
Then use the camera and onboard compass to mark known peaks (more would give better accuracy) and use the peak details and a vector map (like mapforge maps) to draw lines from peaks via compass bearing and where the lines intersect is where you should be in the map.
I have never seen any app do this but it really should not be hard i don't think. Most everything you need is already open source. Peak details and data base Compass and camera info Mapforge map display.

Thank you for the suggestion. I believe the tool you are looking for in Trail Sense is the Augmented Reality tool. That will display nearby beacons as an overlay.
As for adding peak data, unfortunately it is not feasible for Trail Sense to add that because of the following:

It requires too much data to package with the app, might be possible with the plugins (see #1540 )
If they are not packaged with Trail Sense, then it would need to look them up over the internet, which is what PeakOrama does. This is not compatible with Trail Sense's lack of Internet permissions

Location via star map and camera+compass.
With the correct time (or pretty close) a star chart and a data base you could use the camera+compass to give a general location similar to how they used to use a sextant to do.
There are some sextant apps but i don't know if an open source one. There are many sky maps that are very accurate and if you even know the general location (ie what state you are in) you could use the camera to fine tune a sky map(with major constellations only) to a very accurate location.
A cool tool that should work on land or sea. And educational.
I would think technically you could even find an accurate time for your location via a star chart also.

Thank you, I have plans to add this. See the following existing issues:

https://github.com/kylecorry31/Trail-Sense/issues/1919
https://github.com/kylecorry31/Trail-Sense/issues/1920
https://github.com/kylecorry31/Trail-Sense/issues/1809

These contain the background research and some feasibility concerns.

You don't need all the peak data that a peak finder uses, you could get by with maybe 10% for major peaks only  which might be only 5mb for the USA or Canada
On October 18, 2024 3:41:11 PM PDT, Kyle Corry @.***> wrote:

Get location by triangulation of mountain peaks.
Use a peak finder app like https://github.com/woheller69/PeakOrama
Then use the camera and onboard compass to mark known peaks (more would give better accuracy) and use the peak details and a vector map (like mapforge maps) to draw lines from peaks via compass bearing and where the lines intersect is where you should be in the map.
I have never seen any app do this but it really should not be hard i don't think. Most everything you need is already open source. Peak details and data base Compass and camera info Mapforge map display.

Thank you for the suggestion. I believe the tool you are looking for in Trail Sense is the Augmented Reality tool. That will display nearby beacons as an overlay.
As for adding peak data, unfortunately it is not feasible for Trail Sense to add that because of the following:

It requires too much data to package with the app, might be possible with the plugins (see #1540 )
If they are not packaged with Trail Sense, then it would need to look them up over the internet, which is what PeakOrama does. This is not compatible with Trail Sense's lack of Internet permissions

--
Reply to this email directly or view it on GitHub:
https://github.com/kylecorry31/Trail-Sense/issues/1911#issuecomment-2423333318
You are receiving this because you commented.
Message ID: @.***>

You don't need all the peak data that a peak finder uses, you could get by with maybe 10% for major peaks only which might be only 5mb for the USA or Canada
…
On October 18, 2024 3:41:11 PM PDT, Kyle Corry @.> wrote: > Get location by triangulation of mountain peaks. > > Use a peak finder app like https://github.com/woheller69/PeakOrama > > Then use the camera and onboard compass to mark known peaks (more would give better accuracy) and use the peak details and a vector map (like mapforge maps) to draw lines from peaks via compass bearing and where the lines intersect is where you should be in the map. > > I have never seen any app do this but it really should not be hard i don't think. Most everything you need is already open source. Peak details and data base Compass and camera info Mapforge map display. Thank you for the suggestion. I believe the tool you are looking for in Trail Sense is the Augmented Reality tool. That will display nearby beacons as an overlay. As for adding peak data, unfortunately it is not feasible for Trail Sense to add that because of the following: 1. It requires too much data to package with the app, might be possible with the plugins (see #1540 ) 2. If they are not packaged with Trail Sense, then it would need to look them up over the internet, which is what PeakOrama does. This is not compatible with Trail Sense's lack of Internet permissions -- Reply to this email directly or view it on GitHub: #1911 (comment) You are receiving this because you commented. Message ID: @.>

Unfortunately, the most I would be willing to allocate is about 100 - 300 KB for this in the base Trail Sense app.

I don't know how many peaks you could do with that much data honestly. But why not have a download option for extra area (state or country) data. There are a LOT of new devices that don't have a GPS now. Pixel tablet, Amazon devices and a lot of lower end phones.
You know what is best for your app.
Knowing your Location is the number#1 thing people need to know outdoors.
On October 18, 2024 3:45:54 PM PDT, Kyle Corry @.***> wrote:

You don't need all the peak data that a peak finder uses, you could get by with maybe 10% for major peaks only which might be only 5mb for the USA or Canada
…
On October 18, 2024 3:41:11 PM PDT, Kyle Corry @.> wrote: > Get location by triangulation of mountain peaks. > > Use a peak finder app like https://github.com/woheller69/PeakOrama > > Then use the camera and onboard compass to mark known peaks (more would give better accuracy) and use the peak details and a vector map (like mapforge maps) to draw lines from peaks via compass bearing and where the lines intersect is where you should be in the map. > > I have never seen any app do this but it really should not be hard i don't think. Most everything you need is already open source. Peak details and data base Compass and camera info Mapforge map display. Thank you for the suggestion. I believe the tool you are looking for in Trail Sense is the Augmented Reality tool. That will display nearby beacons as an overlay. As for adding peak data, unfortunately it is not feasible for Trail Sense to add that because of the following: 1. It requires too much data to package with the app, might be possible with the plugins (see #1540 ) 2. If they are not packaged with Trail Sense, then it would need to look them up over the internet, which is what PeakOrama does. This is not compatible with Trail Sense's lack of Internet permissions -- Reply to this email directly or view it on GitHub: #1911 (comment) You are receiving this because you commented. Message ID: @.>

Unfortunately, the most I would be willing to allocate is about 100 - 300 KB for this in the base Trail Sense app.
--
Reply to this email directly or view it on GitHub:
https://github.com/kylecorry31/Trail-Sense/issues/1911#issuecomment-2423336871
You are receiving this because you commented.
Message ID: @.***>

I don't know how many peaks you could do with that much data honestly. But why not have a download option for extra area (state or country) data. There are a LOT of new devices that don't have a GPS now. Pixel tablet, Amazon devices and a lot of lower end phones. You know what is best for your app. Knowing your Location is the number#1 thing people need to know outdoors.
…
On October 18, 2024 3:45:54 PM PDT, Kyle Corry @.> wrote: > You don't need all the peak data that a peak finder uses, you could get by with maybe 10% for major peaks only which might be only 5mb for the USA or Canada > … > On October 18, 2024 3:41:11 PM PDT, Kyle Corry @.> wrote: > Get location by triangulation of mountain peaks. > > Use a peak finder app like https://github.com/woheller69/PeakOrama > > Then use the camera and onboard compass to mark known peaks (more would give better accuracy) and use the peak details and a vector map (like mapforge maps) to draw lines from peaks via compass bearing and where the lines intersect is where you should be in the map. > > I have never seen any app do this but it really should not be hard i don't think. Most everything you need is already open source. Peak details and data base Compass and camera info Mapforge map display. Thank you for the suggestion. I believe the tool you are looking for in Trail Sense is the Augmented Reality tool. That will display nearby beacons as an overlay. As for adding peak data, unfortunately it is not feasible for Trail Sense to add that because of the following: 1. It requires too much data to package with the app, might be possible with the plugins (see #1540 ) 2. If they are not packaged with Trail Sense, then it would need to look them up over the internet, which is what PeakOrama does. This is not compatible with Trail Sense's lack of Internet permissions -- Reply to this email directly or view it on GitHub: [#1911 (comment)](#1911 (comment)) You are receiving this because you commented. Message ID: @.> Unfortunately, the most I would be willing to allocate is about 100 - 300 KB for this in the base Trail Sense app. -- Reply to this email directly or view it on GitHub: #1911 (comment) You are receiving this because you commented. Message ID: @.>

As mentioned, one of the core principles of Trail Sense is that it doesn't use the Internet permission, therefore downloading is not an option. The plugins issue linked above will allow the ability to download data. If someone were to assemble GPX files for all regions that contain waypoints of the mountain peaks, I can link to that as a resource on the Trail Sense website though - I unfortunately do not have time to do that at the moment, and will likely implement plugins before I get around to that.

I don't know how many peaks you could do with that much data honestly. But why not have a download option for extra area (state or country) data. There are a LOT of new devices that don't have a GPS now. Pixel tablet, Amazon devices and a lot of lower end phones. You know what is best for your app. Knowing your Location is the number#1 thing people need to know outdoors.
…
On October 18, 2024 3:45:54 PM PDT, Kyle Corry @.> wrote: > You don't need all the peak data that a peak finder uses, you could get by with maybe 10% for major peaks only which might be only 5mb for the USA or Canada > … > On October 18, 2024 3:41:11 PM PDT, Kyle Corry<EMAIL_ADDRESS>wrote: > Get location by triangulation of mountain peaks. > > Use a peak finder app like https://github.com/woheller69/PeakOrama > > Then use the camera and onboard compass to mark known peaks (more would give better accuracy) and use the peak details and a vector map (like mapforge maps) to draw lines from peaks via compass bearing and where the lines intersect is where you should be in the map. > > I have never seen any app do this but it really should not be hard i don't think. Most everything you need is already open source. Peak details and data base Compass and camera info Mapforge map display. Thank you for the suggestion. I believe the tool you are looking for in Trail Sense is the Augmented Reality tool. That will display nearby beacons as an overlay. As for adding peak data, unfortunately it is not feasible for Trail Sense to add that because of the following: 1. It requires too much data to package with the app, might be possible with the plugins (see #1540 ) 2. If they are not packaged with Trail Sense, then it would need to look them up over the internet, which is what PeakOrama does. This is not compatible with Trail Sense's lack of Internet permissions -- Reply to this email directly or view it on GitHub: [#1911 (comment)](#1911 (comment)) You are receiving this because you commented. Message ID<EMAIL_ADDRESS>Unfortunately, the most I would be willing to allocate is about 100 - 300 KB for this in the base Trail Sense app. -- Reply to this email directly or view it on GitHub: #1911 (comment) You are receiving this because you commented. Message ID: @.**_>

As mentioned, one of the core principles of Trail Sense is that it doesn't use the Internet permission, therefore downloading is not an option. The plugins issue linked above will allow the ability to download data. If someone were to assemble GPX files for all regions that contain waypoints of the mountain peaks, I can link to that as a resource on the Trail Sense website though - I unfortunately do not have time to do that at the moment, and will likely implement plugins before I get around to that.

I created this issue to accept community contributions: https://github.com/kylecorry31/Trail-Sense/issues/2587

Continued in https://github.com/kylecorry31/Trail-Sense/issues/2590


Robocop should not parse directory recursively by default, only with option enabled from cli

If I think longer about this, I think by default it should parse recursively and give option to disable it. What do you think @mnojek?
Or not parse recursively but warn about this in console window. So people will know that files could be skipped due to this setting


Hello world with Buf examples, starting from Java

At the moment, the documentation contains a non-trivial example for Kotlin, which is a little counterintuitive. I propose the documentation offer "hello world"-style examples that only focus on the specific of setting up Connect in a specific language, leaving more advanced features and use cases in a separate section of the doc.
Also, since Java is still a popular language, and Kotlin is Java compatible, probably it would be great to have a "Getting started with Java" that mentions that the code generated is in Kotlin, and you need a certain setup, but you can use Connect when coding in Java
Reference: https://connectrpc.com/docs/kotlin/getting-started/

Hey @edmondop! We intended the Swift and Kotlin implementations to be primarily for mobile developers - that's why they're client-only. Eventually, a full Java implementation would be great. (If you're interested, leave a response on https://github.com/orgs/connectrpc/discussions/11.)
All that said, we should provide a simpler example for server-side Java developers to get started with our Kotlin clients. It probably won't happen soon unless you'd like to open a PR 😉, but we'll get to this eventually!

Reference in new iss

I'll open myself a PR soon :) I would have liked to do this sooner but I was too busy:)


"Named export 'LinkItem' not found" when running "astro build"

I run into this error when I try building my site :
> astro build

file:///Users/cody/workspace/pokedex/node_modules/astro-sitemap/dist/index.js:340
import { SitemapItemLoose as SitemapItemLoose2, LinkItem, EnumChangefreq } from "sitemap";
                                                ^^^^^^^^
SyntaxError: Named export 'LinkItem' not found. The requested module 'sitemap' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'sitemap';
const { SitemapItemLoose: SitemapItemLoose2, LinkItem, EnumChangefreq } = pkg;

    at ModuleJob._instantiate (node:internal/modules/esm/module_job:127:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:193:5)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:337:24)

Thanks for issue.
It's fixed in v0.2.7


0.5.1: Word Count Missing

Just noticed Word Count seems to be missing in the Preview page for this version.
It was working on 0.4.0

Hi @flikteoh, I'm looking into this bug, and can't reproduce on 0.5.1. Could you let me know what version of Ghost (*not Ghost Desktop), you're running?
Thanks!
Bhargav

Hey @bnookala I'm on Ghost 0.8.0

Hey @bnookala @ErisDS @felixrieseberg
Regarding to this editor issue and the word count problem.
So this HTTP2 Preload Headers thingy suddenly strike my mind this afternoon.
I had it removed on one of my blog (Blog A) and both word counts and the editor is now working magically fine.
While my another blog (Blog B) have exact match of all the setup of Blog A with the Preload Headers in place, the editor is remained as blank screen.
Not sure if both of them are related. But my problems are solved by removing the preload header thingy.
Thanks.

@flikteoh Can you elaborate on the HTTP2 Preload Headers? Are you talking about the preload link attribute? https://w3c.github.io/preload/#server-push-http-2

Hi @bnookala
I was actually referring to one of the new feature release on HTTP2 Preload Header for Ghost 0.8.0
I've added preloadHeaders: 100 into my ghost config file and it stopped the Ghost Desktop editing and word count from working.
Now that I have removed it, everything was back to working normal again.

@flikteoh Thanks for your feedback, this will be useful to us, and I'll let the Ghost team know that it appears to be causing issues within the desktop app. For now, I'm closing this issue, since it doesn't appear to be related to Ghost Desktop itself :)


wallmount generator has no reason to exist

Description
costs the same as apu but apu makes 6kw instead of 3kw
apu should be more expensive/complicated to make
Reproduction
yes

will fix after rock and stone


add support for multiple redirects

Fixes #144

This change is

Reviewed 4 of 4 files at r1.
Review status: all files reviewed, 1 unresolved discussion (waiting on @vlukashov)

a discussion (no related file):
I propose to add a cyclic redirect test and fix it.

Comments from Reviewable

Review status: all files reviewed, 1 unresolved discussion (waiting on @vlukashov)

a discussion (no related file):
Previously, SomeoneToIgnore (Kirill Bulatov) wrote…
I propose to add a cyclic redirect test and fix it.

https://github.com/vaadin/vaadin-router/pull/196

Comments from Reviewable

Reviewed 4 of 4 files at r2.
Review status: :shipit: complete! all files reviewed, all discussions resolved

Comments from Reviewable

Review status: 3 of 4 files reviewed, all discussions resolved (waiting on @SomeoneToIgnore and @web-padawan)

src/router.js, line 379 at r2 (raw file):
Previously, web-padawan (Sergey Kulikov) wrote…
BTW can use log() to prepend the "Vaadin.Router" to error text.
Not a blocker, we can revisit error texts later.

done

Comments from Reviewable

Reviewed 1 of 1 files at r3.
Review status: :shipit: complete! all files reviewed, all discussions resolved

Comments from Reviewable

Reviewed 1 of 1 files at r3.
Review status: :shipit: complete! all files reviewed, all discussions resolved

Comments from Reviewable


Added GitHub page as homepage, otherwise RubyGems.org doesn't provide…

...a link to GitHub.

thanks, its going in the next version.


Cache input issue

Flask caching with objects as input introduces a risk of not capturing changes in the object.
Read the warning under memoization in the Flask documentation. Flask only checks the repr() of the object in the input, which might not by unique. The issue has been encountered with Pandas in Webviz, but can occur with any object instance that doesn't have a unique repr() output.
Temporary solution is to avoid using other input types than basic Python types for @CACHE.memoize decorated methods. E.g. converting DataFrames to dict.

Yes, complex objects needs to have a unique __repr__ representation in order to be cached correctly by flask-cache.
Would be interesting to investigate how costly turning it into simple structures (e.g. dict) versus hashing the content is. If the latter is faster (I would perhaps expect it to be), and caching of dataframes is necessary (maybe for most use cases it is not necessary?), one solution (which would solve the problem for all plugins, but at the same time is quite hacky) is to monkey-patch the pandas.DatafFrame __repr__ function by appending a hash of the data in the DataFrame __repr__.

Since pandas.DataFrame and pandas.Seriesare so commonly used, and they don't have a well-behainv __repr__ in the context of using it as cache has, we could perhaps investigate special-casing them and use pandas.util.hash_pandas_object(some_df) instead of __repr__ for those types.


[MODFQMMGR-87] Use new centralized lib patterns

Jira MODFQMMGR-87
https://github.com/folio-org/lib-fqm-query-processor/pull/13 removes essentially the entire org.folio.fqm.lib package, with the exception of FqlValidationService, which is moved to org.folio.fql.lib.  It also adds spring autowiring/etc support to the FQL services.
This PR updates mod-lists to accept these new beans and packages.
SHOULD BE MERGED AFTER https://github.com/folio-org/lib-fqm-query-processor/pull/13

Whoops, forgot to mark this PR as a draft.


Chrome warning: non-passive mousewheel listeners

monaco-editor version: 0.14.6
Browser: Chrome
OS: macOS
I noticed that Chrome's dev tools in verbose mode includes a handful of identical warnings when loading Monaco:

[Violation] Added non-passive event listener to a scroll-blocking 'mousewheel' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952

I'm not sure if there's an intentional reason why these event listeners aren't passive or if it was just an oversight, but I thought I'd surface it in case others also hadn't noticed these warnings.

This is intentional. The editor uses those events to paint only the current visible viewport of the editor.

Is it a bug in Chrome that it warns on these?

It is a hint that Chrome shows to developers that introduces a new possibility (at the time) for scroll listeners, with the passive flag. I have seen the hint, am aware of it, but our use-case is valid and we cannot use the passive flag. I don't know if there is a way to explain that to Chrome to have it not print these messages anymore.

You can avoid the warning if the code that adds the event listener actually specifies passive: true or passive: false.  If the passive attribute is set either way it will not warn.

Had a chat with Nzolghadr@chromium, we can change the link to the explainer which has more information:
https://github.com/WICG/EventListenerOptions/blob/gh-pages/explainer.md


Derive Debug, PartialEq and Eq for more types

Closes #28

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @adamgreig (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

bors r+


Channel naming change broke the build

Steps to Reproduce
https://github.com/flutter/flutter/pull/9270 seems to have broken the build.
Logs
    :1:1: warning: umbrella header for module 'Flutter' does not include header 'FlutterAsyncMessageListener.h' [-Wincomplete-umbrella]
    #import "Headers/Flutter.h"
    ^
    :1:1: warning: umbrella header for module 'Flutter' does not include header 'FlutterJSONMessageListener.h' [-Wincomplete-umbrella]
    :1:1: warning: umbrella header for module 'Flutter' does not include header 'FlutterMessageListener.h' [-Wincomplete-umbrella]
    3 warnings generated.
    /Users/mac4/.cocoon/flutter/examples/platform_channel/ios/Runner/AppDelegate.m:72:8: error: use of undeclared identifier '_eventReceiver'
      if (!_eventReceiver) return;
           ^
    3 warnings and 1 error generated.

    CompileC /Users/mac4/.cocoon/flutter/examples/platform_channel/build/ios/Runner.build/Release-iphoneos/Runner.build/Objects-normal/arm64/main.o Runner/main.m normal arm64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
        cd /Users/mac4/.cocoon/flutter/examples/platform_channel/ios
        export LANG=en_US.US-ASCII
        export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/opt/dart/libexec/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
        /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c -arch arm64 -fmessage-length=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -std=gnu99 -fobjc-arc -fmodules -gmodules -fmodules-prune-interval=86400 -fmodules-prune-after=345600 -fbuild-session-file=/var/folders/y2/jg40j9852qx7sdc998yvwt7w0000gn/C/org.llvm.clang/ModuleCache/Session.modulevalidation -fmodules-validate-once-per-build-session -Wnon-modular-include-in-framework-module -Werror=non-modular-include-in-framework-module -Wno-trigraphs -fpascal-strings -Os -fno-common -Wno-missing-field-initializers -Wno-missing-prototypes -Werror=return-type -Wunreachable-code -Wno-implicit-atomic-properties -Werror=deprecated-objc-isa-usage -Werror=objc-root-class -Wno-arc-repeated-use-of-weak -Wduplicate-method-match -Wno-missing-braces -Wparentheses -Wswitch -Wunused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wempty-body -Wuninitialized -Wconditional-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wbool-conversion -Wenum-conversion -Wshorten-64-to-32 -Wpointer-sign -Wno-newline-eof -Wno-selector -Wno-strict-selector-match -Wundeclared-selector -Wno-deprecated-implementations -DNS_BLOCK_ASSERTIONS=1 -DOBJC_OLD_DISPATCH_PROTOTYPES=0 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS10.3.sdk -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -miphoneos-version-min=8.0 -g -fvisibility=hidden -Wno-sign-conversion -Winfinite-recursion -iquote /Users/mac4/.cocoon/flutter/examples/platform_channel/build/ios/Runner.build/Release-iphoneos/Runner.build/Runner-generated-files.hmap -I/Users/mac4/.cocoon/flutter/examples/platform_channel/build/ios/Runner.build/Release-iphoneos/Runner.build/Runner-own-target-headers.hmap -I/Users/mac4/.cocoon/flutter/examples/platform_channel/build/ios/Runner.build/Release-iphoneos/Runner.build/Runner-all-target-headers.hmap -iquote /Users/mac4/.cocoon/flutter/examples/platform_channel/build/ios/Runner.build/Release-iphoneos/Runner.build/Runner-project-headers.hmap -I/Users/mac4/.cocoon/flutter/examples/platform_channel/build/ios/Release-iphoneos/include -I/Users/mac4/.cocoon/flutter/examples/platform_channel/build/ios/Runner.build/Release-iphoneos/Runner.build/DerivedSources/arm64 -I/Users/mac4/.cocoon/flutter/examples/platform_channel/build/ios/Runner.build/Release-iphoneos/Runner.build/DerivedSources -F/Users/mac4/.cocoon/flutter/examples/platform_channel/build/ios/Release-iphoneos -F/Users/mac4/.cocoon/flutter/examples/platform_channel/ios/Flutter -MMD -MT dependencies -MF /Users/mac4/.cocoon/flutter/examples/platform_channel/build/ios/Runner.build/Release-iphoneos/Runner.build/Objects-normal/arm64/main.d --serialize-diagnostics /Users/mac4/.cocoon/flutter/examples/platform_channel/build/ios/Runner.build/Release-iphoneos/Runner.build/Objects-normal/arm64/main.dia -c /Users/mac4/.cocoon/flutter/examples/platform_channel/ios/Runner/main.m -o /Users/mac4/.cocoon/flutter/examples/platform_channel/build/ios/Runner.build/Release-iphoneos/Runner.build/Objects-normal/arm64/main.o

Encountered error while building for device.
Task failed: Executable failed with exit code 1.

Complete log file
@mravn-google

Fix in progress

👍


Enhancement support 'microseconds_add' function for datetimev2

Proposed changes
Issue Number: close #16967
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[x] Has unit tests been added
[x] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

@Gabriel39 @yangzhg

run buildall

@jackwener @morrySnow PTAL, thank you.

cc @BiteTheDDDDt

run buildall

@BiteTheDDDDt PTAL, thank you

@BiteTheDDDDt Is this pr ok to merge? Or may you invite some other committers review? Thank you :)


Add organization zvmexporter and repository zvm_exporter

OSSC Proposal number: SYS144920160509
Project name: z/VM Exporter
Proposer: Ye Na Rhee/Germany/IBM
Proposer backups: Juergen Leopold/Germany/IBM

@yrhee This LGTM but needs to be rebased so that it can be merged. Thanks

@yrhee please rebase and resolve any merge conflicts... thanks

I'm cleaning up old PRs -- @yrhee I checked the zvmexporter org and not much is going on there since 2016. Please confirm if this change is still desired.

Closing PR as it's inactive


Remove JCenter dependency

JCenter has been deprecated and should be removed from build.gradle.
https://blog.gradle.org/jcenter-shutdown
If I remove jcenter() from the build.gradle file, I get a Kotlin not supported warning in Android Studio.
Consider putting the remaining dependencies onto Maven or somewhere else.

Fixed per https://github.com/SAP/gigya-flutter-plugin/commit/6c52065e6223816189d6b7b257d88b6919457774


Didn't update my stream last commit

Make sure the confirm modal is always the top most open modal

I really need this in a production environment, any way you can expedite this? thanks!

Sorry, it fell off my list. Reviewed, care to amend and resend? Thanks :smile:


Show matching study in the list of DARs

If a study accession exists matchign the phs, show it in the DAR table on the DAR snapshot page.

Closed by #579


Set up seed db scripts

Basic Information
Use prisma to create database seeding script(s) to make testing easier (once some models have been made). This will be continuously maintained as part of other branches.
Other Information
https://www.prisma.io/docs/guides/migrate/seed-database

Blocked by #19


Dated video

Video is helpful but quite dated.  Any updates in the last 7 years that would be helpful to know?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: c3deb045-565e-169b-ecd4-6f0f07c966e4
Version Independent ID: 1bd84f68-4820-4d11-aafc-da1657bddc80
Content: Security baselines guide
Content Source: windows/security/threat-protection/windows-security-configuration-framework/windows-security-baselines.md
Product: windows-client
Technology: itpro-security
GitHub Login: @vinaypamnani-msft
Microsoft Alias: vinpa

Thanks @tbiles for the feedback. We're not aware of any updated video content. @jmunck do you know?
@yogkumgit - assigning to you. After a quick chat with Vinay, let's remove the embedded video, but add a link to it in the "see also" section. As noted, it's still helpful. Unless Rick has any additional suggestions to add.

Hi @aczechowski unfortunately we don't have any other videos. I'd be happy to work with folks on some though!

@tbiles Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/windows-itpro-docs/pull/11406
Once the author approves, the changes will be live.
Thanks
Sri


Remove dependency on node-gyp.

Feature Request
Do not have any direct or transitive dependence on node-gyp.
Summary
Currenty, node-gyp is required to use Embark.  This creates a notable barrier to entry because node-gyp depends on a ton of OS/architecture specific build tools including make, gcc, python, VC++, etc. (depending on OS).  There is really no reason Embark needs node-gyp as all of Ethereum's crypto can be done with pure JS library alternatives.
Running into the transitive dependency on node-gyp has caused me to look elsewhere for frameworks to use, as in my experience any project with a dependency on node-gyp ends up causing me no end of headache.  I'm filing this issue in an effort to encourage the Embark developers to drop the node-gyp dependency so that future users don't get turned away from the project like I have.

node-gyp is strictly required by several of our transitive dependencies, i.e. dependencies of our dependencies. This is a problem facing many libraries and frameworks in the Ethereum ecosystem since some of the cryptographic primitives required for Ethereum related things aren't provided by the runtime and pure-JS implementations tended to be slow. The situation is improving across the ecosystem, but it will be some time before we can fully eliminate all dependencies and transitive dependencies that rely on node-gyp for compiling crypotgraphy related functions implemented in C/C++.

Embark isn't running a miner, so I am dubious about the need for fast crypto here.  Which libraries are you unable to get rid of due to transitive dependencies?  In my experience, there are solutions available for solving most/all problems without having to pull in something with a transitive dependency on node-gyp.  For example, ethereumjs-util is notoriously bad at pulling in unnecessarily complicated transitive dependencies, several of which require node-gyp, but a project can simply not use ethereumjs-util and instead use something else.
Note: I do acknowledge that migrating away from some of these bad libraries is not a trivial task, but it is one that it feels like is worth having on the roadmap and working toward over time.  FWIW, I have tried lobbying to get some of the common ecosystem libraries to fix their packages and stop depending on node-gyp, but I haven't had much luck.  My solution has been to just drop those dependencies in my projects in favor of something else and/or create alternatives where alternatives didn't exist.

the need for fast crypto [in JavaScript contexts]

I'm generally agreed, as are some of the folks that work on EthereumJS libs and the maintainer of web3.js; and probably other lib/framework maintainers as well, but those are the ones I've communicated with directly regarding this very problem.
What we have in mind:  libs should first check if the runtime, e.g. Node.js, provides a built-in KDF or hash, etc., and use it if it's available. If it's not available, then fallback to a pure-JS implementation. In some cases, the lib can also check if a native-module implementation is resolvable, e.g. with Node's require.resolve, and use that instead of the pure-JS implementation (in the case a built-in isn't available and the user elected to install such a module). I personally implemented such an approach for the scrypt KDF and it's used by<EMAIL_ADDRESS>
Embark isn't running a miner

scrypt, keccak-256, and secp256k1 are examples of non-mining crypto facilities involved in Ethereum keystores, keys, and signing-verifying transactions. Regarding what I wrote above about "[w]hat we have in mind", the reality today is that many Ethereum-related libraries don't yet take that approach and instead rely on implementations that involve node-gyp.
The Embark team, as well as other lib/framework devs in this space, are hoping for and working toward an improved situation for the overal Ethereum-JavaScript ecosystem, but it will take a bit of time. The problem is amplified when one's dependency tree involves dependencies-of-dependencies-of-dependencies that are using older versions of libraries (that depend on node-gyp) and the "fork to solve" approach of solving this kind of problem gets much messier.

@michaelsbradleyjr Please can you help me solve an issue i have been facing with node-gyp for like 3 days now

I have been struggling with it for some days now.
Tried all possible solutions I could find online but no luck