What's New?

You will find everything you need to install card_1 version 10.1 in the Download Centre of our website. Here you will find the installation package, the installation guide and additional sample or template projects. You can also order your personal licence data here which you will need for the installation.

Here you find a complete overview of the system requirements of card_1 version 10.1.

First of all, we would like to reemphasize the importance of project data backup. Your project data is extremely valuable. A loss of data may cause significant workload and cost, which can be avoided easily. Therefore, it is in your own interest to check when you have saved your card_1 projects for the last time.

NOTE  We recommend that you save your project data before the installation of version 10.1.

The installation process of version 10.1 will run in parallel to a possibly existing card_1 version 10.0. Both card_1 versions may work in parallel. However, please note that the data of version 10.1 are not backward compatible and can therefore no longer be edited using version 10.0.

NOTE  Please note that projects that have been converted for card_1 version 10.1 can no longer be edited using older card_1 versions (no backward compatibility).

Your project data in card_1 version 10.1 can only be converted for projects from data version 8.4.0.0. Older projects (not older than version 7.7) must be previously converted using card_1 version 8.4. Standalone converters are available for projects that are older than version 7.7.

Our recommendation: Please bring any older projects to data version 8.4.x.x using card_1 version 8.4, at the latest before permanently uninstalling card_1 8.4. Otherwise, keep version 8.4 working on at least one of your workstations for subsequent conversion. This also requires Firebird version 2.5 to be installed.

• ALKIS Import: Substantial acceleration of ALKIS import, project data exchange and backup process.

• GeoInfoDok 7.1.2: Support of the new GeoInfoDok 7.1.2, valid from January 1st, 2024, for importing ALKIS data.

• Transformations: Additional transformation method to be used for conversion between DB_REF and the distortion-free coordinate systems for traffic facilities (VA systems), especially passenger stations.

• Measurement Data Formats: Import of measurement data, points and attributes in the formats Leica HeXML, Trimble JXL and Topcon LandXML.

• Junctions: A junction may be generated based on two or three roads involved. The basic model 'Junction' will then be recognised automatically and configured using a wizard. The junction can be generated in line with the requirements of RAL 2012 or freely configured.

• Corresponding Junctions: Neighbouring junctions whose definitions influence each other are automatically generated jointly.

• Free Bicycle and Pedestrian Lanes: It is possible to freely design a bicycle or pedestrian lane or a shared bicycle and pedestrian lane. A wizard which takes into account the requirements of EFA, ERA and H RSV may be used to specify the design parameters. Furthermore, junctions can be generated as t-junctions or crossroads. A connection to a road is also possible.

• Evaluations: The programme enables evaluations which may be used to directly derive classical data, such as topographic lines and slopes, as well as cross-section lines, from the resulting model. You can use this data as usual for subsequent processing steps.

• Remaining Area Automatic/Manual: These elements may be used to fill zones between other design elements and the route body. For the automatic remaining area, the connecting edges are re-determined during each update. The manual remaining area is more flexible, it allows the segment definition on connecting edges as well as the connection to a route body.

• Connecting Edges: Design elements can also be connected segment by segment to multiple existing elements. In addition, the connection to the edges of route bodies is possible.

• Trench Free: The freely designed trench enables you to flexibly place the tracking path on the bottom. This facilitates, for example, the connection to existing trenches. The upper structure is captured separately for bottom and slope. According to the German Guidelines for the Drainage of Roads (Richtlinien für die Entwässerung von Straßen, REwS), the upper trench edges may now be rounded. In this context, the tangent length of the rounding may be defined as a constant or a variable depending on the slope height. The functionality 'Closure with Embankment' is available for designing the start and end section.

• VA Systems: Additional transformation method to be used for conversion between DB_REF and the distortion-free coordinate systems for traffic facilities (VA systems), especially passenger stations.

• Platform Generator: Additional functionalities for quick and simple modeling of platforms.

• DB-GIS/AVANI: Import and export GND-Edit files in the formats DB-GIS and AVANI.

