Creating automated tDPR in Geo Web Publisher

Hi Mike,

I would first make sure the .db shows in each row the xy extensions, to verify the .db you can follow the steps described here

http://communities.bentley.com/products/geospatial/server/w/geospatial_server__wiki/12549.gwp2055-how-to-view-tdpr-and-traster-index-files

If the .db contains all the .dpr file extensions…

…note that that the tDPR workflow has been designed to display at a large scale, with a minimum set of DGNs displayed at the same time. In tDPR 1 DGN = 1 DPR file and If you fit to the entire dataset, you will display (load in memory) all dpr files. I don’t know how many dpr you have but this could explain what is happening, simply you may be requesting too much data.

To prevent loading all the files, you must define a scale range, there is no need for such detail when fitting the whole data. Could you please test setting the Map Layer to 1:5000 for example (depending on the amount of levels and elements per dgn this could be even lower). Then in WMS mode zoom in and verify if a location where you know there is data (and below that scale range) displays the data.

What you can consider for startup/overview layer is the use of an iDPR layer that contains limited levels.

Let us know if it helps
Regards
Carlos

Hi Carlos and thanks for the reply.

Im not sure if I follow you all the way, but at least a little :)

Yes the .db file contains all the .dpr extenstions. But the name column refers to the dgn source file (not the created dpr), is that correct?

In my scenario I'm intrested in viewing the dgn files in large scales, between 1:5 -> 1:100 so I guess tDPR is a good sugestion for me? And when I try to view the information I have been witin those scale levels. So I guess that shouldn't be to much data in that scale?

In my test I have only tried to convert 25 dgn files (meaning the 25 dpr files are created).

Dont know if you could have any other idea what could be causing this?

In theory it looks you have everything properly set. The index file contains the extensions, the dpr files were created.

As I don't know what WMS client is being used to test the data, it would be good to confirm if something is published/displayed through the Geo Web Publisher Map Viewer (GWP Examples site: http://servername/Examples/default.aspx), perhaps the publishing fails only through the OGC WMS?

Regards,
Carlos

Hi

Im using OpenLayers and that might of course be the case. But I'm thinking that it works great with all other wms -layer that are created with other conversions for the same source dgn files. So therefor I'm thinking I'm doing something wrong with the tDPR conversion. Perhaps with the coordinate transformation?

Because the wms-call dont get any error, just an white image (meaning no data is there).
I have the dgn files stored in the same coordinate system (EPSG:3021) that I'm reuqesting from the wms-client.

When I look at the extent (and this I should of course checked earlier) for the wms-layer and the extent in the .db file the extents are "wrong" (only the Y coordinate value is wrong) compared to where the actual data is stored in the dgn file.

My tDPR config file look like this (I have tried removing the coordinate transformation also since its not much of a transformation):

<ConversionParameter xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<InputFormat>Dgn</InputFormat>
<SeedFile>
<FileName>C:\Bentley\data\seed\01_sed.dgn</FileName>
<!--ModelName is optional-->
<ModelName>Default</ModelName>
</SeedFile>
<OutputFormat>Dpr</OutputFormat>
<Reprojection>
<SourceCoordinateSystem>EPSG:3021</SourceCoordinateSystem>
<TargetCoordinateSystem>EPSG:3021</TargetCoordinateSystem>
</Reprojection>
<WorkspaceProject>
</WorkspaceProject>
</ConversionParameter>

Br
Mike

For example if I try with this .dgn file (attached) the data in the file (looking in Microstation) is located in x 1628442 and y=6588773

But if I look at the .db file created by the tDPR conversion I have one row saying:

Xmin:1628437,041

XMax:1628480,644

YMin:1290757,877

YMax:1290790,633

And the extent in the wms layer gets those values. And as I wrote before, the X values are great, but how come the Y values gets all wrong?

tdpr_example.dgn

Hello Mike,

I get the following extensions in the .db

I converted the V7 file you sent to v8 and used a V8 seed file with the EPSG:3021

Here are the files I used

Creating_automated_tDPR_in_Geo_Web_Publisher.zip