Innosoft GeoCoder 2.2 (Innosoft.CRM.Core 1.9.x - 14.07.2022)

Bug in GeoCoder 2.0 version !!!

New functions have been added:

  • When starting the (1,2,3 or 4 - mode) it is checked whether GeoCoder has already been started on this system. (This will create a record in the VERSIONEN table with the G2 flag).

  • If there is no entry in the VERSIONS table yet, the geocoordinate checking process is started automatically.

    • GEODATA will be deleted,

    • VKUNZUS/RESSLIST and MAPARK analyze whether the distance between land center and stored coordinates is not greater than the distance between land center and the rotated coordinates. Rotated coordinates have several thousand kilometers in difference and can thus be detected and fixed.

  • Coordinate check can be started manually: Option 7

News in 2.2 version

  1. Google-GeocodeAPI" has been added as a second provider. This allows both LocationIQ and Google to be configured in the system. If both are preconfigured for GeoCoder, Google will be used as a "fallback" provider. (If LocationIQ does not find an address => try with Google). Settings in the FIELDINHALTM.

    Group

    Counter

    Description

    6003

    2

    Google Geocode Api Key for GeoCoder

    6003

    3

    LocationIQ Api Key

  2. Table GEODATA2 is used instead of GEODATA

  3. ERRORCODECOUNT has been replaced by NextRequestUtc. Depending on the error type, GeoCoder will determine in time the next encoding attempts (e.g. day/month limits, etc.)

  4. The LANDKF code is always used for coding.

  5. Google coordinates are automatically deleted from GEODATA2, MAPARK/VKUNZUS and RESSLIST after 30 days and then re-coded.

  6. FSM-GUI

    1. Manual coordinates for addresses and resources

    2. Manual coordinates or addresses for machines (only Google API is used here).

    3. API Keys Configuration from "General Settings"

  1. Unzip the contents of the release archive to any folder.

  2. Place an innoconfig.xml in this folder. Read here how to create such a file.

  3. Place the key provided by Innosoft in the database (Tabelle FeldinhaltM, Gruppe 6003, Zähler 3).

  4. Set up a scheduled task that will run the tool on a regular basis. The call must follow the following pattern:
    GeoCoder.exe <INNOSOFTBENUTZERNAME> <PASSWORT> <OBJECTID> [FILENAME].
    Use the objectID to select which objects to geocode. Choose one of the following values

    • Addresses

    • Resources

    • Machines

    • All mentioned

    • Special mode for coordinates output to CSV file. Coordinates from LocationIQ and LocationB are saved to allow further analysis.

    • Coordinate checking routine in "read only" mode.

    • Force coordinates check routine to start.

  5. Configure the settings in the FELDINHALT

    Gruppe

    Zähler

    Value

    Beschreibung

    7031

    3

    int

    LocationIQ => Distance between several returned coordinates must not be greater than value (km). (default = 3)

    7031

    5

    0/1

    LocationIQ => ZIP code is ignored. "q" query is preselected (default = 0).

  6. The requests are sent via HTTPS to the URL eu1.locationiq.com. The URL may need to be shared in the firewall and access is via port 443.

  7. HttpClient can now use proxy settings from *.config file.

    Proxy settings
    <configuration>
    <appSettings>
    <add key="Proxy.UseProxy" value="true"/>
    <add key="Proxy.Server" value="proxy-server"/>
     
    <add key="Proxy.Port" value="proxy-port"/>
     
    <add key="Proxy.UseDefaultCredentials" value="true"/>
    <add key="Proxy.User" value=""/>
    <add key="Proxy.Password" value=""/>
     
    <add key="Proxy.UserAgent" value="Innosoft GeoCode/2.0 (Windows NT 10.0; Win64; x64)"/>
    </appSettings>
    </configuration>