[mapguide-dev] PHP pages for describing a feature source RFC

[Tom Fukushima]

Hi Jason,
 
These are good ideas.  Unfortunately, after some investigation, it looks
like these will require a little more effort than we have available
right now. The good news is that these things can be seemlessly added
later.  If anyone else wants to do this, I'm sure a MapGuide developer
can help with meta data storage formats, and an FDO developer could help
with the Raster config schema.
 
Tom

 
  _____  

From: Jason Birch [mailto:Jason.Birch at nanaimo.ca] 
Sent: Wednesday, December 13, 2006 11:32 AM
To: dev at mapguide.osgeo.org
Subject: RE: [mapguide-dev] PHP pages for describing a feature source
RFC


Honestly, I'm not sure about the technical details.  
 
Bob said something at AU about the WMS parameters being stored in the
metadata element of the resource header, but I could be a bit fuzzy on
that.  Basically, I'd like to be able to see:
 
- The WMS parameters for WMS feature sources
- The image catalog definition for Raster feature sources (such as those
converted from 6.5 RIC files)
 
Jason

  _____  

From: Rex Szeto (Intern) [mailto:Rex.Szeto at autodesk.com] 
Sent: Wednesday, December 13, 2006 10:27
To: dev at mapguide.osgeo.org
Subject: RE: [mapguide-dev] PHP pages for describing a feature source
RFC



Hi Jason,

 

Yes, the scripts for this will be in another directory with the same
level as the mapagent/* and mapadmin/*. I'll make changes on the RFC to
specify this.

 

As for the contents of the resource header, can you clarify as to what
you are looking for?

I performed a GetResourceHeader on a Raster feature source in the
mapagent and got back the information:

 

  <?xml version="1.0" encoding="utf-8" ?> 

- <ResourceDocumentHeader
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xsi:noNamespaceSchemaLocation="ResourceDocumentHeader-1.0.0.xsd">

  - <General>

      <IconName>FeatureSourceRasterAtil</IconName> 

    </General>

  - <Security
xsi:noNamespaceSchemaLocation="ResourceSecurity-1.0.0.xsd">

      <Inherited>true</Inherited> 

    </Security>

  </ResourceDocumentHeader>

 

Thanks,

Rex

 

  _____  

From: Jason Birch [mailto:Jason.Birch at nanaimo.ca] 
Sent: Tuesday, December 12, 2006 2:03 PM
To: dev at mapguide.osgeo.org
Subject: RE: [mapguide-dev] PHP pages for describing a feature source
RFC

 

Cool idea.  I really like the idea of doing this as a generic feature
that can be used by either Studio or Web Studio.

 

I'm a little at a loss on where these will fit in.  

 

- The php viewer won't always be installed

- The mapagent/*.(html|php) scripts will generally not be installed on
production machines

- The mapadmin/* scripts will typically be secured to the point where
accessing them from Studio or Web Studio may not be realistic.

 

Do we need a new location for generic server-side web scripts?

 

I would also like to be able to use these scripts to view the contents
of the resource header for the feature type, including any metadata
(resource metadata, not ISO or FGDC metadata).  This would help
understand feature types like Raster and WMS better.

 

Jason

 

  _____  

From: Rex Szeto (Intern) [mailto:Rex.Szeto at autodesk.com] 
Sent: Tuesday, December 12, 2006 12:30
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/20061219/1d747637/attachment.html