Changes between Version 9 and Version 10 of GoogleSoC2007


Ignore:
Timestamp:
Mar 6, 2007, 1:09:29 PM (17 years ago)
Author:
jbirch
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GoogleSoC2007

    v9 v10  
    1717=== !MapGuide Web 2.0 Enhancements ===
    1818
    19 [Mentor: Jason Birch (if nobody else volunteers)]
     19[Mentor: Jason Birch]
    2020
    21 While !MapGuide's support for enterprise standards (OGC), and KML is well established, there are several areas where we could take a leading edge stance.  These enhancements all around Web 2.0 data interchange techniques: Tile Map Service (TMS), GeoRSS, and REST-based feature retrieval.  These could be initially written as PHP scripts and then brought into the core code base if desired at a later point.
     21While !MapGuide's support for enterprise standards (OGC), and KML is well established, there are several areas where we could take a leading edge stance.  These enhancements all around Web 2.0 data interchange techniques: Tile Map Service (TMS), and GeoRSS.  These could be initially written as PHP scripts and then brought into the core code base if desired at a later point.
    2222
    2323==== TMS ====
    … …  
    3232
    3333This component of the project would involve the development of a PHP "gateway" script that allows the end user to configure the Geometry, Name, Description, and Modified Date from an existing feature source, and present this as a GeoRSS feed in any of Atom 1.0, RSS 1.0, and RSS 2.0 formats, leveraging the GeoRSS Simple and GML profiles.
    34 
    35 ==== REST-based feature retrieval ====
    36 
    37 [http://en.wikipedia.org/wiki/Representational_State_Transfer REST] is form of system architecture which defines unique URIs for each feature, and then applies methods against these URIs.  This is different from a typical GET query string, where the parameters are somewhat arbitrary, and make it impossible to distinguish which parameters define the feature, which define the operation, and which control the output type.
    38 
    39 This component of the project would involve the development of a PHP "gateway" script that allows the end user to define a REST-based feature retrieval system from !MapGuide resources.  A typical request might look something like this:
    40 
    41 GET !http://localhost:8008/mapguide/gateways/rest.php/parcels/231-232-534?accepts=application/vnd.google-earth.kml+xml
    42 
    43 or:
    44 
    45 GET !http://localhost:8008/mapguide/gateways/rest.php/parcels/231-232-534?representation=zoningmap&accepts=image/png
    46 
    47 In these cases, the user would have to configure how these requests are handled, and somehow publish the content-types and representations that are available.
    48 
    49 ''This component requires more input before submission.''