ElmerEmail APRS Commands
The APRS System VERY experimental and most likely will not work just yet.
APRS has the smallest text length response from ElmerEmail. APRS only allows a maximum of 60 or so characters per message, and because of this information sent back via APRS is necessarily small. ElmerEmail does not create "chains" of APRS messages, your response will be formatted to fit into a single message. Because of this, some commands are not available via APRS.
Many of the commands on ElmerEmail are location based. This is the argument {location} or {loc}. In commands where there is only ONE location argument, that argument is possibly optional. Many email services, such as WinLink, embed your current location in the email message headers (the "headers" are the parts of the email message you typically don't see or interact with). There is also a setting that allows you to specify a more permeant location for yourself. If there is only one {location} argument needed, and you did not send us a location in your request, our software will attempt to divine your location from the last last location your device reported to APRS.fi. If this is not available, or more than a few hours old, we will check to see if you have set a permeant location in the settings, and then use that location to fulfill the request. This makes it much easier to make location based requests, particularly if the request involves information from where you are right now.
A {location} could be blank (if you want to use your current or permeant location), a set of GPS coordinates in the decimal format latitude,longitude such as 35.9521,-85.0327 (note there is NO SPACE after the comma), a Maidenhead Grid Square such as EM75lw58, or just a place name/address such as Knoxville, TN or 6071 Buford Hwy Atlanta, GA.
If the location you entered was incorrectly formatted, or simple not found through geocoding, you may get an error reply
Commands and Subcommands sent to ElmerEmail are case insensitive, we convert them anyway to lower case for processing. Arguments however may be case sensitive depending on what the request you are making.
Examples are given in this format: commands subcommand|subcommand argument {argument}
Possible Subcommands are delimited by the pipe symbol "|". When you see the subcommand "self" this means that the command can be sent without any subcommands, though the arguments may vary, see the description for details.
Arguments that are encapsulated be the curly brackets "{}" are optional, Arguments without curly brackets "{}" are madatory. The argument name should give you some idea about what information is expected by that argument
Some commands require that arguments have "markers" on them. This could be something like from: to: start: end:, etc. Markers will always have colons ":" and be shown/noted in the example
Because we are still in the pre-release phase of this project, these commands, especially their examples, are not yet standardized nor fully correct
Here are a list of all the currently active ElmerEmail commands:
Here are a list of some of the ElmerEmail commands that will be working soon:
Sends an SMS Text message to the number given.
Sends back the location of a given {callsign,email} as last recorded by ElmerEmail only if the user has allowed their location to be shared.
Sends an Email to {address}