New to Map Enterprise / Schema questions

Old Microstation 95 developer here . Our office is in the midst of upgrading from 95 to Map Enterprise/ Descartes. We're still very confused about Geospatial Admin / Schema. I'm less concerned with creating a schema and more concerned with how to use it. If were going to be attaching shapefiles as reference files when exactly does the schema work it's magic? When we attach the reference shapefiles there's nothing that says "Apply schema". 

Parents
  • You use the GSA to define the XFM schema to match that of the shape file (feature geometry type and properties). You then start Bentley Map with the XFM Workspace generated in the GSA. When you import the shapefile, you will now have a option to map the shape file feature set with one of the features defined in the XFM schema. You will also be able to map the feature set properties with the XFM schema feature set properties. Once you are happy with this ( test it first), then save the import definition out to a impx file so you can reuse it with a shapefile of the same feature set/properties.

    HTH

    Jerry

     

  • Jim's colleague here, also a new Bentley Map user.  Some more questions on that front..

    1) To work with the XFM Workspace, do you need to launch it from GSA each time, or is there a way to do this from Bentley Map directly?

    2) At what point in the import process do you get this option to map a shapefile (etc.) to one of the features defined in the XFM schema?  I tried this out - Bentley Map imports the shapefile, but there are no user prompts, nor does it look like the schema worked its magic (shapefile features should have been mapped to cells, etc.)  Not sure how this is supposed to happen.

  • Greetings Janice and James,

    First let me start by saying that importing or reference attaching a SHP file into a Bentley Map session does not require that an XFM workspace be active. Using the Interoperability application you may find that you can apply the desired element symbology such as color, weight, style and cell names that may be sufficient. In addition you can 1) save the Import settings to an .impx file for reuse at a later time or 2) attach the .impx file as a reference file. Please see this section of the Bentley Map help for more information.

    Next please be aware that the Import process of the Interoperability application has a command line interface (CLI) that can be used to automate the import process and detine symbologies as well. Please see this section of the Bentley Map help for more information.

    If you wish to apply Property Based Symbology (PBA) rules to incoming feature instances then an XFM workspace generated using the Bentley Geospatial Administrator will be required. During import you can map incoming feature classes and business properties as you originally questioned. To accomplish the mapping, first select the feature class such as...

    ...then use the "General > Mapped Name" setting to select the target feature class from the active XFM schema. To optionally map the business properties, first select the feature class and right-click select the "Show Properties > Ungrouped" as shown here...

    ...then select the business property and use the "General > Mapped Name" setting to select the target business property as seen here:

    Finally to start any XFM workspace, running from the Bentley Geospatial Administrator is not required. You can use the "Create Shortcut" command in the Bentley Geospatial Administrator to create a Windows program shortcut with the required ustation.exe command line. If running Bentley Map in a layered MicroStation installation (as opposed to standalone edition) a command line such as the following starts the geo example designer workspace:

    ustation.exe -wugeo_example_designer

    You can also simply choose the user workspace in the MicroStation Manager file open dialog as shown here:

    I hope this helps somewhat, if not let us know and I'm sure someone will be able to further assist.

     

    Regards,

    Jeff Bielefeld [Bentley]



  • Jeff and Jerry, thanks for the tips.  Some on-site training (held a few weeks ago) also helped.  Fun bonus fact that we found: you can dynamically load the schema in Bentley Map via the CLI:

    ggcaches reload all override

  • Yes, for now that may work. In the class I do not recommend using this as a regularly. There has been discussions of removing this since at times  it is not reliable.

    Jerry

     

  • Good to know.  Is there another (recommended) way for dynamically re-loading the schema?  It's a huge pain to have to re-start Bentley Map each time we make a tweak to the schema.  Thanks.

  • Yes, there is a method to the madness.

    I would recommend.

    1. Make sure all your Microstation resources are well defined ( cell library, dgnlibs, seed files, GCS).
    2. Create any needed user workspaces.
    3. Define the relational database connection ( if needed).
    4. Make sure you have defined the feature schemas ( geometry and attributes, along with any annotation sub-features).
    5. Define the Categories, if needed.
    6. Define the domains , if needed.
    7. Review what is needed for PBS. Setup any criteria.
    8. Define the symbology keys.
    9. If you have annotation, define the PBA
    10. Set up the placement metadata
    11. Set up the GUI ( pulldowns, command menu, etc.)

    Always remember, that yo do not need to "Export"  all workspaces and metadata all the time. You can export the feature meta data separate from the workspaces, etc.

     

Reply
  • Yes, there is a method to the madness.

    I would recommend.

    1. Make sure all your Microstation resources are well defined ( cell library, dgnlibs, seed files, GCS).
    2. Create any needed user workspaces.
    3. Define the relational database connection ( if needed).
    4. Make sure you have defined the feature schemas ( geometry and attributes, along with any annotation sub-features).
    5. Define the Categories, if needed.
    6. Define the domains , if needed.
    7. Review what is needed for PBS. Setup any criteria.
    8. Define the symbology keys.
    9. If you have annotation, define the PBA
    10. Set up the placement metadata
    11. Set up the GUI ( pulldowns, command menu, etc.)

    Always remember, that yo do not need to "Export"  all workspaces and metadata all the time. You can export the feature meta data separate from the workspaces, etc.

     

Children