• Basic Switch Models: Extension of the rules framework 'Basis_Bahn' to include the basic switch models of the German guideline Ril Obri‑NE (Oberbau-Richtlinien für Nichtbundeseigene Eisenbahnen, Ausgabe 1984)

• Sewer Network Extension: A sewer network can be completely deleted or only extended. In this process, the programme will maintain a maximum of information, add new reaches and delete reaches that no longer exist, including logging and graphic visualisation.

• 3D Symbols: Additional 3D symbols for the visualisation of vegetation for structuring your 3D models.

• Incremental Backup: Only modified projects are saved during backup.

• Email Notification: Error information on backup can now be emailed to a pre-defined recipient.

Besides the traditional cross-section design, this module for version 10.1 comprises a basic package of both the New Road Design and the Construction kit ConKit.

This includes, for example, the creation of rural roads, motorways, pedestrian and bicycle lanes, the definition of traffic lanes and carriageway geometry, the generation of the route body including carriageway markings and entrances.

In addition, it includes design elements from the Construction kit ConKit, such as kerb, wall, shoulder, swale, slopes, ground connection, connection strips, remaining areas, etc.

In contrast, junctions, signs and parts of structures are not included.

The module should licence all functions and types, which fall into the application field Road Design and are not part of the module Cross-section Design / 3D Route Bo^dyBIM.

Compliant automated design of junctions, t-junctions, corresponding junctions, ramps, entrances and exits.

The module will be extended step by step to include bifurcations (for interchanges), roundabouts, service roads, ancillary facilities, etc.

Based on the Construction kit ConKit, this module should enable interactive subject-specific design of, for example, lateral clearances of railway and road routes, squares, entrances and traffic areas of private and commercial properties as well as terrain surfaces.

Alignments, topographic lines and terrain models are required for the design, according to the situation.

Use the Issue Management in card_1 to document and manage tasks, problems and any other information, which shall be processed at a later project stage and, if appropriate, shared with colleagues.

However, issues are not only text information. An important characteristic of issues is that fact that they may be located in your project. This means that issues have a 2D or 3D reference in your project model, with the advantage that, when you read the problem description, you will simultaneously see the problem in both the base map and the 3D project view.

The BCF interface is available for exchanging your issues with external project participants. This way, the tasks and messages managed in the issues can be easily handled jointly.

The Issue Management in card_1 is helpful for both the self-organisation and the communication between the users involved in a card_1 project or for the communication with external project partners.

During a card_1 freshup, the update process also refers to central project files.

When you first open a project after a freshup, you will receive a log message to say that the files in the central project should be checked. When you later open the central project, the programme will list the updated files. Mark the files which should be replaced by newer file versions.

NOTE  There are project files which are exclusively maintained by IB&T and will automatically be overwritten during a freshup with project conversion. These files shouldn't be adjusted but adopted during the freshup. A list may be found in the card_1 Help.

card_1 version 10.1 now uses version 2.2 of the graphics engine Ogre-Next. In addition to general bug fixes and performance improvements, it offers a new method for managing textures. All textures, e.g. in 3D symbols, are now reloaded when necessary and asynchronously. This may significantly shorten the time until the project is started and 3D symbols are displayed.

The print system for lists via FastReport was updated and modernised. The previous FastReport component already used in card_1 since its version 8.3 is now replaced by FastReport .NET. The new component offers reliable processing routines and a modern user interface, which makes the process of designing your outputs easier and more intuitive. In addition, you benefit from current outputs using standard file formats and a simplified installation.

In version 10.1, contact details of individuals and companies extend the card_1 data model. Use the contact catalogue to manage contact details of clients, data providers, subcontractors, BIM coordinators, etc. (see Contact Catalogue).

Optimisation of object update: Control options for updating objects are especially intended to facilitate the handling of technical objects. Object update may be temporarily disabled, which enables consecutive changes of parameters to be carried out faster. However, in view of numerous interdependencies between the objects, it is important that a current and valid state is regularly reproduced. This is why the object update rules have been revised.

• Object update is now generally enabled when a function group is accessed. This protects you from working unintentionally with disabled object update.

• When you generate design elements while object update is disabled, elements will be recalculated after modifications, in order to allow reasonable work with the system.

