CHIRP

Here is an example: This, URL pulls the repeater in question ==>

https://www.repeaterbook.com/api/export.php?country=United%20States&callsign=K4ECR%

The Data is shown below, see my comment, it says it supports Analog, but Chirp won't copy it into the BoaFeng grid ...

{
  "count": 1,
  "results": [
    {
      "State ID": "12",
      "Rptr ID": "9936",
      "Frequency": "444.20000",
      "Input Freq": "449.20000",
      "PL": "100.0",
      "TSQ": "100.0",
      "Nearest City": "Navarre",
      "Landmark": "",
      "County": "Santa Rosa",
      "State": "Florida",
      "Country": "United States",
      "Lat": "30.43219948",
      "Long": "-86.87329865",
      "Precise": 0,
      "Callsign": "K4ECR",
      "Use": "OPEN",
      "Operational Status": "On-air",
      "ARES": "No",
      "RACES": "No",
      "SKYWARN": "No",
      "CANWARN": "No",
      "AllStar Node": "0",
      "EchoLink Node": "0",
      "IRLP Node": "0",
      "Wires Node": "81218",
      "FM Analog": "Yes",   // <==== HERE !!
      "DMR": "No",
      "DMR Color Code": "",
      "DMR ID": "",
      "D-Star": "No",
      "NXDN": "No",
      "APCO P-25": "No",
      "P-25 NAC": "",
      "M17": "No",
      "M17 CAN": "",
      "Tetra": "No",
      "Tetra MCC": "",
      "Tetra MNC": "",
      "System Fusion": "Yes",
      "YSF DG ID Uplink": "00",
      "YSF DG IS Downlink": "00",
      "YSF DSC": "Open",
      "Notes": "",
      "Last Update": "2021-02-04"
    }
  ]
}

Hey Mike,

Yeah, I understand the problem, it's just not very easy to change this in a compatible way. I've got some ideas and will be looking into them, but it's not a trivial fix.

In the meantime, the trivial workaround you can do is open a CSV tab (File -> New) and use it as an intermediate step, change the DN to FM and then copy it over to your other radio.

The two options I've thought of are:

1. An option in the repeaterbook query UI that says "I'd rather DN repeaters with FM capability be shown as FM instead". Perhaps that could just be assumed if the user only selects FM in the "limit to modes" dialog.
2. Some hidden stuff that stashes the FM-capable bit so the copy-paste/import routine knows it should convert them since the target radio doesn't support DN mode

The problem with #2 is that it will be confusing to people why they can copy DN memories from a repeaterbook tab to an unsupported radio, but not an actual DN radio. And the same goes for anything else like D-STAR, or NFM/FM, etc. Since CHIRP is maximally for compatibility and interchange, we have to be careful to preserve that principle.

The first one above is much less invasive, but requires the user to know about this sort of thing. It also requires a UI change (which isn't necessarily bad, it's just not fun work :P).

I completely understand, I wish Chirp was written in C# for .NET, I'm a software developer and work in the Azure Cloud, I also wrote EntitySpaces, see https://github.com/MikeGriffinReborn/EntitySpaces.

I just don't know Python, if I did I also make the grids sortable and saveable that way, no worries, we appreciate all you guys do for us !!!

It looks as though you made this possible? How will it work in the UI and will this be in the next release? Also, thank you !!!

I implemented the UI "convert to FM" approach, in today's build. Let me know if you think that's a reasonable workaround.

I just downloaded the new version, tried copying the entries from the repeaterbook integration for my county and it still does the same thing, just says I can becuase of DN, where was I supposed to get the prompt, or how do I convert to FM?

OMG this is so awesome, how did I miss that, thank you so much. I don't think you guys put out a bullet point list of new features on each build but this is a big one, as far as useability goes !!!