The move from Microstation Geographics to Bentley Map supposes an improvement of functionalities that that tool was doing, and of course, trying to gain strength by winning users of other solutions such as MapInfo, ArcView, and now a whole list of low-priced and open source programs .
Just now that I am working with a regular size municipality that wants to implement a GIS solution, they asked me to propose a brand. I explained that this does not work well, that they are the ones who must decide, so we sit down to size expectations, between what they want to do, the money they have and the sustainability alternatives available to their inevitable routine of changing people every four years for political issues.
After seeing different solutions, we conclude that they do not want open source or little-known software. As users coming from ArcView 3x and Microstation J, they were interested to know how easy it is to implement a spatial database, I showed them how the ESRI ArcCatalog worked, they asked basic questions about why ArcSDE was necessary and what was the difference between ArcIMS and GIS Server. When I started explaining the Bentley Map Geospatial Administrator they listened to me out of respect, but in the end, Traroscaron the eyes Average to Like Garfield and they told me in their hearts what others had told me before:
Could not it be more complicated?
To date, Geographics users have problems To migrate to Bentley Map, not only because of what it implies in the change Data or reconstruction of custom tools, but also because the Readme It is not enough and there are no guided tutorials that explain the order that should be followed. For example:
Understanding what is to be done in the Geospatial Administrator, in which user, how to compose domains, how to create forms to feed the dgn xml, is not so intuitive. Just understanding the relation of Criteria-Operation-Method-UI terms is difficult medium to the 3 of the dawn.
Not to mention the execution from the Map side, with the Command Manager and Map Manager.
What happens is that the user of Geographics hopes to find the buttons as it was before -Which were not many by the way-.
The Map Manager took what was the Display Manager, topological analysis is now called Overlay, and for this same place was the Buffer and thematic mapping. If that is not sought with a magnifying glass, anyone can think that Bentley Map does not have this type of function.
Then the Feature Manager was in the right side panel known as Command Manager, from where you can not turn off or turn on features but only create. There is no way to apply or remove attributes like that, nothing more ... in conclusion, difficult for the most experienced.
I must admit, that this feeling of bewilderment has not changed in several years, when they showed it to me for the first time before being called like that.
It was at the 2004 users' conference, when the potential of Xml FEature Markup (XFM), which was already running on Geographics 8.5. Later it was called Bentley Map, from XM 8.9, and they called it a legacy to all of the above. At this time, we were interested in its potential, but in the impression that it was still a crude tool, we decided to reconstruct routines that were done in Geographics.
The videos shown below were elaborated in 2005, from the development on . NET Visual Basic from Microstation that a boy of many desires made, for while Bentley integrated these functionalities in XM, of which I talked to you guys ago few days.
|From Geographics to xfm. Having a schema created, it was programmed to make a layer transfer, from the Geographics project mounted on Oracle, defined what features were wanted and built taking the data in xml on the same DNG. The intention was that the municipality had the data in the DNG, without complicating their lives with a database where there was barely any connectivity.|
|Export the cadastral layer. As in the previous case, maps of a municipality could be exported, the basic data that interested for the xfm layer went as xml to dgn, among them the cadastral key based on sectorization. With this, it was expected that they could do maintenance, and then centrally make a reconciliation of data that differed and that became maintenance transactions.|
|Attach maps of a municipality. This tool was to load from a fence, all the maps that coincided geographically with that geometry, all from the two layers created in the previous step. Similar to what the Map Manager used to do with what was registered in the Vicinity.|
|Turn off and on layers. The Map Manager brings this functionality, but by then we had no other source than Geographics with the Display Manager, but in this case with XFM layers.|
|Topological analysis. With this, what had been done was to reconstruct the functionalities of creation of topologies and analysis Which had Geographics. I could create layers of points, lines, polygons, and then make crosses between them gener |
I'm running an html report. Later it was integrated into the Map Manager, but I think never with that facility.
|Thematic. This now comes in the Map Manager, if Feature classes are created, but before Geographics brought it loose and as such was developed.|
|Custom thetics. This was from attributes of the Oracle database, even though they were not embedded in the XFM data. As in Geographics, he was allowed to create it as DNG.|
|Search by attributes. With this a search was made of some criteria, and colored when selected. It also allowed to send the report to html.|
|Socioeconomic survey. It happens that several municipalities had a socio-economic survey in addition to the cadastral record, what we did was that from the Oracle database, a button made the transfer of data to the xfm layer. Based on the theming criterion could place a different cell, taking advantage of what is called in the project "Criteria".|
|Transfer to the centroid. Also, as the municipality based on certain criteria, was placing a symbol different from the centroid, it was programmed that the socioeconomic survey data could be transferred to this centrolide. Of course, as the sheet that represented the survey was too big, the dialog should be left adjustable on both ends, to make the video was crazy for the screen size.|
|Avoiding the Geospatial Administrator. Understanding the operation is extremely complex, I told the programmer to remove the horrendous, so from the side of the map it was possible to create a new attribute, assign the type, symbology and even dialog box with properties. We also gave you the option to edit an already created feature and even apply changes to previously created objects. |
Great Smoke, this Bentley should implement it as it is literally a toothache Do it from there.
|Load data from Visual Fox. There was a system in the municipality called SIIM, which had the cadastral data under a methodology of massive appraisal and under a cadastral key nomenclature based on quadrants. Well, what we did was create a form that read the dbf data, but from the xfm map in Microstation.|
|Web publishing. Publication features were added using Geoweb Publisher, raising data on the fly from the layers available in xfm.|
All the above was done with Microstation VBA with an installer that left everything running, the XFM project and even Geo Web Publisher.
Because I'm not happy about this:
First, because there was no opportunity to systematize the process, just make the videos. We would gladly take it to the 2007 BE Awards, we sure got a nomination as it was the first development on XFM.
Then, as far as I know, only a couple of municipalities came to implement it, because government projects are sad after every 4 years.
Finally, because Bentley needs -in these 2008 versions- improve the ease of operation of Bentley Map, which to be a GIS tool -In my opinion-, is not ready for a person to buy the package, take the manual, seek help in the forums and implement a system.
In conclusion, the friends went for another solution, despite its costs.