• When the object update is disabled and the project contains technical objects which should be recalculated, the programme now offers an improved type of display: The 'Perform Object Update' button is shown with a red background . In addition, an information text in the status display shows how many objects are not up to date. This creates greater transparency regarding the update status of your project data.

  

With Windows 10, Microsoft has created the possibility to 'scroll through inactive windows while pointing' in the mouse settings. Enabling this option causes a change in the flow of messages: The card_1 frame window with docked CAD menu no longer receives mouse wheel messages from the operating system, when the mouse is positioned in the CAD menu.

With version 10.1 it is again possible to scroll through the CAD menu with the mouse wheel.

Faster working: Due to the transition to the new version of Orgre-Next and the support of asynchronous loading of textures, the 3D project model is available more quickly for further processing.

Lines: Due to the transition to the new version of Orgre-Next, the limitation of the line points to be displayed was abandoned.

Virtual Reality: The Virtual Reality was improved based on the new version of Orgre-Next.

• When you wear the VR glasses, you will see that the 3D project view has substantially improved its performance. You will enjoy a significantly sharper and flicker-free vision.

• In addition, you will see your VR controllers with a pointer, so that you can easily refer to anomalies, save them as perspectives and document them for further processing.

Background map: Background maps can be displayed not only in their original appearance but also modified, e.g. pale or in grey scales. Thereby, the download and storage of raster images becomes obsolete for some application cases. This saves time and storage space.

Raster images: Raster images, which are only intended to be displayed, can be stored in external folders, especially in order to save storage space and to accelerate project backup.

• Multiple storage of raster images that are used in multiple projects is therefore no longer required.

• Since raster images do not constantly change during project editing, it is reasonable and in most cases even advantageous to avoid daily backup.

• When projects are processed using the network or the cloud, the network load may be reduced by referring to locally saved raster images. This can also contribute to raising the performance.

With card_1 version 10.1, you can combine pre-assignments across projects in your own rules frameworks.

• Rules frameworks are a simple solution in order to create general pre-assignments across projects. Differing from central projects, it is not necessary to consider all topics or there combinations in a rules framework.

• A rules framework can be specifically defined for a topic, a client, a client information request (Auftraggeber-Informationsanforderung, AIA), a regulation or something similar. For their usage in projects, the required rules frameworks are activated, when necessary.

• A rules framework can be activated automatically using project information (topic, region).

• A rules framework is edited and maintained in a specific rules framework project. Only when editing is completed, the finished rules framework will be published or updated for a project area.

• The contents of rules frameworks currently include catalogue entries, drawings, insertion files for drawing specifications and scripts (*.QPR, *.QPC).

• In a rules framework, you may also specify project sub-attributes, which are automatically entered when the project is created or the rules framework is activated. Use Edit Sub-attributes to add current values. This may be used, for example, in order to add the PROJIS number or any information regarding the client. Sub-attributes may be used directly in drawings.

With the Visualisation module, you now have the possibility to use your own 3D symbols.

Use free tools, such as Tinkercad or Blender, to create your own 3D models (textured, if desired) and import them in the 3D symbol catalogue. Supported 3D model formats for import include OBJ, FBX and GLTF/GLB. As a next step, you can define the insertion position, the orientation and the scaling for the 3D symbols. By analogy with the 3D symbols, which we make available to you as a rules framework, you may use your own 3D symbols for editing and design of your project models.

The component catalogue now enables the definition of multiple components in one cross-section (Multi Cross-sections). Use the catalogue to store corresponding cross-section drawings. Components may be assigned a material. This way, it is possible to generate elongated objects along tracking paths.

The rules framework 'Basis_Strasse' was extended to include components for box drains, slotted and through channels, amphibian guidance systems, concrete crash barriers, and angled retaining walls.

The new contact catalogue in card_1 version 10.1 enables you to manage your project-related contacts.

• It is possible to store both organisations and individuals. This includes the role carried out in a project as well as a contact category, allowing a better filtering in individual card_1 applications.

• The catalogue also supports the assignment of individuals to organisations.

