[mapguide-users] Commercial vs. Open Source Functionality

Wang, Weili wwang at road-inc.com
Thu Apr 20 18:50:01 EDT 2006


Do you know if Commercial and Open Source offer forward geocoding
function? If yes, are there any limitations? How many countries does it
currently support?

 

Thanks,

 

Weili Wang

@Road, Inc.

 

________________________________

From: Robert Bray [mailto:robert.bray at autodesk.com] 
Sent: Thursday, March 23, 2006 1:05 PM
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] Commercial vs. Open Source Functionality

 

Studio Lite will most likely only support a fixed default layout. Once
it generates the layout you could edit it by modifying the XML. Time and
resources is the major constraint on this.

 

I could make them available for both Windows and Red Hat 3. On Linux the
providers are .so libraries.

 

Bob

 

________________________________

From: Jason Birch [mailto:Jason.Birch at nanaimo.ca] 
Sent: Thursday, March 23, 2006 2:00 PM
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] Commercial vs. Open Source Functionality

 

Will Studio Lite not be supporting the creation of layouts?

 

I think that making a binary distribution of the FDO providers available
would be a great idea.  Would you be able to support both Linux and
Windows with this (are they loadable modules in Linux?)

 

Jason

 

________________________________

From: Robert Bray [mailto:robert.bray at autodesk.com] 
Sent: Thursday, March 23, 2006 12:51
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] Commercial vs. Open Source Functionality

Some more answers...

 

1. The initial Studio Lite will be a subset, with support for creating
SDF and SHP data sources, layers, and maps. It's all just an HTML based
web application though so pretty easy for someone in the open source
domain to extend.

 

2. That's the plan. Studio Lite should be available sometime in the
spring and Studio does not expire until October 1.

 

3. The Open Source effort behind FDO is taking longer than we would
like. In the interim would folks on this list mind getting binaries for
these so that you could at least make use of them?

 

I can't comment on pricing at the moment because it is not finalized,
but I can tell you that it will be sold on a subscription basis. The one
other benefit to going commercial besides Oracle, SQL Server, and our
OEM coordinate system library is the availability of product support. 

 

Bob

 

________________________________

From: Buscher, Shane [mailto:Shane.Buscher at nngco.com] 
Sent: Thursday, March 23, 2006 12:27 PM
To: users at mapguide.osgeo.org
Subject: [mapguide-users] Commercial vs. Open Source Functionality

 

I appreciate everyone's response and am glad that some input from
Autodesk was received.  I am especially interested in pursuing the use
of this product because I see it solving many of our technical needs.  I
know that AutoDesk needs to make money off of this somehow since they
are embracing open source instead of competing against it.  So kudos to
Autodesk and the OS community for partnering on this endeavor.  I think
ESRI is losing serious ground with the advent of Google Maps, and now
MapGuide.  

A majority of the answers were provided, although it generated a couple
more:  

1) Will Studio Lite support everything it currently has available (or
supposed to have available)?  From a development end I need to know
whether you will be able to make all the data source connections (wms,
sql server, sde, etc...) with studio lite, for example.  

2) Will Studio Lite be available before Studio Preview expires, avoiding
a gap in time where OS developers have no authoring tool?

3) Are there any tentative release dates for some of the OS
functionality?  Also, any pricing being made available for the
commercial products?  

Thanks, 

Shane 

Content-Type: multipart/alternative;
        boundary="----_=_NextPart_001_01C64EA2.165BC440"
Date: Thu, 23 Mar 2006 09:49:09 -0800
From: Robert Bray <robert.bray at autodesk.com>
Subject: [mapguide-users] Commercial vs. Open Source Functionality

Thanks Jason good answers. Let me just confirm (with my Autodesk hat
on). When we launched mapguide.osgeo.org we moved all of the core source
code for MapGuide into open source (you can see our daily development by
subscribing to the commits e-mail list). Both the open source and
commercial versions of the product are built from this one code base. We
actually deleted our internal source tree, so any changes to open source
will appear in commercial and vice versa. Now that said, we are a
business and need to make money in order to keep producing software. So
the commercial version will have additional functionality, but these
will be more like add-ons that come with the commercial distribution
(the core code will be the same).



