It has been almost two years since the APRS function has displayed correctly on the place files. I’m unsure why it’s even listed as an option anymore since it doesn’t work.Thank you Mark. I may just put together my own script to produce an APRS list out of the APRS-IS stream. I was hoping not have to put that much work into it. But it seem like SN may or may not work on fixing this. So if SN works on this and needs help, let me know.
Thanks a bunch.
I am interested in creating a script or method to generate filtered place files from APRS too. I need to set up an iGate first though.Thank you Mark. I may just put together my own script to produce an APRS list out of the APRS-IS stream. I was hoping not have to put that much work into it. But it seem like SN may or may not work on fixing this. So if SN works on this and needs help, let me know.
I’ve used the custom SN place file on Allison House for a few years. The only drawback is the icon doesn’t indicate movement (you have to hover the cursor over the icon to see it). However, it doesn’t really matter with most SN users now converting to RadarScope because movement isn’t displayed. It is an option if you’re able to subscribe.After my initial post, I discovered that AllisonHouse.com provides a custom APRS placefile, in addition to custom SN placefile. The cost may not be for everyone, but it is an option I can use.
There lies the issue. From what I understand the APRS data is flowing into SN, but no one knows why the information isn't being transmitted to the various place files and apps.This thread is almost like a cold case murder file where you need to start from scratch with a fresh viewpoint and hope you find a detail that may have been overlooked. It would be nice if someone who understands the inner workings of APRS could remote into your computer using Team Viewer to take a look. That's taking support to a whole new level though on freeware!
I think the problem is people have been frustrated with this issue not being resolved in the two years since it started. No one knows or sees anything on the backend being done. All they see is what is being said in a “forum” style response, which at times has been less than empathetic by some on the SN board. Coming from someone that has worked in the customer service industry for over fifteen years, anytime you don’t empathize, assure, and understand where the user or customer is coming from, everyone suffers externally and internally as well.Was the support more timely before it was relocated to ST? If so we'll need to discuss that, probably in a new thread so we don't get off topic here.
Yep, the same person supports both and it is largely a shared code base which is why this is so brain wracking.Thanks for the update, @John Wetter and for all that y'all have been doing regarding this issue. I have a question... Has anyone looked at the APRS Tracker option on the Allison House site, how it operates, and how the data is transmitted outbound? Instead of having the system poll for the !SN! string, just have it poll the call/SSID of the user. I know I maybe grasping at straws, but just a thought.
It's a load-balanced setup but in general yes, it is the same system if I'm understanding the question correctly...@John Wetter, is all of the data flowing into SN on the same server or are there separate servers handling different things?
Edit: Sorry, I haven't had my coffee yet. I guess I'm asking if all requests are made to the same location in reference to APRS vs standard location updates?
I ran into a similar situation with an application I developed for GPS tracking. One component worked with a different protocol than the other, and running into the same endpoint caused issues that to this day I have no idea how it happened. I migrated one protocol to a different API endpoint, then converted the information into a readable format the application could use with the Google Maps API. Worked like a charm after that.It's a load-balanced setup but in general yes, it is the same system if I'm understanding the question correctly...