Location Publishing

Wrap-Up of TIF Databases

1) Document Control
DOCUMENT CONTROL
Version Date Author Approved Status Circulation Remark
By
2.1 26AUG08 JT BN/HD Final All via E-PRIDE TIF17 plus User
Feedback Updates
HISTORY
1.0 14NOV05 KG KG, DJ, Final All via WIKI
PLT
1.1 02DEC05 KG KG Final All via WIKI Included copyright
and on-line doc
comment in footer.
1.2 09DEC05 KG KG Final All via WIKI Prelim audit changes:
LP in header and
measures.
1.3 02FEB06 KG KG Final All via WIKI Copyright 2006
1.4 28FEB06 CD KG Draft KG, TLT Draft of document
1.5 23MAR06 KG CD, PLT Final All via E-PRIDE Review retention &
disposal in records
table from cert audit.
1.6 08AUG06 GR KG Final All via E-PRIDE Update to Tif 15
1.7 18JAN07 MW GR Final All via E-PRIDE Consistency
Improvements
1.8 17SEPT07 GR, KG Final All via E-PRIDE Improvements added
MW for TMC, Team
Leader signoff and
ADB checks
1.9 08NOV07 MW GR Final All via E-PRIDE Improvements added
for housenumbers,
TMC and delivery
format
2.0 14FEB08 MW GR Final All via E-PRIDE TIF17 plus User
Feedback Updates

© Copyright Sensis Pty. Ltd. 2006.

Note: The contents of this publication are subject to change. For the most recent version always refer to the on-line
documentation.

Wrap_Up_v2-1_W.doc 1/14
2) References
Reference Type Title
Related Process Finalise Data
Work Product Conversion data
Tool Toolbox, TA Mapper, Fealing Road, RemHnr, List MPI, Log Interpreter,
TIF2Asc, Dupid check, X01cdbi (Consistency Check Tools ), Corrwork
(Consistency Fix Tools).
Support Material <Specs, TADM_TM, TADM_PM etc>

© Copyright Sensis Pty. Ltd. 2006.

Note: The contents of this publication are subject to change. For the most recent version always refer to the on-line
documentation.

Wrap_Up_v2-1_W.doc 2/14
3) Purpose
To wrap-up TIF databases for release

4) Scope
This process is completed by GIS Officers in the Production team.

5) Tasks

A. Preparation
 Get signoff from a team leader that all INCA checks (including CONCAD preset) have been run
and completed. Check Release Checklist on “P:\PLM\RELEASE\Aussie16_QualityReports\
COUNTRY\Release Checklist”
 Check if Pre Wrapup Tool has been run on the dataset. Without this sign off wrap-up cannot be
completed. Check Release Checklist on “P:\PLM\RELEASE\Aussie16_QualityReports\
COUNTRY\Release Checklist”
 Make sure the database is FULLY CONSISTENT. No errors are found after consistency is run
over the particular dataset; e.g (chkcntry nsw 01 /all /tag). Warnings need to be fixed also. Make
sure snips are checked when running consistency over the country. Also check cross-country
seaming. Note: consistency runs quicker locally.
 HINT: there are sometimes hundreds or thousands of street used counter errors which would take
an unbelievably long amount of time to fix- so you can use the batch file countpy for this Located
on M:\AUS\Workspac\ count.py.
 All the latest programs and tools need to be installed locally as all checks and processes will be run
on one computer. Note: Make sure before running any tools that the tool possesses the country’s
DBI’s and that they are set locally.
 Programs you will need on your computer are listed above in point 2) Tools.
 Make sure the local computer has at least 7GB of hard disk space free.

B. Database Lock-Down
 Open TOOLBOX and “LOCK” the selected database (on M:\AUS\ or P:\NZL) by placing
“WRAPUP” in the production column.
 Copy the locked databases to a local drive and place it within D:\Ta_Data
 Set DBI’s to point at this location.
 Reffex the dataset using Toolbox to “Create Reference Files with ADB Connection” to the new
locally copied databases as working will now be done locally.

C. Road Fealings
 Take Road Fealings dump of Country, PartitionID, EdgeId, Length (Road Fields), FRC-A, FRC-B,
