I suggest adding iGate Digipeater symbol to the UI.
It is a green star with letter I.
"overlay": "I",
"symbol": "#",
This will be a common use-case.
I suggest adding iGate Digipeater symbol to the UI.
It is a green star with letter I.
```
"overlay": "I",
"symbol": "#",
```
This will be a common use-case.
<!-- github-sync-id:2498760374 -->
It has always been there in the UI. Or do you mean something different?

It has always been there in the UI. Or do you mean something different?
<!-- github-comment-id:2322853010 -->
Green star with I is "I-gate equipped digipeater" (I#)
Green star with L is "WIDEn-N with path length trapping" (L#)
My node is an I-gate equipped digipeater.
It works in the JSON config, just not in the UI.
According to https://github.com/PhirePhly/aprs_notes/blob/master/digipeater_symbol_selection.md and http://aprs.org/symbols/symbols-new.txt
Green star with I is "I-gate equipped digipeater" (I#)
Green star with L is "WIDEn-N with path length trapping" (L#)
My node is an I-gate equipped digipeater.
It works in the JSON config, just not in the UI.
<!-- github-comment-id:2322854903 -->
The current usage of L# for an I-gate equipped LoRa digipeater is logical, but the reference symbol table doesn't define a symbol for this combination, so you would like to fall back to the "generic digipeater with igate" symbol. Perhaps a new symbol should be requested for this from aprs.org ?
Ah, uppercase I vs. lowercase L makes your comment clearer. Per http://aprs.org/symbols/symbols-new.txt the following two symbols are used for gateways:
I& = Igate Generic (please use more specific overlay)
L& - Lora Igate
However, for digipeaters there is no analogy, becase L# is already used for something else.
I# - I-gate equipped digipeater
L# - WIDEn-N with path length trapping
The current usage of L# for an I-gate equipped LoRa digipeater is logical, but the reference symbol table doesn't define a symbol for this combination, so you would like to fall back to the "generic digipeater with igate" symbol. Perhaps a new symbol should be requested for this from aprs.org ?
<!-- github-comment-id:2322859548 -->
Thank you for pointing out the LoRa-specific symbols/overlays. Since there is no perfect answer for this situation, I will make a local choice.
Up to you / the other contributors whether to adopt my suggestion or not, I am happy either way.
IMHO L# has no place in LoRa_APRS_iGate but it is present, however I'm not requesting its removal. La and L_ also appear in the UI and appear to be non-standard, same applies.
<option value="L#">
Green star with L
</option>
<option value="L_">
Blue circle with L
</option>
<option value="L&">
Black diamond with L
</option>
<option value="La">
Red diamond with L
</option>
Thank you for pointing out the LoRa-specific symbols/overlays. Since there is no perfect answer for this situation, I will make a local choice.
Up to you / the other contributors whether to adopt my suggestion or not, I am happy either way.
IMHO `L#` has no place in LoRa_APRS_iGate but it is present, however I'm not requesting its removal. `La` and `L_` also appear in the UI and appear to be non-standard, same applies.
```
<option value="L#">
Green star with L
</option>
<option value="L_">
Blue circle with L
</option>
<option value="L&">
Black diamond with L
</option>
<option value="La">
Red diamond with L
</option>
```
<!-- github-comment-id:2322861274 -->
L_ is requred for aprs.fi to process the weather info, they trigger on blue color of the symbol. As a user, I would like to see these real-world use cases reflected back in the formal standard, but I don't know the process. Having said that, I think it is better to leave this decision to CA2RXU, it's his project.
L_ is requred for aprs.fi to process the weather info, they trigger on blue color of the symbol. As a user, I would like to see these real-world use cases reflected back in the formal standard, but I don't know the process. Having said that, I think it is better to leave this decision to CA2RXU, it's his project.
<!-- github-comment-id:2322864635 -->
Absolutely agree.
I've customised my fork to work a bit more how I'd like it to.
Adding the symbol I wanted:
<img width="410" alt="image" src="https://github.com/user-attachments/assets/38c00217-b4a1-4ca7-ae74-29e4c7a93b38">
Making it clear why `L_` is there, and showing the codes in the drop down list:
<img width="469" alt="image" src="https://github.com/user-attachments/assets/6e67af39-af5d-49f2-bdea-6659184e6aac">
Adding a `?` symbol when there isn't an icon provided:
<img width="413" alt="image" src="https://github.com/user-attachments/assets/7e3a6ac3-3bd9-46e4-9665-bbd048f9831b">
Feel free to adopt the commit, or not.
https://github.com/M0LTE/LoRa_APRS_iGate/commit/1d6adde
<!-- github-comment-id:2322874796 -->
I think some caution is needed here, the standard for symbols on Aprs.org specifies a Digipeater as a green star with white centre. It doesn’t seem to specify a preferred overlay for anything specific, hence different projects seem to have adopted their preferred overlay. There is a good practical argument for using L as the overlay for all things Lora. If I am looking for Lora Digi’s and/or igates L is very helpful. It also seems the L is already widely in use in the UK for Lora nodes.
I think some caution is needed here, the standard for symbols on Aprs.org specifies a Digipeater as a green star with white centre. It doesn’t seem to specify a preferred overlay for anything specific, hence different projects seem to have adopted their preferred overlay. There is a good practical argument for using L as the overlay for all things Lora. If I am looking for Lora Digi’s and/or igates L is very helpful. It also seems the L is already widely in use in the UK for Lora nodes.
<!-- github-comment-id:2323051918 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I suggest adding iGate Digipeater symbol to the UI.
It is a green star with letter I.
This will be a common use-case.
It has always been there in the UI. Or do you mean something different?
According to https://github.com/PhirePhly/aprs_notes/blob/master/digipeater_symbol_selection.md and http://aprs.org/symbols/symbols-new.txt
Green star with I is "I-gate equipped digipeater" (I#)
Green star with L is "WIDEn-N with path length trapping" (L#)
My node is an I-gate equipped digipeater.
It works in the JSON config, just not in the UI.
Ah, uppercase I vs. lowercase L makes your comment clearer. Per http://aprs.org/symbols/symbols-new.txt the following two symbols are used for gateways:
I& = Igate Generic (please use more specific overlay)
L& - Lora Igate
However, for digipeaters there is no analogy, becase L# is already used for something else.
I# - I-gate equipped digipeater
L# - WIDEn-N with path length trapping
The current usage of L# for an I-gate equipped LoRa digipeater is logical, but the reference symbol table doesn't define a symbol for this combination, so you would like to fall back to the "generic digipeater with igate" symbol. Perhaps a new symbol should be requested for this from aprs.org ?
Thank you for pointing out the LoRa-specific symbols/overlays. Since there is no perfect answer for this situation, I will make a local choice.
Up to you / the other contributors whether to adopt my suggestion or not, I am happy either way.
IMHO
L#has no place in LoRa_APRS_iGate but it is present, however I'm not requesting its removal.LaandL_also appear in the UI and appear to be non-standard, same applies.L_ is requred for aprs.fi to process the weather info, they trigger on blue color of the symbol. As a user, I would like to see these real-world use cases reflected back in the formal standard, but I don't know the process. Having said that, I think it is better to leave this decision to CA2RXU, it's his project.
Absolutely agree.
I've customised my fork to work a bit more how I'd like it to.
Adding the symbol I wanted:

Making it clear why

L_is there, and showing the codes in the drop down list:Adding a

?symbol when there isn't an icon provided:Feel free to adopt the commit, or not.
https://github.com/M0LTE/LoRa_APRS_iGate/commit/1d6adde
I think some caution is needed here, the standard for symbols on Aprs.org specifies a Digipeater as a green star with white centre. It doesn’t seem to specify a preferred overlay for anything specific, hence different projects seem to have adopted their preferred overlay. There is a good practical argument for using L as the overlay for all things Lora. If I am looking for Lora Digi’s and/or igates L is very helpful. It also seems the L is already widely in use in the UK for Lora nodes.