2015Q1.0 Resolved Cases
2015Q1.0 Resolved Cases
Local API Updates
- Case 00004881: Latest loqate jar is giving UnsatisfiedLinkError
- Case 00004826: US Addresses getting cleansed without state
- Case 00004816: Engine crash with addresses from Peru
- Case 00004807: Complete Address Change
- Case 00004796: lqtDemo.exe “To Clipboard” bug
- Case 00004766: Engine crash with Australian address
- Case 00004726: CASS return multiple responses
- Case 00004712: Multi-threads crash issue
- Case 00004711: No DPID returned when using AMAS
- Case 00004690: Issue with Autocomplete stage when provide country and postal code only
- Case 00004689: Loqate issue using Query as process option with new binaries.
- Case 00004674: Address in Philippines does not work anymore – Mariano Ponce St.
- Case 00004636: Issue with Netherland address.
- Case 00004634: Loqate Autocomplete power search issue. – Losing house numbers in Croatia
- Case 00004632: Verify / Search discrepancies – addresses not verifying in Verify but does verify in Search
- Case 00004604: Abbreviation issues related to Powersearch
- Case 00004597: Loqate crash on Address “?” and Country “USA”
- Case 00004580: Query on AVC
- Case 00004566: Major German Data issue
- Case 00004545: Crash running 2014Q4 through initial multithreading test
- Case 00004542: Loqate API crash
- Case 00004492: Query Around An Australian Address – AMAS library changes Street Postfix
- Case 00004477: Crash during multithreaded operation
- Case 00004473: Crash on address
- Case 00004429: Autocomplete results with Loqate Query Interface
- Case 00004412: Address Queries – Homebush Bay parses to DependentLocality causing bad matching
- Case 00004404: German Accents – problematic Search output from inputs without accents
- Case 00004361: Greece Address – CITY IS GETTING CHANGED FROM ENGLISH TO LOCAL LANGUAGE
- Case 00003638: Italian Province Casing is Title case rather than Upper case and inconsistent at that
- Case 00003127: Alpha in Alphanumeric premise designations should be uppercased
- Case 00003003: Italian city incorrectly changed
- Case 00002397: House number / postcode use case
- Case 00002269: Zip code is changed despite invalid street
Cloud API Updates
- Case 00004904: Single process request error
- Case 00004883: Loqate processlist issue for REST request
- Case 00004742: Cloud performance when going from powersearch to old “register”
- Case 00004558: Cloud transaction
- Case 00004484: Wrong counts for “by country” in cloud reports
- Case 00004479: “ECM” not recognized as PostBoxType
- Case 00002713: Loqate server response have Verified status, but no DeliveryAddress1
Country Updates
- Case 00004852: Irish thoroughfare with ‘Estate’ mistaken for building
- Case 00004811: Different ZIP code in Address and PostalCode fields
- Case 00004795: ThoroughfareName Blank
- Case 00004710: Incorrect UK Building Name
- Case 00004673: Ordinal streets are not recognized if suffix st/nd/rd/th is missing
- Case 00004669: US address issue
- Case 00004596: Matching issue in Europe
- Case 00004586: The result Latitude and Longitude are incorrect
- Case 00004562: South Korea Address Formatting
- Case 00004551: Brazil data feedback
- Case 00004543: Australian city not verified
- Case 00004537: Loqate does not correct Thoroughfare input
- Case 00004521: Zip-plus-four issue
- Case 00004451: French output elements stripped of special characters
- Case 00003484: SupressMatchFields option implemented
- Case 00003479: Addresses in Spanish not validating
- Case 00003435: AVC incorrect
- Case 00003371: P4 geocode in wrong place
- Case 00003208: Netherlands matching
- Case 00002977: Mishandling abbreviation ZAC even though it’s identified by Lexicon
- Case 00002966: Abbreviation (Lv) not recognized in Australian address
- Case 00002871: Missing address in reference data – Australia address is missing
- Case 00002772: There is no “Intontry” road in Bellary Karnataka
- Case 00002662: Formatted address for Taiwan is in English rather than Chinese format
- Case 00002042: Incorrect ambiguities for France