• For each contact, you can define whether it may or should be visible for users of other companies when a project is passed on.

Sub-attribute definitions for DB GIS have been revised for purposes of DB InfraGO:

• Sub-attribute definitions are no longer abbreviated. For better understanding, all definitions are written and explained in their description.

• Attributes, that are determined directly from the geometry, are abandoned. The attributes track type, chainage line type, railway station number (consisting of DB Netz key and code number/signalling and control district) and node description (derived from the railway station number) are added.

• Some of the sub-attribute definitions are no longer managed as plain text or number, but with a unit (example: horizontal and vertical accuracy in metres).

• In order to ensure correct MDB export, some of the sub-attribute definitions are indexed. This enables, for example, a better illustration of nodes and edges of a switch. The indexed record type 11 (general point type) provides information on all involved alignments of a switch. The indexed record type 31 (track node) is used to display all alignment and switch nodes.

Sub-attributes can now be specifically assigned to subordinate alignment types. This way, each alignment may be assigned user-defined attributes and pre-settings differentiated according to the code, type or subtype.

Distance reductions due to elevation and projection for primary coordinate systems are now preset for preparing the measured data.

Project Start Wizard: Use the new wizard for a more comfortable entry into new projects.

• Based on the selected project region, you can now define the coordinate system and the project extent. If you don't want to define the coordinate system using the wizard, the primary coordinate system ETRS89/UTM zone 32 (EPSG code 25832) will be set automatically.

  In addition to federal states (project attribute Region), you can now also select towns and rural districts. This ensures an automatic assignment to a federal state.

• Select Coordinate System: The relevant coordinate systems are offered for selection depending on the federal state selected. The default coordinate system for the selected federal state is preset.

  

• Define Project Extent: A background map is loaded automatically. It provides orientation for the graphic definition of project extent.

  

Now, an unregistered project no longer prevents the creation of a new project with the same name. A message will now be displayed to say that the folder already exists.

Email configuration file, new parameter 'Cc': This enables you to specify the email address of the recipient of a copy.

The programme now checks whether the versions of the files cardbackup.jar and export.jar are identical. If this is not the case, the backup will be cancelled and a corresponding message will be output in the log. Copy the mismatching jar file from the card_1 programme folder to your backup programme folder.

New import format E57: The import was extended to include the compact, non-proprietary data format E57.

New Batch Import Function: The multiple file selection can now be used to import multiple point clouds in the formats LAS/LAZ and E57 in a single working step.

For example, public authorities provide comprehensive laser scan data as a basis for your transport infrastructure planning. Since point clouds are provided in tiles, your project area may comprise a large number of files.

Mark using Attributes: The function groups for editing topography have been extended to include a marking option using sub- and object attributes. In this process, you may also use multiple attributes for marking purposes.

Example: Mark all lines of the current layer, which have the entry 'Elektro' in the sub-attribute field 'Branche>Thema', whose value in the sub-attribute field 'kV' exceeds 110 and whose 2D line length exceeds 1 m.

GIS evaluation functions, such as the creation of drawings from sub-attributes or the generation of area signatures within circumference lines, can now be accessed directly via topography editing, if GIS Import or GIS Export is licenced. This way, the detour leading to these functions within GIS data exchange becomes obsolete.

Function Structures made of Lines - Crash Barrier: If the traffic barrier includes a lowering, it will now be generated within the topographic line.

Simple generation of entrances and exits: The new card_1 version 10.1 enables quick and simple generation of entrances and exits for rural roads and motorways in accordance with the valid guidelines. Complex structures such as traffic lane additions and subtractions or two-lane entries and exits are also supported. The result is a technical 3D model that can be easily checked and edited.

As a first step, design the horizontal and vertical alignment of a connecting ramp. Based on this, generate the route body of the ramp. card_1 automatically recognises whether the ramp is part of an entrance or an exit and generates the entry and exit lane as well as the transition segments to the ramp.

The cross-fall of the entry and exit lane can be adjusted individually. It is also possible to select the types designated in the guidelines, including traffic lane additions and subtractions or two-lane entries and exits. Technically correct solutions for traffic lane and hardstrip widenings will also be found in this process.

