Archive for the ‘Safe Software’ Category

Why the Platform Is Important

Thursday, September 17th, 2009

Sometimes we can miss how large marketplaces can be, and their importance to development new ecosystems and technologies. The iPhone app market gives a glimpse as to why a SaaS-based application platform is so important for future geospatial business growth.

While the iPhone article describes a consumer based platform (mobile phones) for applications, the concept for a geospatial application platform is similar. By providing a platform on which developers can “write their own visions” of products, more products are developed, tested, purchased, and discarded at a much higher frequency than previous enterprise development cycles. This increase in the velocity of the product development cycle will provide opportunities in the future beyond those previously seen in the traditional software business. It will also increase the risk of marginalization of current software packages.

Our mission has been to develop a means to bring platform technologies to the geospatial industry. We focused on content first, because most of the current value of geo-knowledge is “stored” in the content produced under professional services and consulting contracts. The geospatial content are also larger and has proprietary file issues that are not necessarily seen in the consumer web space, which add to the difficulties in providing a true application platform to the Spatial Data Infrastructure (SDI).

However, it became clear to us about 2 years ago that cracking the content index, search, customization, and delivery process required developing an application platform along with the content management platform. So we began the process of creating an application platform that is accessible through APIs, which we then used to build our content management platform. Furthermore,we sought a partnership with a vendor who could supply additional transforms and ETL functions (Safe Software), which we could expose via our SaaS offerings, to allow others to build their own applications. We have thus created a geospatial application platform that will allow others to rapidly create their own small, but very targeted applications. By providing this application platform at the same time as providing the content management and financial services, all on a scalable SaaS-based architecture, we are poised to create an ecosystem around developer-driven applications and content.

This application/content (de-)evolution from the traditional software vending models is happening all around us. It will come to the SDI, probably a little later than other consumer driven niches, but it is coming. We strive to be that platform that others use to make money, and in that process help change our world.

Scaling FME Engines on WeoGeo

Friday, June 19th, 2009

I presented the movie below as part of a presentation at the Safe Software FME User Conference. We had a great time and the Safe crew put on a marvelous show.

The movie shows WeoGeo scaling up to 64 Safe Software distributed FME Engines in the production of tile caches from a world-wide elevation database. The FME Workspace script was created by Dmitri Bagh, and processed on WeoGeo’s FME Constellation built on Amazon Web Services.

The scaling occurred automatically, spinning up FME Engine AMIs, and then shutting them down when the job queue was completed. This is one of our first examples of bringing scalable processing to difficult geospatial tasks.

Examples of the tiles created by Dmitri’s script for Virtual Earth (Bing Maps for Enterprise) and Google Earth can be found here.

Panel 1 (upper left hand corner) refers to the total number of engines in the constellation processing job.

Panel 2 (upper right hand corner) refers to the total constellation utilization percentage. The constellation is polled and when the utilization exceeds the pre-set threshold (50% in this example), it increases (doubles here) the number of engines until it reaches the pre-set maximum number of engines (64 here). The downward spikes occur when each new set of engines are added.

Panel 3 (lower left hand corner) is the average job processing time. There is an increase in velocity when the number of engines exceeds 16, which may be a function of increased overhead costs on the FME Core or bandwidth to the database.

Panel 4 (lower right hand corner) is the total number of jobs completed. 2000 jobs were submitted for this test. The job completion rate accelerates until the maximum number of engines are brought on-line.

Safe Software and WeoGeo Partnership

Friday, July 18th, 2008

The facts of this partnership are well covered by the press release and Directions Magazine’s coverage (see Adena Schutzberg’s article and podcast). I thought I would give a bit more of the why.

1) ETL is fundamental to the needs of our customer base.
2) Safe is the best at spatial ETL.
3) People trust Safe for ETL.
4) If you use CAD or GIS software, there is a good chance you use Safe Software.

For a marketplace to be successful, its players have to trust their interactions and delivery mechanisms. Safe operates on over 200 different file formats across multiple platforms. Bringing this type of technology to our users is critical to our success; bringing Safe to our customers is just good sense.

What does Safe get out of this? We give them the cloud for FME Server and provide their users with the path to the future of web infrastructure.

Together, we get to focus on our strengths and bring new tools to bear on our respective businesses.

I am excited about our opportunities and the impacts I believe we will have on the spatial industry.