[mapguide-dev] PHP pages for describing a feature source RFC
Rex Szeto (Intern)
Rex.Szeto at autodesk.com
Tue Dec 12 19:42:59 EST 2006
Yes, I agree. A warning for the user would be appropriate when working
with large data sets.
I will make changes so a warning would pop up if the number of features
is too large (once it goes over a maximum value).
Thanks for the idea.
Rex
_____
From: Andy Morsell [mailto:amorsell at spatialgis.com]
Sent: Tuesday, December 12, 2006 5:09 PM
To: dev at mapguide.osgeo.org
Subject: RE: [mapguide-dev] PHP pages for describing a feature source
RFC
OK. That's better functionality then. Unfortunately, Studio doesn't
work that way. If you last viewed a layer in split or preview mode,
then open a newly created default layer, it will attempt to draw the
extents in the preview window without prompting the user. Anyway, it
would still be nice if you could warn users somehow before they try to
display large feature sources - but would not be a critical piece of
functionality at this point.
Andy
_____
From: Rex Szeto (Intern) [mailto:Rex.Szeto at autodesk.com]
Sent: Tuesday, December 12, 2006 2:05 PM
To: dev at mapguide.osgeo.org
Subject: RE: [mapguide-dev] PHP pages for describing a feature source
RFC
The graphical display only shows the geometric properties for the given
feature class after the user selects the "show details" link beside the
geometric property. In a way, this is similar to how you described the
default view to be set up in Edit mode for Studio. It does not force the
user to view the map unless he/she chooses to.
Thanks,
Rex
_____
From: Andy Morsell [mailto:amorsell at spatialgis.com]
Sent: Tuesday, December 12, 2006 1:56 PM
To: dev at mapguide.osgeo.org
Subject: RE: [mapguide-dev] PHP pages for describing a feature source
RFC
I like the overall functionality and think that it will be very useful.
One thing to watch out for, however, is graphically displaying the
extents of a large feature source. This is not always desirable since
it can cause a strain on MGOS server and take excessively long to return
the map view. The same problem already exists in Studio when you view a
default layer definition in split or preview mode (one of the reasons I
would like to have the ability in Studio to specify that my default view
is always Edit mode). So, perhaps you could query the feature source to
determine the number of features and then tell the user "This feature
source is very large, are you sure you want to preview it?"
Andy Morsell, P.E.
Spatial Integrators, Inc.
http://www.SpatialGIS.com
_____
From: Rex Szeto (Intern) [mailto:Rex.Szeto at autodesk.com]
Sent: Tuesday, December 12, 2006 12:30 PM
To: dev at mapguide.osgeo.org
Subject: [mapguide-dev] PHP pages for describing a feature source RFC
I have just posted a draft of the RFC for "PHP pages for describing a
feature source" in MGOS to the following location:
http://wiki.osgeo.org/index.php/MapGuide_RFC_8_-_PHP_pages_for_describin
g_a_feature_source
Please take a look, and post any feedback to this group.
Thanks,
Rex Szeto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-internals/attachments/20061212/49e3ea9d/attachment.html
More information about the Mapguide-internals
mailing list