FOW, Net-2 Class.
 IN MORE DETAIL: You need to have countries DBI’s pasted in C:\Program Files\Tele Atlas\
Fealing Road 17.00 to be able to select all the partitions within the dataset. You deselect all types
in EatFields & NameTypes. You only need ‘Country, PartitionID, EdgeID, Length, FRC-A, FRC-
B, FOW, NET2 Class from the RoadFields section. This table is dumped in C:\Program Files\Tele
Atlas\Fealing Road 17.00\Output under your specified name.
 Sort by length to see if any roads < 5m are present.
 There should not be any road edges < 5m at this stage as the process should have been performed
at some stage before wrap-up.
 If at this stage any short edges are found, use the edge ids of these edges generated by the Fealings
dump (steps A and B above) to manually fix them in TA Mapper. Then repeat steps A and B to
see if all short edges have been eliminated.

© Copyright Sensis Pty. Ltd. 2006.

Note: The contents of this publication are subject to change. For the most recent version always refer to the on-line
documentation.

Wrap_Up_v2-1_W.doc 3/14
 Repeat these steps until no short edges and Value “0” remain.
 Rerun consistency on affected partitions and solve any new errors generated. Go in C:\ X01cdbi
(Local Consistency Check Tools on C:\), Corrwork (Local Consistency Fix Tools on C:\)
 Also check attributions for FRC-A, FRC-B, FOW, Net-2 Class. They should not have the value
“0”, if they do then open the partition in TaMapper and fix it.

D. Removing Stars (*) From House Numbers

Note: stars (*) are generated by TA Mapper wherever an address range is split by a new node and it
must interpolate a new range. These stars must be removed prior to supplying the dataset to the
conversion team as they cause problems for their processes.

 Check DBIs are pointing at the local copy of the database.

 Open RemoveHnr program
 Open the “Partitions” ( 
) icon and select all the partitions within the database and then press
“Done”.
 In the “FRCCheck” browser tick all the FRC’s and make sure the ‘*’Check box is also ticked

Example

 Hit “Start Bang” (!) once completed.

 Close RemHnr.

© Copyright Sensis Pty. Ltd. 2006.

Note: The contents of this publication are subject to change. For the most recent version always refer to the on-line
documentation.

Wrap_Up_v2-1_W.doc 4/14
 To check if stars were deleted, an Access Database is created in the database D:\TA_DATA\
XXX_01\XXX_GADM\External called ‘RemovedInfo.mdb’. Inside this database it states if any
stars were deleted, and provides edge id’s where this has occurred (if it has).
 Note: At this stage there should not be any stars, however it is possible that some may have been
generated if short edges had to be fixed as a result of the Road Fealings dump. If this occurs, use
the edge id’s generated by the RemHnr tool to manually repair the address ranges which were
deleted by the tool in TA Mapper, utilizing the copy of the database still on network drive as a
reference (i.e. open this copy in TA Mapper as read-only to view how the address ranges were
before they were deleted). Repeat steps 1 – 7 until no stars are deleted.
 Re-run consistency on any partitions which were affected.

E. Query ADB to ensure “AdminCode = AdminCodeRW” and Check

CNT/CPT Status
 The ADB.mdb is found at D:\TA_DATA\XXX_GADM\Access. Make a copy of ADB.mdb in
your D:\ drive
 Open a new query window in ADB.mdb, (design view mode, and close SHOW TABLE browser)
select SQL option. (tool bar)
 Execute the following query
SELECT *
 FROM AdminArea
 WHERE AdminCode <> AdminCodeRW;

(can copy & paste this query to replace existing text):

If pasted, remove ampersand (?) if any from a front of the text, click on ‘start bang’ (!)

 If there are any records where AdminCode and AdminCodeRW are not the same then investigate
this in TA Mapper to see which of the two values is incorrect and amend in ADB.
 Repeat the above three (5) steps until the query generates no results.

 Execute the following Query for Checking CNT/CPT status (copy paste the below statement as
SQL query)
 SELECT LinkPartitionAdminArea.AdminID, Count(LinkPartitionAdminArea.AdminID) AS