1. Studio is a commercial product. There is an open source web-based
variation in the works that we plan to have available later this spring.
It will not be as functional as the commercial version, but it will be a
full open source project.



2. The Open Source release will eventually contain providers for SDF,
SHP, ArcSDE, MySQL, ODBC, WMS, and WFS. As Jason points out, Frank W is
working on a Raster provider based on GDAL and we would really like to
get a PostGIS provider developed. These same providers (with the
exception of GDAL) are shipping with the upcoming release of Autodesk
Map. Getting them ready for that release has taken priority over getting
them ready for open source. Again we are a business and need to fund all
of this somehow.



As for investment, we have put over two years of development into this
product. We have big plans for it and absolutely no intention of
abandoning it.



Bob



  _____ 

From: Jason Birch [mailto:Jason.Birch at nanaimo.ca
<mailto:Jason.Birch at nanaimo.ca> ]
Sent: Thursday, March 23, 2006 10:05 AM
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] Commercial vs. Open Source Functionality



Your questions are shared by many.  This is just my interpretation, but
the information that Autodesk has revealed so far indicates that:



1. Studio will be strictly commercial (it contains AutoCAD components)
but Autodesk will be creating an open source "Studio Lite" application
for authoring maps.



2. ArcSDE and WMS providers will be in the Open Source edition, as will
ODBC which you can use to access aspatial data in SQL Server.  The
Essential FDO guide provides more information on this:
https://fdo.osgeo.org/docs/FET_TheEssentialFDO.pdf
<https://fdo.osgeo.org/docs/FET_TheEssentialFDO.pdf>   Currently the
providers not slated for OS release are Oracle, SQL Server (spatial) and
Raster.  This last one is a bit of a sticking point, but I believe that
Frank W is working on a GDAL Raster provider.



3. The OS version of the MapGuide code is the only version.  The
Enterprise package that Autodesk is selling will of course have
additional applications and plugins provided with it, but the entire
community will benefit from enhancements to the core, which is on its
own pretty impressive.  As a commercial entity, Autodesk is in this to
make money, and will be doing so with a combination of services and
software sales, similar to the Red Hat model.



Jason



  _____ 

From: Buscher, Shane [mailto:Shane.Buscher at nngco.com
<mailto:Shane.Buscher at nngco.com> ]
Sent: Thursday, March 23, 2006 05:45
To: users at mapguide.osgeo.org
Subject: [mapguide-users] Commercial vs. Open Source Functionality

All right, I'm a little frustrated at this point trying to figure out
the current direction of MapGuide OS and MapGuide Commercial.  I'm
trying to choose between several competing technologies in the web
mapping arena, including ArcIMS, MapGuide OS, MapGuide Commercial, and
MapServer. 

1.  Is the MapGuide Studio product going to become strictly a commercial
product?  I see it expires in October.  If so, what authoring tool is
going to be made available for the OS users, if any?

2. There's a lot of vaporware advertising going on, especially in the
data provider category.  I have SQL Server,  ArcSDE, and WMS consumption
requirements.  These are documented as being supported, but you quickly
realize they are not post-install.  Are these functionalities only going
to be made available in the Commercial product?  This is what it seems.

What is the general direction for both OS and Commercial?  Are they
going to be one in the same, with only support being the difference
between the two?  Or, will Autodesk just add functionality independently
of the OS project, leaving the open source community to catch up?

Maybe this is not the right forum to ask these questions, but I don't
know where else to ask.  It's important to know the direction of these
products, as I'm looking for a long term solution.

Thanks in advance.

Shane Buscher
GIS/Compliance Systems
Northern Natural Gas
402.398.7841

 

Shane Buscher 
GIS/Compliance Systems 
Northern Natural Gas 
402.398.7841 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-users/attachments/20060420/93769453/attachment.html


More information about the Mapguide-users mailing list