Geocoding in Radian is done in SQL (for now... there will be point and click templates added to the Transform dialog later on).
Launch the command window and enter geocode in the filter box to see the functions. Data sources are the various geocoding servers that are supported, which you can useNew Data Source to create. In the Type box enter Web Server: geocodeserver and that will give you a list of geocoding servers you can use, similar to how you can get a list of built-in imageservers. It's a big list, and the legacy geocoding database (TIGER/Line) used in Release 8 can also be used via other types.
Suppose we create a geocoding server data source called GoogleG using the google geocoding server. We have a table called adds (short for addresses) and it has a field called address. The address has addresses in the form like
123 main street, newtown, OK, 12345
Add a new field to the table, let's call it location, that is of type float32x2, and with the Set Field values box checked. In the Expression tab enter
You're telling Radian to populate the location field with the results of the GeocodeAddress function using the Google geocoder applied to the contents of the address field. That function (as you can see from the command window listing) returns a value x 2 , that is, two numbers. That's why we made the location field type float32x2.
Press the add field button and you get a column that provides geocoding for the addresses.
If you want to do this sort of thing as a query , in the command window you can enter SQL like
SELECT GeocodeAddress([GoogleG],[address]) FROM [adds];
The google geocoder, by the way, is a huge deal. It does reverse geocoding. The opencage geocoder uses OSM. Others supported by Radian might require an API key (paid). But the choices are much better and the functionality using things like reverse geocoding will be expanded.