Opened 17 years ago
Closed 15 years ago
#565 closed enhancement (fixed)
Add support for editing Xml config files on resources
Reported by: | ksgeograf | Owned by: | ksgeograf |
---|---|---|---|
Priority: | medium | Milestone: | |
Component: | Maestro | Version: | |
Severity: | major | Keywords: | |
Cc: | External ID: |
Description
- Comments from the original report
Many FDO providers have Xml files that override basic settings. It should be possible to edit these from MapStudio. The mime-type on the resource should indicate if the attached document is text/xml.
-
I like this one :)
Note that you can also detect configuration documents (as opposed to just resource data) by the presence of the ConfigurationDocument entity under the FeatureSource entity, which contains the name of the linked resource data to use for configuration.
<ConfigurationDocument>ConfigurationDocument</ConfigurationDocument>
Ideally, you'd be able to create specific editors for data sources with complex override schemas, like WMS:
http://trac.osgeo.org/fdo/wiki/FdoWmsNotes
You can find some more example schemas for WMS here:
http://trac.osgeo.org/fdo/browser/trunk/Providers/WMS/Src/UnitTest
There doesn't seem to be a consistant way of storing configuration schemas in the FDO repository so I guess the best approach would be to ask on the fdo-users or fdo- internals lists about where to look in the code for these overrides.
Change History (4)
comment:1 by , 16 years ago
Status: | new → assigned |
---|
comment:2 by , 16 years ago
Type: | defect → enhancement |
---|
comment:3 by , 16 years ago
That depends on what you mean. CS overrides is in the feature Xml and supported. I'm not sure what can be done with WMS besides coordinate system override.
This issue is here to remind me to implement a feature that allows a user to open the config file in the internal editor, edit it, and save it. This will ease the current method where the file must be downloaded to disk, edited externally and then uploaded again.
If you mean something else, please do create a new issue.
Note, this is partially implemented (for Rasters, is this the same mechanism used for joins, CS overrides?) but not yet for WMS. Should I create a separate item for WMS overrides and close this?