Yep, but:
Also if you use sqlite tile storage, there are so far no other navigation apps with support for the format other than modRana. This might change in the future as the format is open & documented here and the Cloud GPS developer mentioned having support for it on his roadmap.

I think most probably support this through their configuration files.

This is actually already a ticket for this from a long time ago. A new table in the POI database with rows bound to the POI ids would be needed. This table would store all the various alarms (more than one alarm per POI would be supported) & their metadata (distance, beep/spoken message, enabled/disabled, etc.). and you would have to assure that alarms are removed when a POI is deleted (this might be automatic given proper key arrangements are done in the database).

While I still think this is the proper way for implementing POI based alarms, your question got me thinking it there is another, more simple way how for handling alarms.

I asked myself a couple questions:

• do the alarms need to be bound to POI after all ?
• how to easily add an alarm without making a POI ?
• how to make it easy for users to add many alarms at once (eq. with a script that generates them from a list of speed-limits/whatever) ?

Result: Plain-text alarm lists !
The alarms would be just stored in one or more plain-text files, one alarm per row with CSV notation.

Row notation might look like this:
Explanation:
lat - latitude in decimal format
lon - longitude in decimal format
distance - trigger distance
enabled - 1 = enabled, 0 = disabled
name - displayed name
alert - any string other than BEEP or SAY would go directly to text-to-speech, BEEP triggers some default alarm sound, SAY: says whats after the colon (so you can SAY:BEEP )

What about elevation ?
A friend of mine is a glider pilot so the idea of 3D alarm coordinates has crossed my mind. Still, I want the format be as simple as possible (so that users can basically just generate the lists in excel/calc) and elevation would probably not bee needed 99% of the time. As a result, elevation support can be added in the future - probably into the distance field with some prefix (eq. ELEV:375,200)

How to add new alarms ?
There would be two ways: editing the alarm lists from the outside (just create a valid list and modRana will be able to use it) or interactively inside modRana (create new lists, add alarms from map/poi/coordinates, enabled/disable alarms, activate/deactivate alarm lists).

And now the most important thing:
What do you thing about this idea ?

• did I forgot about some essential alarm parameter ?
• any ideas for a better row format or an other technical solution overall ?
• implementation/scalability concerns ?
• or anything else ?