Steve;
Apologies in advance. I'm about to confuse the matter even more. EDACS is treated differently than Motorola. Here's a quick synopsis of why ...
1. P25 always has a site number and system id.
2. Motorola always has a system id and may (or not) have a site number.
3. EDACS always has a site number and never a system id.
4. MPT1327 has a (weak) system id and may have a weak site number.
5. LTR has not a system or site number.
By "weak", I mean the number may not be unique which means you can't assume that system "X" decoded today is the same as system "X" decoded yesterday.
Notice that EDACS does not have a system ID. We can't tell if site 1 and site 2 are part of the same network or completely different systems. To cope with handling two EDACS sites in the same area - the program treats the site number as a system id. That way - EDACS sites 1, 2, 3, etc. all get their own data files. To allow sharing EDACS data across sites - you can use the delegate feature to pull talkgroup and radio id data from another EDACS site.
For a given EDACS site that announces neighbors - you can see the list of neighboring sites in the [V]iew -> Stes list. The [V]iew -> Pr[o]ps display will tell you the number of neighbors (among other things).
So ... in the context of EDACS ... site 0 means "this" site. The displayed system number is the real site number.
-rick