Microstation V8i Manual
Suyay Escarsega
The data conversion from the oracle database to dgn works fine. I see in Microstation that the coordinates are identical with the counterparts in the Oracle database. However, Microstation doesn't seem to know that it has a coordinate system. It says .
In processes 'downstream' requires that the dgn files have a coordinate system for further usage. This is now a manual step, that we want to avoid. Is someone familiair with this and knows how we can setup FME to write the coordinate information?
Basically every writer has a coordinate system parameter, which will identify on the output file what the coordinate system is.It default to same as source, which normally works, except in your case the Oracle db doesn't know what the coordinate system is.
A quick way you can test whether a file has a coordinate system is to open it back up in the Data Inspector, and in the lower right corner the coordinate system and units will be there. Does it look any different when you read in a file where you have manually set its coordinate system in Microstation? When you manually set the coordinate system, does it save it to the dgn file or the microstation Project/Workspace? I think it could be a limitation of the dgn format, that you need to tell it what its coordinate system is when you open the file.
Unfortunately, this is currently not possible to write out the coordinate system to the DGN file. This is a known limitation with the current Microstation writer. We do have an outstanding enhancement request to add coordinate system support to our Microstation reader/writer (internal reference: FMEENGINE-9051).
The District Department of Transportation (DDOT) Compendium lists policies and procedures for managing the District of Columbia's (District) transportation network and public space. The Standards and Manuals section of the DDOT Compendium contains a full list of all Standards and Manuals.
The Standard Specifications for Highways and Structures are standard for all DDOT contracts awarded by the Mayor of the District, the Council of the District, and/or the Contracting Officer. The Standard Specifications shall also be used for all the construction activities and material control within the Public Space of the District.
This manual has been prepared to assist the DDOT and its Consultants in the inventory, inspection, appraisal, and load rating of bridges under the District's jurisdiction in accordance with the Manual for Bridge Evaluation published by the American Association of State Highway and Transportation Officials (AASHTO). The program detailed in this manual will help implement the National Bridge Inspection Standards (NBIS) as issued by FHWA.
The Manual on Uniform Traffic Control Devices for Streets and Highways (MUTCD) is a document issued by the Federal Highway Administration (FHWA) of the United States Department of Transportation (USDOT) to specify the standards by which traffic signs, road surface markings, and signals are designed, installed, and used.
The following Right-of-way (ROW) policies and procedures are intended to establish a fair and efficient process for completing ROW acquisitions and transfers, consistent with federal and local regulations.
These documents provide the policies and procedures for utility accommodation and relocation within the Public Space for DDOT construction projects. The Manual establishes a fair and efficient process for completing utility work, consistent with federal and local regulations and DDOT Standards. In addition, this Manual is intended to be the companion of the DDOT Design and Engineering Manual, and together provide the utility coordination and technical requirements required to accomplish utility accommodation and relocation in advance of or in conjunction with DDOT construction projects.
The purpose of these documents is to provide guidance to practitioners in the implementation and management of work zones throughout the District, as well as provide the basis for the developing various work zone related documents.
You can submit jobs from within MicroStation by installing the integrated submission script, or you can submit them from the Deadline Monitor. The instructions for installing the integrated submission script can be found further down this page.
Design File(s): This option is only relevant to the Monitor Submitter, and specifies which Design File(s) to use for the selected operation. Multiple design files may be specified in order to submit a batch of jobs. For the integrated Submitter, this will always be the DGN file that is currently open.
Use Current Settings: This checkbox is only available from the integrated submitter. If checked, a new settings file will be created and submitted with the Job, based on the settings in the current MicroStation session.
When using the integrated submitter to submit through Microstation you have the ability to use any of the event plugins that you have enabled through the Deadline Monitor. This is done by opening the Pipeline Tools window via the Pipeline Tools button. This window is explained further in the Pipeline Tools documentation.
This section defines the possible locations for ustation.exe for different versions of MicroStation. The Deadline Workers will look for the executable in each of these locations (in order) when it tries to render a MicroStation job.
This switch determines whether the contents of a script will be written to the Deadline Worker log. This only applies for script job operations. Writing the contents of an MVBA script is currently not supported.
The following procedures describe how to install the integrated MicroStation submission script. This script enables MicroStation jobs to be submitted to Deadline directly from the MicroStation GUI. The following procedure has been tested in MicroStation v8i SS3 (08.11.09).
The integrated and Monitor MicroStation submitters have a feature that saves previously selected values for specific controls as Custom Properties in the design file that was used for submission, so that they can be restored automatically for future submissions.
Sticky Settings: For a given control, if there is a sticky value present in the scene file, it will be used first if the control is flagged as sticky in MicroStation_StickySettings.ini.
As of Deadline 7.2.1 we have changed the way we are installing the integrated submission script. In order to update from an older version you will need to remove the old submitter and then install the new one using the new method (submitter installer or manually). The files that need to be removed are:
If the menu entry does not appear it generally means that the configuration entry MS_GUIDGNLIBLIST is being modified by another cfg file. In this case you will want to append %localappdata%\Thinkbox\Deadline\submitters\MicrostationSubmitter\*.dgnlib to the MS_GUIDGNLIBLIST variable, which can be done through the Workspace->Configuration Menu.
You can use a *.dws DWG settings file when submitting a DWG export job to ensure a correctly compliant DWG file is created which is compatible with the 3rd party application you intend to import it into. Check with the developer of the 3rd party application developer to confirm the correct version/specification of DWG file format which it supports, if you have difficulty importing certain DWG files exported from MicroStation.
This chapter will walk you through a typical Axiom product installation. These instructions apply to both MicroStation V8 and V10. Microsoft Office Importer for V8 and V10 are used in these examples, but you can use these instructions for other tools and multi-tool installers for both MicroStation V8/XM/V8i and V10.
RasterDgn Resize Canvas lets you interactively change the dimensions of a raster reference file without scaling the image in that file. This means you can add empty working area to a raster reference file or you can crop it.
RasterDgn Copy makes it easy to copy raster data (pixels) from one part of a raster reference file into another. It can even copy pixels between raster reference files just as easily. Or you can create a brand new raster reference file from the copied pixels.
On Raster File Type/Compression Combinations: All listed file types have been tested with all listed compression types and all listed color depths but not necessarily every combination of those compression types and color depths.
!Unexpected End of FormulaIf your raster reference file is not level, use RasterDgn Deskew to fix it. In the picture above, RasterDgn automatically analyzed the raster reference file and determined the exact angle by which it was skewed.
Stamping is the process of turning vector elements drawn with MicroStation into raster pixels in a raster reference file. RasterDgn Stamp can significantly extend the life of your raster files.
Technical Details: Why is the Continue button necessary? RasterDgn asks you to tell it when you are done editing the raster file in your external program because many external programs do not lock the file in a standard way, so RasterDgn cannot reliably detect automatically when you are done editing them. Doing this ensures you do not edit the raster file simultaneously using RasterDgn and your external program, which could result in some of your modifications being lost.
Technical Note: Resize Canvas does partially overlap RasterDgn Crop functionality-wise. They can both decrease the dimensions of a raster reference file without scaling it down, which is the definition of cropping. But their purposes are really quite different: Resize Canvas is really for making your raster file bigger without scaling it up. And Crop can also optionally just clip your raster reference file instead of cropping it, leaving the actual raster file unchanged.
4a15465005