Hi
This is an very nice plot/print help to get the right scale to your plot/print and see how the print area is overlapping your design.
https://communities.bentley.com/products/microstation/w/askinga/1222/create-plot-shapes-with-this-macro
Can someone change this to Connect edition ?
//Tom
As an alternative i would also suggest looking at named boundaries:
https://communities.bentley.com/products/microstation/w/microstation__wiki/25068/named-boundaries
https://communities.bentley.com/products/microstation/w/microstation__wiki/25090/automating-sheet-creation-using-drawing-boundaries-and-named-boundaries
Along with drawing boundaries this may help it setting up sheet files for printing.
Hi David
Yes you right, there is a lot of options. But if you would want to print in size X and in scale Y and also in right coordinate system (PDF) under an minute your suggestion is not making the time or geolocatiion.
DavidI don´t know if you can do it or not but if you can please share how you did it.
Do Named Boundaries respect the Geolocation of a file?
While Bentley seems to believe that their solution is the absolutely best, brightest, and only way to get anything done, we often have requirements from clients to produce information in a certain way. Sometimes this includes georeferenced sheets - attach the base file 1:1, "in place", and move/scale/rotate the border to the proper location.
I do not believe Named Boundaries and Saved Views support this workflow. If not, then those suggestions are not helpful.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
MaryB said:I do not believe Named Boundaries and Saved Views support this workflow. If not, then those suggestions are not helpful.
Why do you believe that, have you tried it yourself? My post above mentions exactly what you need to do for Saved Views to work with sheets positioned of geospatially located plans.
My mistake. I was always working on the fact that a saved view is placed by cursor point - it is not automatically placed to be geolocated. Since placement by default was never globally accurate, I had assumed that the information simply wasn't available, and so never bothered with them again (since that would make them useless to me).
With your additional steps, it can indeed be corrected to the proper location and rotation. It is definitely an extra step or so, but it does overcome the initial flaw in saved views, and gives me ideas for ways to work with/around certain OpenRoads workflows.
I stand corrected, and I apologize for my ignorance!