Since you have a need for permanent and private/shared resources then temporary 
SDF's are not a solution.

MG API does not contain any Schema creation API so you would need to use 
something like Autodesk Map to create the datastore/schema in the database. 
After that it's more of an insert/update/delete feature sequence of commands 
and security and possibly filters on the layers to access the data.

What may also add some complications would be if you use different coordinate 
systems. Unless the data is stored as LL84 it might be hard to work with 
multiple spatial contexts in 1 table. The table can support multiple feature 
types.

Dave

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of r0ss
Sent: Tuesday, April 22, 2008 2:16 PM
To: 'MapGuide Users Mail List'
Subject: RE: [mapguide-users] Creating mark ups / redlining using anything 
other than SDF

Dave,

To outline what we're trying to accomplish based on some business requirements:


1.       Users can create two types of redlines; private and public,  both of 
which are permanent and/or temporary.

2.       The creator of the redline can determine if it gets deleted.

3.       They may be quasi temporary in that they may only last a week or so, 
but not session temporary

4.       Multiple users can view and/or edit the public mark-ups only, add, 
update, delete items etc concurrently.

The private ones seem to be fine, although multiple users may be concurrently 
editing private redlines too. This all seems to go awry when multiple users 
concurrently edit public redlines that where created programmatically using the 
API feature service.

Regards

R0ss


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Wilson
Sent: April-22-08 1:13 PM
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] Creating mark ups / redlining using anything 
other than SDF

Are the markups permanent or temporary: this may have a big impact on the 
approach you can take? If temporary they should be created in the Session 
Repository which should at least avoid whatever may be causing corruption of 
the main repository. If users are creating their own markups do they need to 
share the same resource? Why can't they each have their own temporary session 
based SDF? This will probably avoid any corruption.

The fact that you are trying to delete them suggests they are somewhat 
temporary. If they were created based on the session id then when the session 
expires you might create a process to delete the expired ones. Just a thought.

Dave

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of r0ss
Sent: Tuesday, April 22, 2008 12:11 PM
To: 'MapGuide Users Mail List'
Subject: [mapguide-users] Creating mark ups / redlining using anything other 
than SDF
Importance: High

All,

We have encountered a critical flaw with MapGuide in particular the 
undocumented use of the SDF format to create multi user based red lines - the 
default samples all highlight this is the approach.

As an example, we created an application that allows users to each create, 
modify and display redlines from the same SDF file (as per the sample).  We 
were recently informed by Autodesk that the SDF format is not meant to serve as 
a mutli-user creation format (which is an undocumented feature by the way!).

During our testing when multiple users create redlines at the same time - the 
repository become corrupt and forces us restore the previous MapGuide package 
(does anyone know how to automate the deletion of SDF files in the repository 
without knowing the names of the repository names - i.e. the users create 
redlines and we do not know the repository names)

The big ask:
Does anyone have any experience creating redlines in anything other than SDF, 
notable SQL Server 2005, GML, KML, etc (we are not an Oracle or PostGIS shop) 
or any other work arounds we would greatly appreciated we are at a loss and in 
a time crunch.
Regards

R0ss

_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users

Reply via email to