CountOfAdminID
 FROM LinkPartitionAdminArea
 GROUP BY LinkPartitionAdminArea.AdminID
 HAVING (((Count(LinkPartitionAdminArea.AdminID))>1));

Run and save the query as Table “CNT_CPT”

 If the Admin ID exits more then once in CNT_CPT Table then create another query to find out the
Partition and the CNT/CPT Status of that partition.
 (copy paste the below statement as SQL query)

 SELECT CNT_CPT.AdminID, LinkPartitionAdminArea.PartitionID, Partition.PartitionCode,

Partition.PartitionName, Partition.[Coverage Profile Type], Partition.[Coverage Network
Type] FROM CNT_CPT INNER JOIN (Partition INNER JOIN LinkPartitionAdminArea ON
(Partition.Database = LinkPartitionAdminArea.Database) AND (Partition.PartitionID =
LinkPartitionAdminArea.PartitionID)) ON CNT_CPT.AdminID =
LinkPartitionAdminArea.AdminID;

Any AdminID that exit in two different partition should have the Same CNT and CPT status, If not
then check the Partition in TaMapper and make the changes “If repart is required then follow the repart
Instruction”

© Copyright Sensis Pty. Ltd. 2006.

Note: The contents of this publication are subject to change. For the most recent version always refer to the on-line
documentation.

Wrap_Up_v2-1_W.doc 5/14
PartitionI AdminID PartitionCode PartitionName Coverage Coverage
D Profile Type Network Type
5 61705375 SSC01000 SUNSHINE COAST EXT STNW
10 61705375 BRS11000 CABOOLTURE EXT STNW

F. Query ADB to ensure that 2 admin areas of the same order don’t
exist
 The ADB.mdb is found at D:\TA_DATA\XXX_GADM\Access.
 Open a new query window in ADB.mdb, (design view mode, and close SHOW TABLE browser)
select SQL option. (tool bar)
 Execute the following query:
 SELECT AdminArea.StandardName, Count(AdminArea.StandardName) AS
CountOfStandardName, AdminArea.Order
 FROM AdminArea
 GROUP BY AdminArea.StandardName, AdminArea.Order;
 Select the Countofstandardname column and hit Z-A. If there are any duplicate admin areas there
will be a count of more than 1. If there is a count of >1 for the same order, this is a problem and
should be fixed through checking the source data and fixing the situation accordingly. Eg. Make
the 2 admin areas one area. Check with Team Leaders before altering any data. It may be the
case that two admin areas with the same name and order need to exist. (check other sources; UBD
etc)
 Razorback in RNS is an example!
 Rerun consistency on any partitions that changes were made (affected.)

G. Query ADB to ensure SpeedUnitID value is either null or ‘1’

 The ADB.mdb is found at D:\TA_DATA\ACT_GADM\Access.
 Open the Admin table and scroll across to the SpeedUnitID column.
 Sort Ascending and Descending. The only values present should be either null (no value)
or 1.

© Copyright Sensis Pty. Ltd. 2006.

Note: The contents of this publication are subject to change. For the most recent version always refer to the on-line
documentation.

Wrap_Up_v2-1_W.doc 6/14
This needs to be checked for all Dataset.

H. Check TMC Country Code

 Check that the correct TMC country code is entered in the mdb located at M:\Aus
 \Ta_Data\<country>_01\<country>_GADM\ACCESS\TMC. Open the access database and look at
the TMC MetaInfo table.
 Official Country Code list for all states is as follows:

CC = Country Code, LTN = Location Table Number

Australia Location Table Numbering

AU CC LTN ECC
Aus. Capital Territory 1 53 F0
New South Wales 2 54 F0
Victoria 3 1 F0
Queensland 4 56 F0
South Australia 5 57 F0
Western Australia 6 58 F0
Tasmania 7 59 F0
Northern Territory 8 60 F0

 The MetaTypeId 3 is the country code and a MetaValue of 1 means ACT

 Supplier
Should be ATMCC for (ACT, SAX and WAX)
Should be Sensis for (MGM, NSW, QLD)

