Geo Web Publisher, seems easier

Reviewing what is now Geoweb Publisher V8i, it is well known that this product has had Muuuucha Evolution, although the logic remains, there is a great change between what was a primitive tool for geo-engineers to publish their data in vector and what is now a proposal intended for geospatial purposes.

I have the V8i version, I plan to do a review but before, I take the opportunity to talk about what the previous versions were so as not to make the article of comparison so heavy and to remember the weaknesses they had.

Publisher - GeoWeb Publisher

Initially, Publisher was a geofundada difficult to implement, since it occupied a lot of knowing the guts of the workspace of Microstation and Geographics legacy. Geoweb publisherI had no wizard, no template icons, everything had to be built on foot. For 2004 was released Geoweb Publisher that already included a half wizard for the creation of pages with basic frames and for everything that had been cibstryudi with the Publisher (with the nails) was an offense that did not compensate the improvements. Apart from that, we had to invest in adapting the changes.


Geoweb publisher 3 When Geoweb Publisher arrived, Bentley stopped stubbornly with the Java applet, which had arrived with Microstation J. A Bentley own ActiveX called vpr emerged, as an acronym for what could be done with the: view, print and redline.

The service in the form of images was not a problem, the problem was always the vector data viewer, even if the data was served via IIS, if the initial version required the installation of a more archaic than specific Java engine (JRE) in the implementation Of the AcitveX was shut down to run only with Internet Explorer, and it was a drag to make it run for the first time, if you had a slow connection and little patience (or knowledge of what was going on in the liver of the data office)

Geoweb publisher 2 Everything the vpr did was a simple deployment of the dgn, but it was possible to serve almost anything that Geographics did, since in practice the Geoweb Publisher was itself a Geographics working from the server. So the magic was in the wonders that were done on Geographics, it could serve thematic, topological analysis, even quasi-vectorize online and this was added as a redline file associated with the original DNG. Sure, with the weaknesses before XM, you could not make transparencies unless they were geofumed with PictureScript Scenes (PSS), there were no dynamic symbols, and it was medium Depleted The management of scales, in practice the projection was not in a conventional way and when generating a theme on a new seed file was lost in space for a strange reason.

It required a deadly resource from the server, for being a Publisher serving routines running on Geographics at the user's request was understood. Although I admit that it was admirable, if we consider that 25,000 raised plots of vectorial form in seconds, and once they fell the refresh was not necessary at the level of zoom, only of pan outside of extent. Also the integration to Project Wise allowed control of workflow and association to external documents through the Web Explorer Lite.

Geoweb publisher Everything was done following the guidelines of the Geographics project, which could be in Oracle, SQL or Access. The display window read the four corners of the viewer, and did spatial analysis on the Index file and then loaded reference the dgn registered in that view (or through the map manager). This deployment was not a common image, since the msliks became hyperlinks of the objects that were linked to the database and in this way the associated table could be displayed.

Geoweb publisher Then, it allowed to configure the categories and attributes in a lateral tree to turn on or to turn off. The limited ones Query keys disguised buttons that executed common Microstation tasks: turn off or turn on layers (levels), Attachar Reference maps, images, shut down, run mdl routines, macros or vba applications.

Not standard

But there were no OGC standards, everything was a Bentley's own smoke, in their style. In the only two positions possible: the resignation that the interested party should wrap his shirt sleeves or the tranquility that is a hairy beard GNU, who previously worked at NASA and now is dedicated to doing GIS.


Geoweb publisher 3

I've taken a look at Geoweb Publisher v8i, and my compliments. I think that in this Bentley improves his point of view of the common user, who does not have Walter Mercado next to him to explain his daily letter. Make it easier, it could be, the truth is that it now has a more understandable logic in the flow from the built object to the service.

But rather than waiting for the implementation to be easy, the power of what it does looks interesting, like the evolution of the primitive dpr, now as idpr I find it magnificent in a spatial database concept (from the map) where it is possible Integrate dwg, dgn, xfm and even archaic shape files that are then served from a spatial database.

And then support OGC standards.

We'll see it in the next few days.

Leave an answer

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.