|
|
| (45 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | The '''Link Editor''' access level grants access to the [[:Category:Link Editor|Link Editor menu]] and all functions contained by it.
| + | With the '''Link Editor''' access level you can create network links and have access to the [[:Category:Link Editor|Link Editor menu]] and all functions it contains. |
| | + | |
| | + | The link editor builds up on the functions available in the '''[[Editor|editor]]'''. |
| | | | |
| | ==Import from Exchange table== | | ==Import from Exchange table== |
| | | | |
| − | The format in TMC Studio is different from the former version. Therefore you will not be able to open the database created with TMC Editor in TMC Studio. You have to create a new database from the exported tables as Exchange Format. TMC Studio is able to import from Exchange Format ANSI and UTF-8.
| + | '''Concerning older TMC versions:''' |
| − | | + | → [[Open Database]] |
| − | '''Start TMC Studio''' | |
| − | | |
| − | [[File:Startpage TMC Studio.png]]
| |
| − | | |
| − | | |
| − | '''Select 'Import Location Table Exchange Format into new database''''
| |
| − | | |
| − | [[File:Import TMC Location Table Exchange Format.png]] | |
| − | | |
| − | | |
| − | '''Database file:''' Double click. Click on folder icon. Input database name and select where the database should be stored. When working with a local Firebird database, it must be stored on a local hard drive.
| |
| − | | |
| − | '''Source file:''' Double click. Click on folder and select exchange file if it was delivered as ZIP-File.
| |
| − | | |
| − | '''Source directory:''' Double click. Click on folder and select the directory where the DAT-Files from the Export Exchange are stored.
| |
| − | | |
| − | '''Run semantic checks:''' Ticking the box results in semantic checks being run after the import of the files.
| |
| − | | |
| − | In order to be able to press the OK button database file, source file and source directory must be defined.
| |
| − | | |
| − | ==Structure of INI file==
| |
| − | | |
| − | TMC Studio will store data in two INI files. One INI file contains data from the application!. This INI file is always located in the directory where the EXE file is installed.
| |
| − | | |
| − | The other INI file is always stored toghether with the database and has the same name as the database. This INI file contains the configurations and setting that you will input into the software menue-tools-options. It is recommended to not manually change this file.
| |
| | | | |
| − | The INI file of the application is delivered with the software. Normally there will be ine INI file per country you have licensed. The structure looks as follows:
| + | '''Start TMC Studio''' |
| | + | → [[Setup & Data Requirements for First Time Use|Setup & Data Requirements for First Time Use]] |
| | | | |
| − | | + | ==Define network database for attributing map liks== |
| − | [GeoLogix]
| |
| − | | |
| − | '''ProjectName = TMC Country Y''' If you have more than one country, this is the name shown in the selection when starting TMC studio.
| |
| − | | |
| − | '''UserProjectRegistryPath = Country Y''' Personal settings will be stored under this name.
| |
| − | | |
| − | '''ErrorSendMode = 2''' Should the software crash, you can send us an error message.
| |
| − | | |
| − | | |
| − | [About]
| |
| − | | |
| − | '''Name = Customer X'''
| |
| − | | |
| − | '''Serialnumber = N0QwQ-TRw''' Name and serial number are created by us and your license is registered with this information. Do not manually change this information.
| |
| − | | |
| − | | |
| − | [Database]
| |
| − | | |
| − | '''BSDatabaseType = FIREBIRD_LOCAL''' Normally you will work with Firebird local database.
| |
| − | | |
| − | '''User_Name = sysdba''' Standard for Firebird, don't change.
| |
| − | | |
| − | '''Password = masterkey''' Standard for Firebird, don't change.
| |
| − | | |
| − | '''Charset = UTF8''' Standard for Firebird, don't change.
| |
| − | | |
| − | ==Define Network database for attributing map liks== | |
| | | | |
| | To be able to link TMC Paths and Map, you will require the additional license for these functions. | | To be able to link TMC Paths and Map, you will require the additional license for these functions. |
| | Once you have these licences go through the following steps: | | Once you have these licences go through the following steps: |
| | | | |
| − | '''Menu → Link Editor → Import Network Database form Shapefile''' | + | '''Menu → Link Editor → [[Import Network Database From Shapefile|Import Network Database form Shapefile]]''' |
| − | | |
| − | [[File:Import Network.png]]
| |
| − | | |
| − | | |
| − | '''Shapefile:''' Double click. Click on folder and select the shape file with the network data.
| |
| − | | |
| − | '''Link ID:''' Select the field that contains the ID for the segment. It's mandatory your network table contain a unique ID for each segment.
| |
| − | | |
| − | '''Link Name:''' Select the field that contains the street names; optional, but it's use is recommended.
| |
| − | | |
| − | '''From Node:''' Optional and has no effect on linking - field with information from node.
| |
| − | | |
| − | '''To Node:''' Optional and has no effect on linking – field with information to node.
| |
| − | | |
| − | '''From Segment:''' Optional and has no effect on linking – field with information from Segment.
| |
| − | | |
| − | '''To Segment:''' Optional and has no effect on linking – field with information to Segment.
| |
| − | | |
| − | '''Link Type:''' Select field that contains information regarding Road Type. It's usually named FRC
| |
| − | | |
| − | '''Link Type Filter:''' The filter will show which road types are available in the shape file. You can select all types for import or limit the import certain types. If you select 1, 2, and 3 you will be able to import 4 and 5 later.
| |
| − | | |
| − | '''Connection Settings:''' If you want to import into an existing database, choose it here.
| |
| − | | |
| − | '''Create Database:''' If you want to create a new database enter the destination here. With Firebird local it must always be on a local hard drive.
| |
| − | | |
| − | '''Delete existing data in network database:''' !!
| |
| − | | |
| − | Depending on the number of imported segments this task can take several hours. An approximate estimation is shown in the import screen. It will also show how many segments already been processed.
| |
| | | | |
| | ==Configuration of the Link Editor== | | ==Configuration of the Link Editor== |
| | | | |
| − | '''Menu → Tools → Options → Link Editor
| + | Amongst other things, this page is used to '''enable the link editor's buttons & functions'''. |
| − | | |
| − | [[File:Options - Link Editor.png]]
| |
| − | | |
| − | '''Enable:''' When using Link Editor this box should be ticked
| |
| − | '''Connection Settings:''' If you imported your data from Shapefile, these setting should already be in order.
| |
| − | *Database Type - must be Firebird (local)
| |
| − | *Database - click on folder to select database
| |
| − | *User Name - must be sysdba
| |
| − | *Password - must be masterkey
| |
| − | | |
| − | '''Layer Properties:''' Configuration of the network layer, see next entry.
| |
| − | | |
| − | '''Network Cache File / Directory:''' Define where the cache file will be stored.
| |
| − | | |
| − | '''Display Network Link:''' Define the color and pattern of network links on the map.
| |
| − | | |
| − | '''Display TMC Link:''' Define color and pattern of TMC links on the map.
| |
| − | | |
| − | ==Layer Properties==
| |
| − | | |
| − | [[File:Edit Layer Configuration File.png]]
| |
| − | | |
| − | Network database contains linear data. Here you can define how the various roadtypes should be represented on the map.
| |
| − | | |
| − | '''Name:''' Define name of the level.
| |
| − | | |
| − | '''Visible at scale from/to:''' Define the scale from where to where the individaul levels are visible.
| |
| − | *It makes little sense showing all levels constantly since this slows down the program. It is therefore sensible to define different parameters depending on the road's importance.
| |
| − | *For Instance: Motorway from 0 to 500'000; Main roads from 0 to 100'000; Secondary roads from 0 to 50'000; Urban roads from 0 to 25'000
| |
| − | | |
| − | '''Transparency:''' Can be kept at 100.
| |
| − | | |
| − | '''Filter:''' Set 'ROADTYPE =' and then select road level.
| |
| − | | |
| − | '''Lines:''' Define color and pattern.
| |
| − | | |
| − | ==Configuration for Routing==
| |
| − | | |
| − | Menu → Tools → Options → Link Editor → Routing
| |
| | | | |
| − | [[File:Routing.png]] | + | '''Menu → Tools → Options → [[Options#Link Editor|Link Editor]] |
| | | | |
| | + | ==Using the Link Editor Menu== |
| | | | |
| − | Define a cost factor for the various road types. It depends on the structure of your network what makes most sense and gives the best results. As soon as you use the routing function you will see if the results make sense.
| + | This menu is used in order to import, export and manage any information concerning the link editor. |
| | | | |
| − | ==Creating and clearing Cache Files==
| + | '''Menu''' → [[:Category:Link Editor|'''Category Link Editor''']] |
| | | | |
| − | Menu → Link Editor → Routing → Create Cache File
| + | ==Using the Link Editor Toolbar== |
| | | | |
| − | This function MUST be performed after the creation of a network database. Without this the performance of Routing will be very poor. Depending on the number of segments in your database this function will take several hours.
| + | [[:Category:Toolbar Link Editor|Toolbar '''Link Editor''']] |
| | | | |
| − | Menu → Link Editor → Routing → Clear Cache File
| + | Now you will be able to start working with the Link Editor. |
| | | | |
| − | Use this function if you import new data into your network database. After this is done start 'Create Cache File'.
| + | [[File:ToolbarLinkEditor.png]] |
| | | | |
| − | ==Importing Network Links==
| + | Start by clicking '''[[Add Network Link|add network link]]''' [[File:ImageList-126.png|link=|alt=]]. Now click on the road near the beginning of a TMC-link. This will create the first network link. Make sure that the arrows of the network link are facing in the right direction (usually this will be the same direction as the arrows of the TMC-link are pointing in). |
| | | | |
| − | Menu → Link Editor → Import XML
| + | Now do the same at the other end of the TMC-link. Now that there is a network link at the beginning and at the end of the TMC-link press '''[[Routing|routing]]'''. In most cases [[File:RoutingButton.png]] will not only fill in the remaining network links, but also arrange all network links in the same direction and list them in the correct order in the window on the lower left-hand side. |
| | | | |
| − | [[file:Import XML.png]]
| + | Occasionally 'routing' experiences difficulties when placing the remaining network links. |
| | | | |
| − | If you had already defined TMC Links in the TMC Editor that information must be transferres to TMC Studio with Export XML. This will create an XML File containing all the information.
| + | Roundabouts can pose a problem resluting in 'routing' placing network links everywhere on the roundabout or going off in a nonsensical direction. Roads with different hierarcical levels can also be source of mistakes. |
| | | | |
| − | '''Source File:''' Double click. Click on folder and select the file you want to export. The program will look for ZIP files by default, so change it to XML. | + | 'Routing' will sometimes move the links to a road of a higher level (should it intersects with one), despite the road starting and ending on a lower hierachical level. |
| | | | |
| − | '''Clear Existing Links:''' Tick this box if you want to delete links that have already been created in the database. If you don't tick the box the link information in the database will be kept if it doen't already exist in the XML file. !!!
| + | Finally, in the rare case that the underlying data is in some way corrupted or badly composed, 'routing' will generate a network-link road that follows a completely different route (usually a very long one). |
| | | | |
| − | To be able to click the OK button you will be required to click the field, even if you don't tick the box.
| + | In these cases the easiest way is usually to lay the network links manually. When doing so, it is important to make sure that the sequence of the network links on the map corresponds with the sequence of the links in the list on the left-hand side. |
With the Link Editor access level you can create network links and have access to the Link Editor menu and all functions it contains.
The link editor builds up on the functions available in the editor.
Import from Exchange table
Concerning older TMC versions:
→ Open Database
Start TMC Studio
→ Setup & Data Requirements for First Time Use
Define network database for attributing map liks
To be able to link TMC Paths and Map, you will require the additional license for these functions.
Once you have these licences go through the following steps:
Menu → Link Editor → Import Network Database form Shapefile
Configuration of the Link Editor
Amongst other things, this page is used to enable the link editor's buttons & functions.
Menu → Tools → Options → Link Editor
This menu is used in order to import, export and manage any information concerning the link editor.
Menu → Category Link Editor
Using the Link Editor Toolbar
Toolbar Link Editor
Now you will be able to start working with the Link Editor.
Start by clicking add network link 
. Now click on the road near the beginning of a TMC-link. This will create the first network link. Make sure that the arrows of the network link are facing in the right direction (usually this will be the same direction as the arrows of the TMC-link are pointing in).
Now do the same at the other end of the TMC-link. Now that there is a network link at the beginning and at the end of the TMC-link press routing. In most cases 
will not only fill in the remaining network links, but also arrange all network links in the same direction and list them in the correct order in the window on the lower left-hand side.
Occasionally 'routing' experiences difficulties when placing the remaining network links.
Roundabouts can pose a problem resluting in 'routing' placing network links everywhere on the roundabout or going off in a nonsensical direction. Roads with different hierarcical levels can also be source of mistakes.
'Routing' will sometimes move the links to a road of a higher level (should it intersects with one), despite the road starting and ending on a lower hierachical level.
Finally, in the rare case that the underlying data is in some way corrupted or badly composed, 'routing' will generate a network-link road that follows a completely different route (usually a very long one).
In these cases the easiest way is usually to lay the network links manually. When doing so, it is important to make sure that the sequence of the network links on the map corresponds with the sequence of the links in the list on the left-hand side.
will not only fill in the remaining network links, but also arrange all network links in the same direction and list them in the correct order in the window on the lower left-hand side.