Rerun TMC Tools Located in C:\Corrwork (Consistency Fix Tools).

ProcessTMCPathSequence.exe
TMCFPRPathSequence.exe
TMCCorrect.exe
TMCCheck0318.exe
© Copyright Sensis Pty. Ltd. 2006.
Note: The contents of this publication are subject to change. For the most recent version always refer to the on-line
documentation.

Wrap_Up_v2-1_W.doc 7/14
Any error reported in these tools needs to be fixed in Tamapper, rerun the tools until the error log is
“0”.

H. TIF2Asci HNR Check

 Within TIF2Asc program folder place a DBI of the local database. Open TIF2Asc.exe program.
 Within the program interface select the HNR option. Click down the Access Key button. Go to the
“open folder” icon (), when the window opens select the local database’s DBI (one that was
just pasted in. Hit (go)icon and this will set off the dump process.
 In the TiF2Asc program folder go to the newly created database folder and navigate to the mdb
file. Open a new query and select the HNR table. Using design mode, select all (*) in the first
column, then leftfirsthnr in the second – and uncheck its ‘show’ box. In the criteria row, type the
following (or copy and paste):
 [hnr]![leftfirsthnr] Like "*[!0-9]*" Or [hnr]![leftlasthnr] Like "*[!0-9]*" Or [hnr]![rightfirsthnr]
Like "*[!0-9]*" Or [hnr]![rightlasthnr] Like "*[!0-9]*"
 This query gives you a list of all house numbers containing any characters other than numerals.
These characters must be removed. Use the table to correct any errors in TA Mapper and run
consistency on any partitions affected.

 Once the process has completed the databases logs are then copied to P:\PLM\RELEASE\
Aussie##_QualityReports\database\TIF2Asc. (This file path is explained in step J)

I. Checking Address Point Id’s

 A common error that has occurred in the past is Address points not having AddressPointId’s. So
we check this before they have to go through the time consuming conversion process.
 Tif2Asc dump of APT

© Copyright Sensis Pty. Ltd. 2006.

Note: The contents of this publication are subject to change. For the most recent version always refer to the on-line
documentation.

Wrap_Up_v2-1_W.doc 8/14
 Search through the Address Point Id’s (descending/ascending etc) to check that there are no
missing id’s. If there are, then you need to go into TaMapper and fix them. To give them Id’s you
can edit the address point to a Generic Anchor Point. Then change it back to the correct type it was
previously. This should give the address point an AddressPoint Id!
 You should re-dump to make sure you have fixed all address points, and run consistency on the
partitions you were in.
 Once the process has completed the databases logs are then copied to P:\PLM\RELEASE\
Aussie##_QualityReports\database\TIF2Asc. (This file path is explained in step J)

J. Archiving Unwanted Database Files

 We need to archive our unreleased files and clean error logs to P:\PLM\RELEASE\
Aussie##_QualityReports\database.
 Within this location the following folders need to be created: GADM_Archive, DTA_Archive,
GGEO_Archive, TIF2Asc and DupIdLogs.
 We need to cut and paste any folders which are not DTA, database_GADM , database_GGEO or
Extensions (eg. History, Updrep, Repart.tmp) into the specific country’s quality report; P:\PLM\
RELEASE\Aussie##_QualityReports\database. Therefore after we have done this, the country we
are in the process of wrapping up should contain these 4 mentioned folders as seen in picture
below.

© Copyright Sensis Pty. Ltd. 2006.

Note: The contents of this publication are subject to change. For the most recent version always refer to the on-line
documentation.

Wrap_Up_v2-1_W.doc 9/14
 In folders D:\Ta_Data\database_01\DTA\partition\log and D:\Ta_Data\database\glob\partition\
logs make sure that the only files present are IncaViol.mdb and logs.mdb. Archive the rest within
P:\PLM\RELEASE\Aussie##_QualityReports\database\Dta_Archive under appropriate folder
headings. See next step on how to do this quickly.

 Hint: Open the DTA folder. Click the “Search” button > All Files and Folders > More Advanced
Options . Type of File > Microsoft Access Database. Search and archive anything that isn’t
IncaViol or logs.

Example: If Hni.mdb was found within D:\Ta_data\mgm_01\01\03003400\logs it will be archived to P:\

PLM\RELEASE\Aussie12_QualityReports\mgm\Dta_Archive\01\03003400\logs.

 Database_GADM’s structure should be as shown below (after archiving). Any unwanted files will
need to be placed within R:\Aussie##_QualityReports\database\GADM_Archive. Commonly,

there are eat_old.ini, nsw_old.ini, nsw.ini.bak, External (folder) to be archived.

 The Access folder will be composed of four Access databases (Adb.mdb, Restrictions.mdb,
COT.mdb & IncaCheckRefdatabase.mdb) and a TMC folder containing TMC mdb’s for the
country and all adjoining countries, see example below.
 As before anything other than what was stated will be archived to Gadm_Archive and a copy of
the TMC folder will be archived as well.

© Copyright Sensis Pty. Ltd. 2006.

Note: The contents of this publication are subject to change. For the most recent version always refer to the on-line
documentation.

Wrap_Up_v2-1_W.doc 10/14
 Database_ggeo should only be composed of connect.database, connext.database, reffiles.acc,
reffiles.dta, refmulti.dta, refparts.dta. (Reffiles.acc may not be there, this is fine.)
 All others will be logged to P:\PLM\RELEASE\Aussie##_QualityReports\database\
GGEO_Archive.

K. Checking, Compacting & Repairing Access Databases

 Within Country_Gadm open ADB.mdb and navigate to the “Versioning” table. The Version
should correspond to the release (Tiff) number. If it does not, consult Team Leader – Production.
 Make sure ADB is not a replica. If it is, consult Team Leader – Production
 Still within Adb.mdb, navigate to the taskbar “Tools” – “Database Utilities” – “Compact
Database” and once that is completed navigate to “Tools” – “Database Utilities” – “Repair
Database”. This process needs to be done for all databases (.mdb) within the database_Gadm
folder.

L. Rebuild Dataset
 Street Files
 TOOLBOX - TOOLS – Street Utilities, SELECT STREET TOOL – Rebuild Street File
 Select Dbi, and check boxes 1, 2 and 3.
 REBUILD OPTIONS – List Street Files to ASCII and Remove all streets with Rejection Code
then STARTBANG!
 After this has run select the rebuild option – Create street file from previously created ASCII file
Note: Tool- no logs generated.
 TMC
 C:\CORR####> Run Processes;
 1)TMCPathEdgeNode.exe
 2) TMCPathSequence.exe
 3) FPRPathSequence.exe
 4) TMCCorrect.exe
 5)TMCcheck0318.exe (X01CDBI)
 Open the dataset folder within CORR#### and check the TMC logs. These will be the most recent
