[mapguide-trac] #560: Consider adding a repository validator
MapGuide Open Source
trac_mapguide at osgeo.org
Mon Oct 27 06:28:53 EDT 2008
#560: Consider adding a repository validator
-------------------------+--------------------------------------------------
Reporter: ksgeograf | Owner: ksgeograf
Type: enhancement | Status: assigned
Priority: medium | Milestone:
Component: Maestro | Version:
Severity: major | Resolution:
Keywords: | External_id:
-------------------------+--------------------------------------------------
Comment (by ksgeograf):
This is the next feature I will work on in Maestro (Repo validator).
This is a potentially endless point, so I will try to keep a list of known
problems here. Feel free to add any detail that you wan't Maestro to
detect as either a warning or error.
* FeatureSource:
* Perform the "Test Connection"
* Perform a "Describe Schema"
* Perform a "Get Identitie Columns"
* Perform a random select.
* Layer
* Detect missing featuresource, class, geometry or columns.
* Detect no scale ranges (warning)
* Detect no items visible in a scale range.
* Detect scale ranges with gaps eg. [0-10[ [11-20[ (warning)
* Try sample rendering, re-test without filter, labels, links or
tooltips, to detect errors in these.
* Try sample rendering with default font and symbols.
* Map
* Detect that all layers exist, and their permissions are equvalent
to the map.
* Detect that spatial contexts for layers are within the maps.
* Warn if coordinate systems are not the same (performance penalty).
* Warn (error?) if raster layer is not in the same coordinate system.
* Perhaps check for visibility logic, ea. order should be: rasters,
polygon layers, lines, then points.
* Layout
* Check that the map exists.
* Check that the startup is within the map bounds.
* Fusion
* Same as layout.
--
Ticket URL: <http://trac.osgeo.org/mapguide/ticket/560#comment:3>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals
More information about the mapguide-trac
mailing list