Import WFS and map point features z value to a field value.

Hi,

Another question here. I have OGC WFS 'point' data that I am importing and would like to map points 'z' value to a property field. 
Can some one point me in the right direction?

Thanks,
Mike 

BM 08.11.09.107

Parents
  • Hello Mike,

    In the propety parameter options in the import dialog you can map the property Z to any property name you are using in your project. I hope I have understood correctly what you want to achieve. See image below where Z is mapped to Elevation

    Hope it helps
    Regards
    Carlos

     

     

     

     



  • Hi Carlos,

    In my case the feature properties don't list at the time of import. The source is a OGC WFS...


     

    Mike

  • Try to select the feature > mouse right-click > show properties > ungrouped. then all the properties should be visible



  • Thanks Carlos.

    I can see the properties now. However I'm still having trouble mapping the elements z value.

    In Bentley Map SS3 help...
    Interoporability > Importing GIS Data Types > Importing into a 3d file > Selecting a property for elevation

    It describes mapping the Feature properties to the elements elevation. I can't get this to work.

    In my case the listbox for 'Mapped Name' in both 'Property Parameters' and 'Feature Parameters' is empty.
    Is 'Mapped Name' something I need to define in Geospatial Administrator prior to import?

    Thanks again.
    Mike

  • The list won't be populated if the features are not registered prior in the GSA and thus this is the reason why there is nothing listed. Hence, in order to do so an XFM schema and workspace needs to be created.

    However you have the possibility in the same fields (the ones you highlighted in yellow) you are allowed to type in any feature name as well as the feature property name that you want to map.

    See example below where I specify the mapping to a new feature name (From Lots to East_City_Lots and the property LOTNUMBER to Lot_Number)



Reply
  • The list won't be populated if the features are not registered prior in the GSA and thus this is the reason why there is nothing listed. Hence, in order to do so an XFM schema and workspace needs to be created.

    However you have the possibility in the same fields (the ones you highlighted in yellow) you are allowed to type in any feature name as well as the feature property name that you want to map.

    See example below where I specify the mapping to a new feature name (From Lots to East_City_Lots and the property LOTNUMBER to Lot_Number)



Children
  • Hi Carlos,

    I think we might be miss understanding each other. What I want to do is to map the point elements 'z' value in a 3d dgn. And not simply map one features attribute to another. Apologies if my previous posts were not specific enough.

    This is described in the help  documentation...

    Interoporability > Importing GIS Data Types > Importing into a 3d file

    There is no mention in the documentation for a requirement to define the features prior in GSA. 
    I can't find anyway in GSA to specify the z value (not Attribute) of a feature. I'm beginning to think I need to write some vba.

    What are the circumstances in which the described steps in the help manual will work.. Is this limited to specific Import types?

    Thanks
    Mike



  • Mike,

    In answer to your question: What are the circumstances in which the described steps in the help manual will work.. Is this limited to specific Import types?

    The command currently only works that way for importing Shapefiles.  Multi-feature sources, such as WFS (Oracle, SQL Server) require some changes to the code to accommodate the import at the Feature-level, rather than the current file-level.  There is a Change Request on the books that is under evaluation to correct this limitation.

    One way you might be able to get around this would require an additional step; round-trip the data from WFS to DGN to SHP to DGN.  Or you could write your vba to produce the results you need.



  • Hi Dan,

    Thanks for the information. That is good to know.

    The documentation could be more specific as it doesn't mention this limitation. Hopefully though the limitation will be resolved.

    Regards,

    Mike