logs. There should be no errors or warnings. If there are error or warning logs these need to be
fixed. discuss with Team Leader
 Sortname
C:\CORR####> SORTNAME
Note: Tool- no logs generated.
 Sortpoc
C:\CORR####> SORTPOC
Note: Tool- no logs generated.
© Copyright Sensis Pty. Ltd. 2006.
Note: The contents of this publication are subject to change. For the most recent version always refer to the on-line
documentation.

Wrap_Up_v2-1_W.doc 11/14
Take local copy of database (as backup) & Rebuild Trees (Toolbox)
 Check all boxes including spatial tree and node tree. Select all partitions including global. Hit
Start-Bang. This can take over two hours depending on processing speed and database size.
 If problems occur (face), go to backup copy of dataset just taken and attempt to rebuild trees again.
 If errors occur again run consistency and solve errors.

M. Duplicate ID check
 Run the Duplicate Identifier Check; ‘dupid.exe’ found in C:\X01CDBI\. Make sure all features
types are selected at the bottom.
 Select Automatic Completion and Not Connected Streets and press green “play” button.

 Open C:\X01CDBI\country for any errors. Sort by “Date Modified”.

 Open all DupId logs. If errors solve with consistency tools then rerun Duplicate Identifier Check
and consistency for relevant partition. Check error logs until clean.
 Archive the logs in the DupIdLogs folder on P:\PLM\RELEASE\Aussie##_QualityReports\
