How to set a point at 0,0 co-ordinates?

My minds gone completely blank!!

I have a site plan and I want to set a point at 0,0 which is then used for setting out/co-ordinating other points. 

Could someone let me know how to do this.

Parents
  • are you using real world or relative to a point?

    If you are like architects they want to make a point on the slab be the new 0,0  and everything is relative to that point, create a new acs and set 0,0 at that point or create sub model ref attach the real model and  move the ref to 0,0 and  merge in ref its now like you want relative to a point  but you still have the realworld version for real coord setout for eastings and northings..

    Which you can call out the real point for your origin point on your table...

    You can even just change the settings so your measuring relative to a point , or use the ordinate dims tool then you can get all the points and copy the info into a table

    Lots of ways but we don't really know what you want to achieve.

    Lorys

    Started msnt work 1990 - Retired  Nov 2022 ( oh boy am I old )

    But was long time user V8iss10 (8.11.09.919) dabbler CE  update 16 (10.16.00.80) 

    MicroStation user since 1990 Melbourne Australia.
    click link to PM me 

  • Depends on who you are working for and what they have in the BEP.

    If you are an architect or engineer using OBD or Mstn's Dynamic Views to generate drawings you will likely need to move the Global Origin using the GO= tool, but model near the DFC to ensure that you are modeling within the recommended SWA / resolution. Don't be surprised if you have troubles with drawing extraction if you are modeling outside the SWA.

    Apparently, moving the GO etc is old skool, and georeferencing is the recommended way to get your correct coordinates. Especially if your BEP requires it for conversion to fancy geocoordinate systems like Snakegrid etc.

  • Depends on who you are working for and what they have in the BEP.

    If you are an architect or engineer

    I often receive autocad files where not only the survey but the design has been grouped and moved to 0,0 and rotated ( sometimes scaled to avoid using meters.. also they can use one corner to do relative measurements and draw lines.. I truely hate this approach... as nothing is georeferenced anymore.. I found out that they don't have to do this in acad before export to dgn .. they can just change the acs location.. but trying to get others supplying data the way you need it is very difficult.. especially  long term acad architecturals and they train their juniors to do the same ... so  perpetuating the process... arrrh!

    Lorys

    Started msnt work 1990 - Retired  Nov 2022 ( oh boy am I old )

    But was long time user V8iss10 (8.11.09.919) dabbler CE  update 16 (10.16.00.80) 

    MicroStation user since 1990 Melbourne Australia.
    click link to PM me 

  • As a rule. I always advise my clients to use the DWG open OPTIONS and change the UNITS to suit the project. plus turn  the 2d options for 2d drawing and then check the scale. They generally find that 9-10 it is wrong and users then use reference files scales to correct it (badly) and move the ref into the correct location, (crazy), so changing them to suit (M to MM or MM to M, Feet to Inches, Inches to Feet) usually sorts out the scale and the GEO location. ie it could be 1000x too small and 1000 x out of location.

    I also create an icon for GO=0,0  and add it to the task bar Q9 and/or a function key, where the keyin is xy=0,0,0.  this will interact with tools such as place smartline, move etc

  • Yes, the problem persists with BIM and Revit files, which has a 32km design area so have to make provision for defining Shared Coordinates. OBD also has its SWA design area limitation.

    I think that the geodectic side of things is really quite esoteric and beyond most CAD admins (myself included). Often you will find seed files that are not tailored to OBD's limitations that you are forced to use even though the modeling area is outside the recommended SWA. I think that this is mainly due to the client's CAD Admins not willing to move the GO and provide project-specific seed files or use georeferencing as this would need to be reconcilled with their existing database of models? Bentley rep, why did you not tell me blah blah... err ok there is no hard and fast rule etc etc

    Also, a lot of the geodectic stuff is applied retrospectively. Surveyors cost money, although this is changing.

    Ideally, you would use a universal free of charge Google Earth type ProjectWise interface and and fence an area and download your CAD file backgound with all the geodetic info. Dgns should have the option behave like Geotiffs. Get the rotation, position and scaling in as early as possible. Drag and drop any dgn onto another and the dgn is aligned / scaled properly like Geotiffs in the raster app space.

    Bentley has made big inroads into Digital Twins, which promises the means to reduce 'dark data' that is not indexed properly or usable. In the process of jumping onto the next-big-thing-with-the-big-dogs band wagon, it would be good to address the problem 2d drawing information poses, along the way. There is tons of info in this old fatberg but most of it is not georeferenced or oriented in 3d correctly... ie dark data.

    A good starting point would be to make it easier to generate new drawings in a spatially unambiguous and correct way:- Hypermodeling in a georeferenced environment... starting from the 'new' button.

  • Looking at the new WMTS referencing function previewed in Mstn U15, wouldn't be good to use this as the means to set up correctly georeferenced and/or correctly modified GO= files in Mstn...?

    1. CAD Admin needs to set up seed file for new project. Fires up a dgn with the WMTS attachment for the UK (incl Scotland Stuck out tongue winking eye).

    2. CAD Admin zooms to the desired site. Calls up 'Define Seed' tool and defines extent of project (can be over well oversized) using a Fence or Shape.

    3. Mstn generates a new dgn with the correct georeferencing and/or GO= settings. Option to show and define SWA. Leverages OBD's SWA Validator tool.

  • I can see this being a great feature for demo jocks if a seed file with a WMTS attachment is included in base install / dataset.

    "What are you working on?"

    "Oh, a small site on the Old Kent Rd. No. 122"

    Generate and open seed... zoom to OKR.

    Is there a Google Map-style search tool? If not, demo jock will need to fire up web browser first and copy the coordinates.

    "... this one?"

    "Yea. Hmmm I didn't notice that extension next door"

    "No worries, my Bentley WMTS attachment includes cadaster, Ordinance Surey CAD info as well as links to the local planning authority's applications map. Let's overlay that"

    "Yea, not on there. Permitted development waiver? I wonder how they built that over the drains in the backyard?"

    "No probs. Let's overlay the utilities companies plans. BTW, we can copy all of this through into our dgn here when we are done being nosy"

    "Amazing. You have done half my job for me already! I can already bill the client without drawing a single line. Hmm, that courtyard looks a bit dark. I wonder if it will pass the local authorities' sunlighting requirements?

    "No worries, Lets turn on the WMTS 3d layer. "

    Or switch to Cesium or extract from Google Earth if WMTS can't handle this. Maybe Bentley should provide or pre-package a low-res imodel for the UK?

    "Mstn here has inbuilt solar analysis. You can even check if the paving gradient is code-compliant with our special Display Styles..."

    etc etc etc

    half an hour later...

    "I wonder what the house you just modeled in 3d looks like?"

    "I thought you would never ask. Mstn has great 3d camera and rendering tools... eye-level view from the street?"

    "Cool. That's great."

    "Let's render this. Mstn can access the long lat info automatically from the WMTS attachment. We will also get the shadowing from the neighbours via the imported OSM or OS CAD data."

    "Wow! How did you get all that context in all photomatched properly?"

    "It's all done automatically because we are operating within a correctly georeferenced environment from the get go. A big difference compared with the old CAD way of doing things."

Reply
  • I can see this being a great feature for demo jocks if a seed file with a WMTS attachment is included in base install / dataset.

    "What are you working on?"

    "Oh, a small site on the Old Kent Rd. No. 122"

    Generate and open seed... zoom to OKR.

    Is there a Google Map-style search tool? If not, demo jock will need to fire up web browser first and copy the coordinates.

    "... this one?"

    "Yea. Hmmm I didn't notice that extension next door"

    "No worries, my Bentley WMTS attachment includes cadaster, Ordinance Surey CAD info as well as links to the local planning authority's applications map. Let's overlay that"

    "Yea, not on there. Permitted development waiver? I wonder how they built that over the drains in the backyard?"

    "No probs. Let's overlay the utilities companies plans. BTW, we can copy all of this through into our dgn here when we are done being nosy"

    "Amazing. You have done half my job for me already! I can already bill the client without drawing a single line. Hmm, that courtyard looks a bit dark. I wonder if it will pass the local authorities' sunlighting requirements?

    "No worries, Lets turn on the WMTS 3d layer. "

    Or switch to Cesium or extract from Google Earth if WMTS can't handle this. Maybe Bentley should provide or pre-package a low-res imodel for the UK?

    "Mstn here has inbuilt solar analysis. You can even check if the paving gradient is code-compliant with our special Display Styles..."

    etc etc etc

    half an hour later...

    "I wonder what the house you just modeled in 3d looks like?"

    "I thought you would never ask. Mstn has great 3d camera and rendering tools... eye-level view from the street?"

    "Cool. That's great."

    "Let's render this. Mstn can access the long lat info automatically from the WMTS attachment. We will also get the shadowing from the neighbours via the imported OSM or OS CAD data."

    "Wow! How did you get all that context in all photomatched properly?"

    "It's all done automatically because we are operating within a correctly georeferenced environment from the get go. A big difference compared with the old CAD way of doing things."

Children
No Data