Let's see if I can take another hack at this. Mapguide was developed as a web-enabled map reader tool (with limited redlining) not as a full-blown map editing tool. ARCGis is a map editing tool.
Mapguide OS is free (MGE costs for support). ARCGis costs a significant amount of money for many users. Mapguide consists of basically 3 software pieces/technologies that you need to be aware of. 1) Mapguide. 2) FDO. 3) Datastorage (either database or file-based) Each of the software pieces will have to accommodate versioning in order for it to work. As a side note, ESRI's ARCGis does NOT do versioning on it's own. It relies on Oracle (which has versioning builtin). The challenge is: Mapguide has no concept of what you are trying to do. You would need to develop, write and test from scratch. I don't think anybody has done this. (someone please correct me if I am wrong) FDO **MIGHT** understand it if the FDO provider was written to support it. The only two databases that I'm aware of that support true versioning is Oracle and Smallworld's VMDS. Both are expensive. Smallworld is not really an option here, since you must use Mapguide Enterprise in order to have the FDO provider for it. So that leaves you with Oracle. I believe that Autodesk's proprietary Oracle FDO provider may have versioning, you will be legally required to purchase and use Mapguide Enterprise though. I don't think King Oracle has versioning built-in (Haris can you confirm/deny). So where are we? If you are wanting true versioning of data, I suspect you are wanting to use Mapguide as an editing tool to avoid buying licenses for each user. It was not designed to do that. I strongly suggest that you use a tool truly designed for editing data. If you are wanting to see a history of data changes, copy each day/week/month data to a new dataset and let the user switch between datasets. This is a matter of writing code to allow the user to change the base map or to allow the user to switch a layer. This would not be generic code for Mapguide, it would be specific to your application. You will need to write this, there are some people on here that can help with specific questions relating to this. If you are simply wanting the users to see redlines or not, than make sure you add them to a separate layer and allow the user them off and on at will. Thanks, Martin -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ivan Milicevic Sent: Tuesday, June 16, 2009 9:56 AM To: MapGuide Users Mail List Subject: RE: [mapguide-users] Map Versioning Martin Morrison replyed on this topic few days ago. Why do you repost it again? -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of sathishpsk9 Sent: Tuesday, June 16, 2009 1:45 PM To: [email protected] Subject: [mapguide-users] Map Versioning Hi all, I need to implement map versiong concept...any body here has ever worked on this before ? Can i get any help or even suggestions ? Last night i gone through the white paper of ARCGIS .. Versioning , i understood that it is more of database thing than programming .......Can anybody throw some light on this concept? Thanks & Regards, Satish -- View this message in context: http://n2.nabble.com/Map-Versioning-tp3085824p3085824.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