database\.

N. Consistency ChkCntry
 Make sure the DBI in C:\X01CDBI is pointing at the local copy of database.
 Open a command window, then open the directory X01CDBI – (C:\>cd x01cdbi). Now type the
command “chkcntry nsw 1/1000”. (Substituting the relevant country code for ‘nsw’.) This process
runs the full range of consistency checks over the database structure and over the global partition
and stops before running the specific partitions.
 Once run open P:\Workspac\Cdbilogs\country code and arrange files in order of ‘Date Modified’
with the most recent at the top. The files that need to be opened and checked are the top
15: .RPT, .TDM, .TMC, .ADB, .POC.CH_, PFI.CHK, NFI.CHK, .LOG, NAME.CH_,
STREET.CH_, .PID, .PCI, .FMT, .EFR, .DIF. Make sure all these files have no errors. If errors are
present fix these using consistency tools and rerun process.
 Once all the logs are clean archive all above files on P:\PLM\RELEASE\
Aussie##_QualityReports\database\

© Copyright Sensis Pty. Ltd. 2006.

Note: The contents of this publication are subject to change. For the most recent version always refer to the on-line
documentation.

Wrap_Up_v2-1_W.doc 12/14
O. ListMPI
 Found in C:\X01CDBI (listMPI.exe)
 Run, then check logs at X01CDBI\logs (ListMpi.mdb).
 “CnsErrorCount” (consistency errors) should all be 0. If they are not, some consistency errors
remain in the logs on M:\AUS\Workspac. Investigate to see whether these are old errors that have
been resolved but not cleared from the logs (this can sometimes occur).
 If this is the case, manually delete the old logs and repeat the first two steps until all
CnsErrorCount values = 0. However, if there are still consistency errors within the dataset at this
time these must be fixed using the consistency correct tools. RE-run when fixed.
 Archive error logs (ListMpi.mdb- when clean) as Country_Release_Date_ListMpi.mdb
 Note: Copy mdb, don’t cut it. Rename after pasting in archive folder.

P. Do virus scan on complete dataset

 Right click on country_01 (eg Sax_01) in D:\Ta_Data
 Select “Scan with OfficeScan Client” (compressed check on)

Q. Conclusion
 Zip up dataset on D:\Ta_data and paste zipped copy on M:\AUS\TA_DATA_R## and P:\PLM\
RELEASE\Ta_data_R##\R_##_FinalDelivery\
 Rename network copy to country_Prewrapup then copy unzipped dataset to M:\AUS\Ta_Data and
refex. Add TOOLBOX tag ‘RELEASED’ .
 Notify conversion team that database is available (usually via email)
 Update “Wrap-up” fields in the Production Spreadsheet.
 Complete Navigation Release Handover Form and deliver to Product Line Management Team.
Located on S:\L&N\geo\PRIDE\Release handover forms\Aus###
 Complete Release Checklist and save it on P:\PLM\RELEASE\Aussie##_QualityReports\database

6) Records
Record Name Task Location Retention Disposal
Production Spreadsheet Update S:\L&N\GROUPS\PRODUCTN\Production 7 years Delete file
Spreadsheets
Navigation Release Form Complet S:\L&N\geo\PRIDE\Release handover forms\ 7 years Deliver to
e Aus### PLM team
Quality Reports All P:\PLM\RELEASE\Aussie##_QualityReports\ 7 years Delete file
database
Release_checklist_Vx.x.xls Update “P:\PLM\RELEASE\ 7 years Delete file
Aussie16_QualityReports\COUNTRY\Release
Checklist”

© Copyright Sensis Pty. Ltd. 2006.

Note: The contents of this publication are subject to change. For the most recent version always refer to the on-line
documentation.

Wrap_Up_v2-1_W.doc 13/14
© Copyright Sensis Pty. Ltd. 2006.
Note: The contents of this publication are subject to change. For the most recent version always refer to the on-line
documentation.

Wrap_Up_v2-1_W.doc 14/14