Thanks to the simplicity of the generation process, you can check quickly whether the entrances and exits are feasible in the particular situation in terms of space and vertical profile. The generated 3D model is an ideal basis for visual examination. In addition, the programme will check the carriageway geometry for zones with poor drainage. The results will be output in the journal system and zones with poor drainage will be displayed in the graphics. All parameters, such as the length and width of entry and exit lanes, can be modified at any time. The new result will be generated with a single click.

Components from individual cross-sections: It is now possible to generate elongated components with individual cross-sections, e.g. concrete crash barriers, other walls or draining channels, and angled retaining walls. Cross-sections can be selected from the component catalogue. The catalogue may also contain user-defined cross-sections based on drawings or multi cross-sections (see Component Catalogue).

Clamped Elements: So-called clamped elements are now available to ensure a simple and elegant interconnection of surface elements, e.g for tracking paths, swales and trenches. These clamped elements enable smooth interconnections between the selected connecting objects. For this purpose, the programme automatically generates a spline which connects tangentially to the existing elements both horizontally and vertically.

Alignment Attributes - Subtype: The subtype of an alignment is already selected in the first dialogue box along with the alignment type. The alignment attributes matching the respective subtype will be automatically pre-assigned. For example, the type 'Railway - Track Opposite Designated Direction' will be automatically assigned the direction code 2.

Alignment Attributes - Alignment Type 'Railway': Now, the subtypes 'Track Alignment' and 'Chainage Line' have different dialogue boxes for entering parameters.

Additional sub-attribute definitions have been created for the GND-Edit interface (see also Sub-attribute definitions). In the GND specifications, track alignments and chainage lines have different sub-attributes. For example, a track alignment has the sub-attribute 'Track Type' for aboveground and inoperative railway lines or station tracks. In contrast, a chainage line has the sub-attribute 'Chainage Line Type' for left, right or all tracks.

Functions Save Points Single and Save Points Multiple:

• Data Selection (Save Multiple): It is now possible to select not only alignments but also switches. The new hierarchical list contains all chainage data of the selected alignment. By default, the reference vertical alignments and reference cant strings are pre-selected.

• Attributes: Attributes are defined in a separate tab.

  • In addition, it is now possible to define a railway station number. Two attributes (DB Netz key and signalling and control district), which are used to determine the railway station number and to ensure correct node description, have been created for this purpose. This will reduce error and instructive messages generated during the test procedure in GND-Edit.

  • The horizontal and vertical accuracy (GND-Edit field names MP/MPEXP and MH/MHEXP) must now be indicated in metres. During GND-Edit import and export, this value is automatically 'translated' into the required system notation (card_1 / GND-Edit).

  • Now, the OSKA number is always copied from the last four characters of the card_1 point code.

• Route Points Horizontal: Alignment master points and ramp points are defined in a single tab. This is thematically more suitable, as certain check boxes have influence on joint point generation. In addition, alignment master points and ramp points can now be prepared separately for left track, right track and station track.

• Vertical Alignment Points (Save Multiple): Vertical alignment points can now be prepared separately for left track, right track and station track. In addition, it is possible to generate alignment, ramp and switch points with heights.

  Additional functions are implemented for VERM.ESN. In addition to the points in accordance with the GND specification, the programme also generates vertical points of intersection for gradient change points with vertical curves.

• Switch Points:

  • The switch start point can no longer be selected optionally. When a switch has been chosen in the 'Data Selection', the corresponding switch start will be generated as well.

  • For diamond crossings with slip(s), the programme automatically generates points for switch ends (according to GND specifications), which means points for A-B in the case of diamond crossings with single slip and points for A-D in the case of diamond crossings with double slip. The points are generated instead of the switch start. For diamond crossings, the crossing centre point is generated as switch start point.

  • According to GND specifications, the check boxes 'Switch End' and 'Switch Centre Point' are not relevant and therefore disabled. Select the check boxes in order to generate the ends and centre points of simple switches.

  • New features include the possibility to generate shunting limit signal points. These points can be placed either at the actual position of the shunting limit signal or at the two foots on the corresponding alignments. Alternatively, it is possible to generate all three (or six in the case of diamond crossings with slip(s)) of these points. This is based on the prerequisite that all alignments concerned have been marked in the 'Data Selection'. If one of the alignments is missing, the programme can only generate one foot on one of the alignments.

  • Switch numbers are created in accordance with regional specifications of Deutsche Bahn Region Nord. In addition, node combinations (switch start linked to switch start) are possible. In this case, two different switch nodes will be assigned the same point address / point number.

