Matchcode International (boreas) Changes
(formally known as Matchcode 6)
Release Y11M11
Matchcode International (boreas) Engine Version 6.3.25
-
AU, CA, NZ, US: Fixed missing space with ampersand characters.
(Bug #541)
E.g. "1067, 10 & 11E RANG, SAINTE-CLOTILDE-DE-HORTON, CS, 0A1H0J"
would return "1067 10 and11e Rang,Sainte-Clotilde-De-Horton QC J0a 1h0".
-
CA: Number in square bracket range not displayed.
(Bug #1093)
E.g. Cross match "2 QUEEN STREET,LOL 1P0,ELMVALE" then select the first ambiguity.
-
CA: Fixed Matchcode Canada does not support UTF-8 accented characters as input.
(Bug #1154)
E.g. Cross match "805 rue Sherbrooke O St W,Montréal,QC,H3A
2K6" should return an exact match.
-
AU, CA, NZ, US, UK: Fix for when loading multiple RCDB files.
(Bug #1236)
-
AU, CA, NZ, US, UK: Updated to also read RCDB files with missing null terminators.
(Bug #1275)
-
US: Fixed an issue where the "change case" formatting
option did not work (Bug #1322)
E.g. A request for CITY(CA=2) will now return title
case output.
-
CA, US: The
VANITYOVERFLOW field now supports
"change case" formatting options.
Matchcode International (boreas) Server/Module Version 1.6.28
(formally known as Matchcode 6)
- Linked with Matchcode 6.3.25.
- Under FieldInfo, output only fields should not have more than zero on "Max Input Length".
Release Y11M08
Matchcode International (boreas) Engine Version 6.3.24
-
CA, US: Fixed a crash in USA and Canada code.
(Bug #1278)
-
US: Fixed an issue where the Matchcode server would have a memory
usage problem, if a corrupted US database was used.
(Bug #1260)
-
AU: Fixed an issue where the ISON code for Australia was not 3 digits
(outputting '36' instead of '036'). (Bug #1242)
-
US: Fixed an issue where the ambiguity list after a select then a
focus was different to the ambiguity list of the original select.
(Bug #1138)
-
NZ: Fixed a potential crash. (Bug #1276)
E.g. Crossmatch on "DELL FINANCIAL SERVICES (NZ),LOCKED BAG
62254,MT WELLINGTON,AUCKLAND NZ,,,," could cause a crash.
-
NZ: Fixed a potential crash. (Bug #1279)
E.g. Crossmatch on "LEVEL 4, 195 KHYBER PASS ROAD, NEW
MARKET" could cause a crash.
-
AU, CA, NZ, US, UK: Changed click counting to use new methods.
-
AU, CA, NZ, US, UK: Performance improvements.
-
CA, US: Work in progress to improve handling of vanity element
(unmatched input elements).
-
AU, CA, NZ, US: Fixed a crash that could occur when running
Matchcode Batch Processor and the latest version of the Matchcode
server. (Bug #1282)
Matchcode International (boreas) Server/Module Version 1.6.27
(formally known as Matchcode 6)
- Linked with Matchcode 6.3.24.
Release Y11M05
Matchcode International (boreas) Engine Version 6.3.23
-
US: Fixed an issue where zip codes were matched as building
numbers. (Bug #895, #1049)
E.g. Crossmatch on "133 Peachtree St NE,Atlanta, GA,
30303-1801" used to return an ambiguity list. It now
returns an exact match.
-
US: Fixed an issue where we failed to match a PO BOX. (Bug
#1104)
E.g. Crossmatch on PO Box 27066, Naval Air Station Jrb,
TX, 76127-0066 used to match to "Naval Air
Station".
-
US: Fixed a crash. (Bug #1113)
E.g. Crossmatch on "*,,,,Boston-South Shore,,," used
to cause a crash.
-
US: Fixed an issue where Cross Matching "bush st san francisco"
was returning unexpected ambiguities. (Bug #1119)
E.g. Crossmatch on "bush st san francisco" used to
return an ambiguity list with entries like "ASH ST". Now you get
an ambiguity of the numbers on Bush St.
-
US: Fixed an issue where we failed to match the suite
number. (Bug #1165)
E.g. Crossmatch on 520 E Cooper Ave Ste
23,Aspen,CO,81611-3801 failed to match the suite number.
-
US: Fixed an issue where we failed to match the suite
number. (Bug #1166)
E.g. Crossmatch on 275 Grove St Ste
3-300,Auburndale,MA,02466-2274 failed to match the suite
number.
-
US: Fixed an issue where we failed to match the intended address.
(Bug #1167)
E.g. Crossmatch on 5555 Ferguson Dr Ste
120-15,Commerce,CA,90022-5152 failed to match the
intended address.
-
US: Fixed an issue with the county not being used in the search
when it came after the city in the input address. Also stopped
the county being used if the county was before the city in the
input address. (Bug #1172)
-
AU, CA, NZ, US, UK: Fixed an issue affecting
the
LISTMODE option
of mcdparam.ini. (Bug #1212)
E.g. Setting ListMode=4 did not result in a
combined list.
-
AU, CA, NZ, US, UK: Fixed an issue where a select using combined
list mode could produce incorrect results. (Bug #1213)
E.g. Crossmatch on Hagey Blvd,Waterloo, Ontario
followed by a select of LISTITEM=0 used to return
"ONTARIO".
-
Fix to add
LISTDELIMITER
and LISTLINEDELIMITER and the short forms of the
names i.e. LDE and LLD. (Bug
#1214)
E.g. ADDR,AMBIGLIST(LISTFORMAT=C,LISTDELIMITER=E,LISTLINEDELIMITER=N)
FROM XMATCH WHERE ADDR=" TELECOMMS & TRADE POLICY,300
SLATES 58,K1A 0C8,OTTAWA"
-
Cross Match with Combined List Mode causes a crash. (Bug
#1219)
E.g. ADDR,AMBIGLIST(LF=C) FROM XMATCH WHERE
ADDR="High st, Tampa" Sometimes caused a crash.
-
AU, CA, NZ, US, UK: Fixed an issue where a focus on a new server
could cause a crash. (Bug #1220)
E.g. Focus on LISTTYPE="11" with no
previous search would crash a server that had just started.
-
Fixed setting
MAX before START causes an
incorrect number of items in the ambiguity list. (Bug
#1224)
E.g. ADDR,AMBIGLIST(LISTFORMAT=C,MAX=2,START=2) FROM
XMATCH WHERE ADDR=" STATION ROAD, WELLINGTON
"
This used to return only one item for the
ambiguity list.
-
Fixed
LISTFORMAT only worked in upper case. (Bug
#1226)
E.g. ADDR,AMBIGLIST(ListFormat=Multiple) FROM XMATCH WHERE
ADDR="GUTHEGA CLOSE,WOODCROFT,NSW"
This used to fail to set the list format as it needed all
settings in upper case. It is now case insensitive.
Matchcode International (boreas) Server/Module Version 1.6.24
- Linked with Matchcode 6.3.23.
- Added support for combined list mode (
LF=C).
- Fixed a crash caused by a memory leak in version 1.6.21 when used with a Date Restricted License..
Release Y11M02
Matchcode International (boreas) Engine Version 6.3.22
- CA: FieldStatus not set correctly.
(Bug #1063)
- CA: FieldStatus not set correctly for areaing elements.
(Bug #1064)
-
AU, CA, NZ, US: Trying to start ambiglist at the end causes a crash.
(Bug #1100)
i.e. Selecting with ambiglist(start=2010) if 2010 is the last element in the ambiguity list.
-
CA: Fixed an issue where
OUTPUTSTATUS was set to the
wrong value. (Bug #1053)
E.g. Crossmatch on "1780 ROSS ROAD,V7X 1L7,,,,"
will now return OUTPUTSTATUS=C.
- CA: Conflict between RESCODE=Hit and MATCHLVL=No Hit.
(Bug #1052)
E.g. XMATCH on "RTE SAINT-JEAN,988,G0S 2W0,ST-LAMBERT-DE-L?ëVIS (QC)"
will give a RESCODE of 1 (hit) and a MATCHLVL of 0 (no hit).
- CA: MATCHLVL indicates matched to street when there is an ambiguity on street or below.
(Bug #1059)
E.g. XMATCH on "RANG 4E E,999,G0R 3V0,SAINT-N?ëR?ëE (QC)"
will give a MATCHLVL of 2 even though it has not matched all the way to street.
- QBROWSE and SEARCH return incorrect RESCODE.
(Bug #479)
E.g. QBROWSE on "1600 pennsylvania ave,dc"
will give a RESCODE of 1 even though it has not matched to anything.
- Ambig list returned even though MATCHLVL=3.
(Bug #1028)
E.g. XMATCH on "PIPER JAFFRAY,California Street, San Francisco, CA, 94104"
- MATCHLVL=1 but there are no address elements.
(Bug #1099)
E.g. XMATCH on "14TH FL,1 FIRST CANADIAN PL,M5X 1W3,TORONTO"
- Make Rural Route match to Street not premise for MATCHLVL.
(Bug #1101)
E.g. XMATCH on "RR # 2, K0A 1L0, CARP," gives a MATCHLVL value of 3 (Premise) for a match to Rural Route.
We want MATCHLVL to give a value of 2 when this happens.
- US: Settings in mcdparam.ini were ignored.
(Bug #1068)
Setting MaxTowns will now work
Matchcode International (boreas) Server/Module Version 1.6.21
- Linked with Matchcode 6.3.22.
Release Y10M11
Matchcode International (boreas) Engine Version 6.3.21
- US: Matchcode not matching directional words such as WEST, NORTH
to abbreviations W, N.
For example:
978 WEST END AVE 8A,10025,NEW YORK,UNITED STATES OF AMERICA will now match to:
978 W END AVE,10025,NEW YORK,UNITED STATES OF AMERICA
(Bug #856).
- ALL: Allow
FIXED and DOUBLEQUOTE to be
set from waf.ini (Bug #995).
- AU, CA, NZ, US: Add LN option to Matchcode 6 address
formatting. (Bug #996)
E.g. Search on "4 CHURCH ST,TORONTO ON M5E1V1,M5E1V1"
requesting ADDR(LINECNT=5,LN=0) returns only the
first line of ADDR.
- AU: Fixed an issue where setting
LOCALITY
formatting options could override POSTTOWN
settings. (Bug #997)
E.g. Crossmatch on "3 church st, perth"
requesting ADDR(LC=8,FO=Y,TWN=FO:5,LOC=FO:3) will
now use POSTTOWN options for placing the town.
-
AU, CA, NZ: Added
POBOX, LOTNO,
and DEPT as element names for formatting
options. (Bug #998)
-
AU, CA, NZ, US: Set post box, floor, unit, flat and lot number
formatting options from subbuilding and building number settings
in waf.ini. (Bug #999)
-
CA: Fixed an issue where
MATCHLVL would always be set
to zero. (Bug #1012)
E.g. Crossmatch on "14 concourse gate,nepean k2e 7s6"
will now return MATCHLVL=3.
-
CA: Fixed an issue where
MATCHLVL set to wrong value. (Bug #1050)
E.g. Crossmatch on "main street,toronto on m4c4x2"
will now return MATCHLVL=2.
Matchcode International (boreas) Server Version 1.6.20
- Linked with Matchcode 6.3.21.2
Release Y10M08
Matchcode International (boreas) Engine Version 6.3.20
- AU, CA, NZ, US: Implemented full Address Formatting (WAF) options
Release Y10M05
Matchcode International (boreas) Engine Version 6.3.19
- UK: Fixed an issue where the setting of
AKMATCHTOP
could affect which addresses are returned. (Bug #835,
#840)
E.g. Crossmatch on "10 AUCHENKILNS HOLDINGS, CONDORRAT,
CUMBERNAULD" with AKMATCHTOP = 0 will now match to "10
Auchenkilns Holdings,Chapelton
Road,Condorrat,Cumbernauld,GLASGOW,Lanarkshire,G67 4HA1A" instead
of "31, AUCHENKILN HOLDINGS, CUMBERNAULD, GLASGOW, LANARKSHIRE,
G689AU".
- UK: Preliminary work to increase the character limit for address
elements. (Bug #754)
Matchcode 6 Server Version 1.6.18
- Linked with Matchcode 6.3.19
Release Y10M02
Matchcode International (boreas) Engine Version 6.3.18
- UK: Improved cross matching when addresses have a building with a
similar name to the street. (Bug #658)
E.g. Crossmatch on "2 Well Hill Cottages, Well Hill, Finstock,
CHIPPING NORTON, Oxfordshire, OX7 3BU" will now match to "2 WELL
HILL COTTAGES" instead of building "2" on the street "WELL
HILL".
Matchcode 6 Server Version 1.6.17
- Linked with Matchcode 6.3.18
Release Y09M11
Matchcode International (boreas) Engine Version 6.3.17
- AU, CA, NZ, UK, US: Add a feature to check for corrupt datafiles.
E.g. The log file may now contain messages describing the state
of datafiles:
Validation successful:
Tue Nov 03 15:05:14 2009,Info,DSG_Check(),"File sanity
check successful."
Validation failed:
Tue Nov 03 15:05:14 2009,HighLevel,DSG_Check(),"Datafile
'C:\CAPSCAN\AUSDATA\ausmatch.adb' does not have a valid
signature sequence! It may be corrupt or
incomplete."
Signature check skipped:
Tue Nov 03 15:05:14 2009,Info,DSG_SmartCheck(),"Signature
check skipped."
- CA, NZ, US: Refactoring of combined list mode code.
- UK: Fixed a potential crash.
Release Y09M08
Matchcode International (boreas) Engine Version 6.3.16
- NZ, UK, US: Fixed an issue where large ambiguity lists were
returned as normal lists instead of combined lists. The system
will now return no list when the ambiguity list is too large.
E.g. Quick browse on "Kent" used to return normal lists in
combined list mode.
- UK: Fixed porting issues on big endian machines
Release Y09M05
Matchcode International (boreas) Engine Version 6.3.15
- UK: Matchcode 5 changes from previous releases ported to Matchcode
6 UK
- NZ, UK, US: Implement combined list mode
- AU, CA, LPG, NG, NZ, UK, US: Fix buffer overflow
- US: Fixed an issue where a matched address could contain a
range. (Bug #287)
E.g. Crossmatch on "CITY CLERK, 225 Market St, SUNBURY,
NORTHUMBERLAND" used to return "STE [6,...,6]" as the value for
SECONDARY.
- US: Change
FIELDSTATUS to support
organisation. (Bug #525)
E.g. Crossmatch on "apple, 1 infinite loop, CA 95014
408.996" now returns "2" in the organisation position
of FIELDSTATUS.
- CA: Fixed a missing space in the
STREET
field. (Bug #541)
E.g. Crossmatch on "1067, 10 & 11E RANG,
SAINTE-CLOTILDE-DE-HORTON, CS, 0A1H0J" used to return "10
AND11E RANG" but now returns "10 AND 11E RANG".
Release Y09M02
Matchcode International (boreas) Engine Version 6.3.14
- Linked to new version of internal libraries util1.
Release Y08M11
Matchcode International (boreas) Engine Version 6.3.13
- HP-UX porting fixes. (Bug #601)
E.g. Crossmatch on "1600 pennsylvania ave,NW,washington dc"
using Matchcode US now results in a match.
E.g. Crossmatch on "George Street,NSW,2000,Sydney" using
Matchcode AU now returns an ambiguity list of building numbers
containing 486 entries.
E.g. Crossmatch on "420 EDGEMONT BAY NW,,,CALGARY,AB,T3A2K6"
using Matchcode CA now returns an MSCORE of 100.
- US: Fix a misaligned read on SPARC Solaris. (Bug #489)
E.g. Crossmatch on "1 DELL WAY,78682-0001,ROUND ROCK," caused a
crash.
- US: Fix an endian problem on SPARC Solaris. (Bug #609)
E.g. Crossmatch on "111 SW COLUMBIA ST STE
1080,97201-5842,PORTLAND,,,,," never returned.
- CA: Remove debug message for missing province accents (Changed
logic so the debug message will not apear under these
conditions) (Bug #550)
E.g. 6521, DESMARTEAU, MONTREAL, QC, H1K4P3, caused debug
message.
- CA: Fix a search that failed when the postcode contained a
space. (Bug #467)
E.g. Quick browse on "J8A 3B2" failed.
Release Y08M08
Matchcode International (boreas) Engine Version 6.3.12
- CA: Fixed the file description on the Windows DLL.
E.g. The file description used to read "Matchcode 6
AU"
Release Y08M05
Matchcode International (boreas) Engine Version 6.3.11
- CA: Implemented support for accented characters.
To use accented characters edit the Canadian mcdparam.ini. Add
"accents=yes" to the OUTPUT section.
E.g. 506, SAINT-FRANCOIS, SHERBROOKE, QC, J1G2B9
Release Y08M02
Matchcode International (boreas) Engine Version 6.3.10
- UK: Implemented a fix to stop a crash which occurred during cross matching
E.g. HALL DRIVE, LINCOLN, LN1 2RD
Release Y07M11
Matchcode International (boreas) Engine Version 6.3.9
- US: Fix to utilise the full forms of directional words
(N=>NORTH,S=>SOUTH etc) now added to the database. (Bug
#470)
E.g. 6921 WEST ROBIN LANE,GLENDALE AZ 85310
Release Y07M08
Matchcode International (boreas) Engine Version 6.3.8
- Porting fixes for 64-bit Big-endian platforms.
- AU, CA, NZ, UK, US:
Add
FIELDSTATUS, OUTPUTSTATUS,
and RESCODE output fields.
- CA: Added support for a '
SERP' value of the
'SOURCE' formatting option. Possible values include:
- '
SERP' - (default) the text of the element is
taken from the address database or the input address.
- '
MATCHED' - the text of the element is taken
from the address database.
- '
INPUT' - the text of the element is taken
from the input address.
- UK: Fixed a bug in cross matching.
- UK: Added support for large databases.
/font>
Matchcode International (boreas) Engine Version 6.3.7
- CA:Added support for a '
SOURCE' formatting option for
address element output fields which can be either:
is taken from the address database.
'INPUT' - the text of the element is taken from
the input address.
Note: SOURCE=INPUT, or SRC=I,
allows for the output of "vanity" elements from the input
address that were not found on the address database. This is
particularly useful for UNIT.
E.g. if the input address is "1919 17 Ave SW Suite 40,
CALGARY AB T2T 0E9", where Suite 40 does not appear on the
Canada Post database, UNIT will return an empty
string, but UNIT(SRC=I) will return "Suite
40".
CA: Extended the range of checking for "vanity" elements to cover
the entire address. This fixes the problem where a specified unit
not found on the database is handled correctly when the
municipality is present and not handled correctly when the
municipality is missing.
E.g.
With the input "1919 17 Ave SW Suite 40,CALGARY AB T2T 0E9"
the unit "Suite 40" was handled correctly.
With the input "1919 17 Ave SW Suite 40,AB T2T 0E9" the unit
"Suite 40" was lost.
Both cases are now handled correctly.
Release Y07M05
Matchcode International (boreas) Engine Version 6.3.6.1
- US: Fixed a bug that cleared address fields after running a quick
browse followed by a cross match and select.
Matchcode International (boreas) Engine Version 6.3.6
- UK: Fixed a bug where select queries returned blank results.
Release Y07M05 Interim
Matchcode International (boreas) Engine Version 6.3.5
- US: Zipcode lookup now works without the addon.
- US: Fixed I/O error that could occur when a zipcode overrode a town match.
Release Y07M02
Matchcode International (boreas) Engine Version 6.3.4
- NZ: New PAF format changes.
- NZ: Fix selecting of 'Without' areaing elements.
Release Y06M11
Matchcode International (boreas) Engine Version 6.3.2
- Stop Cross Match and Quick Browse trashing the input query.
- Save and Restore ListItem and ListType when processing SearchStatus
- NZ: The use of Greater Metropolitan Areas to enhance CIC scoring.
Although Papakura is considered a Town on the PAF,
users often input Papakura, Auckland. This change
will give Papakura a higher score so it gets chosen
over Auckland as the Town.
Matchcode International (boreas) Engine Version 6.3.1
- AU: AMAS Changes
- AU: Bug fix to prevent large incorrect building numbers
appearing in the ambiguity list.
Matchcode International (boreas) Engine Version 6.3.0
- NZ: New Zealand can find a PO BOX/PRIVATE BAG where
there is no Lobby Name because it is the same (or
similar) to the Town Name.
- NZ: Output format changed to meet specification.
- NZ: Added address type flag
- NZ: Added base match flag
Release Y06M08
Matchcode International (boreas) Engine Version 6.2.9
- AU: Fixed a problem in Matchcode Australia where street_type and
street_name were not being set.
Matchcode International (boreas) Engine Version 6.2.8
- Fixed some problems with reading and writing to invalid addresses.
Matchcode International (boreas) Engine Version 6.2.7
- Address Database, Names and RCDB logging implemented.
- UK: fuzzy postcoding can now be disabled by FUZZYPC parameter.
- UK: fuzzy postcoding is only called for invalid postcodes.
Release Y06M05
Matchcode International (boreas) Engine Version 6.2.6
- UK: fuzzy postcode matching bug fixes
Release Y06M02
Matchcode International (boreas) Engine Version 6.2.5
- NZ: first release of Matchcode New Zealand
Release Y05M11
Matchcode International (boreas) Engine Version 6.2.4
- Build errors resolved.
- /mcd6/adb/ecdbXX/common.c now /mcd6/adb/ecdbXX/commonae.c to avoid caplock1\capsec\common.c debug link conflict
Release Y05M11AU, AMAS_2006_ATF
Matchcode International (boreas) Engine Version 6.2.3
- AU: AMAS 2006 cycle
Matchcode International (boreas) Engine Version 6.2.2
- US: Fixed issue with MatchLvl and PCChgLvl having incorrect values.
- US: Fixed issue where incorrect zipcodes on input were given too much importance and broke matching.
Matchcode International (boreas) Engine Version 6.2.1
- NZ: DPID RCDB access fixed for NZ (beta shipped to PinPoint).
Matchcode International (boreas) Engine Version 6.2.0
- IE: Irish & name changes.
- Updated copyright dates to reflect current year.
Matchcode International (boreas) Engine Version 6.1.28
- Fixes to RCDB2 which wasn't initialising DCB.SearchMode in RCDB_GetActualDataItem.
Matchcode International (boreas) Engine Version 6.1.27
- Threadsafe patches for usropt
- CA & AU: Increased maximum MaxTowns.
Matchcode International (boreas) Engine Version 6.1.26
- US: Fixed a bug in Cross Matching.
- Added version strings used by mc5shell DLL and Matchcode Apps.
Release AUS20044
Matchcode International (boreas) Engine Version 6.1.25
- US: Change PCLVL from '4' to '5' if DP code is set.
- AU: Add additional unmatched data to output address field (i.e. ADDR).
Release AUS20043, Y04M02
Matchcode International (boreas) Engine Version 6.1.24
- CA: Canada passed SERP test.
Release AUS20040, AU2003
Matchcode International (boreas) Engine Version 6.1.23
- CA: First working version of Matchcode Canada.
Matchcode International (boreas) Engine Version 6.1.22
- Bug fix for blank lines and increased MaxTowns to 90.
Matchcode International (boreas) Engine Version 6.1.21
- Added version info header file.