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

Tue Dec 19 20:48:21 EST 2006

> _Bounds = XML snippet:  "<Bounds SRS="EPSG:4326" west="-87.74" south="43.68" east="-87.69" north="43.815"/>".   Could be multiple for WMS.  WFS, hmm?

Yes, same for WFS.

Note that _Bounds, in both cases, is “pseudo-XML” since the schema won’t allow nested XML within the value (that is, no complex properties.)  Consequently, the “<” and “>” characters are escaped as &lt; and &gt;.  In general, if the first non-whitespace characters in the value are “&lt;” and the last non-whitespace characters are “&gt;” you should “unescape” the contents of the value, expanding the entities found.  (The check guards against the eventuality that the schema will someday allow nested XML elements, in which case the string will begin with “<” and end with “>” and should not be unescaped.)

(A bit more complex than using CDATA, but it is what it is (namely, stop-gap). :-)

Also note that <Bounds/> uses attributes west, south, east, north, and these need to be mapped to the attributes required by each respective WMS / WFS version’s bounding box elements.  For most cases, there’s a 1:1 mapping, but some (very few) SRSs define a transposed x and y, so those have to be handled differently.

  _____  

From: Tom Fukushima 
Sent: Tuesday, December 19, 2006 5:14 PM
To: dev at mapguide.osgeo.org
Subject: RE: [mapguide-dev] PHP pages for describing a feature source RFC

Yes, the Metadata>Simple>Property contains the data.  Off the top of my head I'm not sure what all the names and values can be for WMS and WFS, but here's a start:

_IsPublished = {"1", "0"} 1 for true and 0 for false
_Title = arbitrary string
_Abstract = arbitrary string
_Keywords = arbitrary string
_PrimarySRS = arbitrary string
_Bounds = XML snippet:  "<Bounds SRS="EPSG:4326" west="-87.74" south="43.68" east="-87.69" north="43.815"/>".   Could be multiple for WMS.  WFS, hmm?
_OtherSRS = for WMS only?
_ExtendedMetadata  - for WMS only?
_Queryable - for WMS only (i.e., only applies to LayerDefinitions)
_Opaque - for WMS only (i.e., only applies to LayerDefinitions)

Note that the PHP pages from this RFC work against feature sources, so you would be able to get WFS metadata.  Layer definitions have WMS metadata.

Tom 

  _____  

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

Lol.  OK.

I've got an example raster configuration document to play with; not sure if it's common to both raster providers though.  It would probably be useful to support the GDAL provider :)

Are the free form strings stored in the metadata-simple element at least?  If so, I can parse it pretty easily.  I have to set one of these up to play around with it.

Jason

  _____  

From: Tom Fukushima [mailto:tom.fukushima at autodesk.com] 
Sent: Tuesday, December 19, 2006 10:51
To: dev at mapguide.osgeo.org
Subject: RE: [mapguide-dev] PHP pages for describing a feature source RFC

Thanks Burce, but unfortunately in this case those schemas will not help:

* the Raster Provider configuration document schema is not stored at that location.

* the WMS data stored in the headers is stored as "free form" strings so the corresponding schema (ResourceDocumentHeader-1.0.0.xsd) will not help.

Tom

  _____  

From: Bruce Dechant 
Sent: Tuesday, December 19, 2006 11:30 AM
To: dev at mapguide.osgeo.org
Subject: RE: [mapguide-dev] PHP pages for describing a feature source RFC

Jason,

The schemas used by MapGuide are available here in the source tree:

..\MgDev\OS\Common\Schema

Or here if you have installed MapGuide:

Open Source: C:\Program Files\MapGuideOpenSource\Server\Schema

Enterprise: C:\Program Files\Autodesk\MapGuideEnterprise2007\Server\Schema

Thanks,

Bruce

  _____  

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

Thanks Tom,

As long as this repository insight tool is built in an easily extensible manner, I won't have any problem voting +1 on the RFP as it stands.

It looks like adding these items is just a matter of doing an XSLT transform on an XML fragment.  If so, that might be something I can play around with in my "spare" time once the initial implementation is in place.  I'll have to pester people for the schemas unless they're already included somewhere in the source tree.

Hopefully as the project matures, we will start getting these enhancement proposals into the RFP process earlier.  Perhaps we should also look at some level of abstraction for large features, so that implementation can be phased across several RFPs but tracked as a part of a set of related features?  This idea is already in the roadmap, but a bit more ad-hoc.

Jason

  _____  

From: Tom Fukushima
Sent: Tuesday, December 19, 2006 09:20
To: dev at mapguide.osgeo.org
Subject: RE: [mapguide-dev] PHP pages for describing a feature source RFC

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
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)
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
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)
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_describing_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/67eef094/attachment.html