Function Change Attributes: Due to the changes made to sub-attribute definitions for GND (see also Sub-attribute Definitions), the dialogue box for checking and changing attributes has been adjusted accordingly.

• A point may now contain up to four entries of record type 11 (example: node switch start linked to switch start). The dialogue box now offers four fields each for the sub-attributes 'Chainage', 'Railway Line Number' and 'Direction Code'.

• Use the buttons 'Previous Point' and 'Next Point' to quickly navigate between the points and to check or change point attributes.

The Class Editor for Sewer Objects in Water Management Pro enables you to define and manage your own attributes. This can be helpful, for example, for the assignment of attributes according to client information requests (Auftraggeber-Informationsanforderungen, AIA) and for the assignment of services according to the standard services catalogue (FitMatchKey).

These are now also available for the resulting technical objects in card_1 for further use and especially for transfer in the IFC or CPIXML format. In the case of changes or extensions to Water Management Pro, the attributes will be updated when new technical objects are generated.

Drawings from Background Maps: Now, raster drawings can also be derived from background maps. The drawing to be created is based on the currently set background map. The level of detail of the resulting drawing can be controlled through the selected pixel spacing. Consequently, it is no longer necessary to save raster images before using them in drawings.

Insertion files and drawing objects can now be selected from an activated user-defined rules framework.

• Insertion files (command INSERT): '<^User-defined Rules Framework>File'

• Drawing objects (e.g. command TITLEBLOCK): 'Object(<^User-defined Rules Framework>PLT file)'

• If the syntax '<?>File' or 'Object(<?>PLT file)' is used instead of a specific rules framework, the file will be searched in the following order: local, central, user-defined rules frameworks, system rules frameworks.

Function Import Point Codes: The point code assignment was enhanced. The points are now considered separately according to topics. The dialogue box contains multiple tabs with different topics:

• Horizontal and vertical alignment points, ramp points: Point codes are defined for alignments, heights and ramps. New features include the possibility to assign point codes separately for left track, right track and station track.

• Other point types: Codes are defined for alignment-independent point data. The list of possible point types was significantly extended and adjusted to meet current and future requirements of the GND specifications.

Function Import MDB:

• Selection of coordinate system: For a better explanation of record types, they have been assigned a description according to the specifications for track network data.

• Selection of Alignments: The new hierarchical list allows data structure to be improved according to open track and station alignments.

  • All alignments of a railway line are collected under the corresponding line number, which facilitates the search for specific alignments. The alignment type names contain your selected coordinate system codes (e.g. DR0, V00).

  • Up to now, in case of incorrect selection, the GND-Edit import had to be cancelled and restarted. Now it is possible to return to the coordinate system selection without cancelling the import process.

  • New features also include the display of start and end chainages of the alignments. This way, you can select exactly the required data for a specific project section without overloading the project with unnecessary data.

• Probably available with version 10.101: Prior to the actual import, the accuracy of the alignment is additionally determined from the horizontal accuracy of the points, and displayed. Alignment-independent points may be optionally imported.

Functions Export MDB-DBGIS/MDB-AVANI: The selection of the data to be exported is clearly arranged and simpler. In addition to the alignments, alignment-independent points and cross-track distances are also output.

New Export Format XPlan: GIS export was extended in order to cover the possibility of exporting data in XPlan format. This format is used to exchange urban land-use plans, spatial development plans and landscape plans. Many public authorities require the use of XPlan format or have planned its mandatory introduction. Since card_1 supports this standard, you can use card_1 to carry out all your measurement or design processes in these fields and deliver results which comply with the applicable regulations.