[mapguide-internals]MapGuideRFC 14- CartographicStylizationEngine(maybe this timeI'll get it right)

Paul Spencer pspencer at dmsolutions.ca
Mon Feb 5 06:09:47 EST 2007


Traian, good points.  I hadn't considered that you could store a  
raster image in a PNG and then reference that symbol in other  
symbols.  This makes my point a bit moot I think.  I'm back on board  
with Carsten and the #1 option :)

Jason raises an interesting point about SLD.  I don't think SLD has  
nearly the expressive power of the FGDC spec, but it would be  
important to look forward to see how SLD support could be implemented  
on top of this.

Cheers

Paul

On 5-Feb-07, at 12:32 AM, Traian Stanev wrote:

>
> Here's my take. To clarify Carsten's item #1, it means to store the  
> image attached to the SymbolDefinition resource using Set/ 
> GetResouceData.
>
> I don't see much value of having a raster that's a component of a  
> SymbolDefinition be a top level resource like Paul is proposing.  
> Here is why --
> (1) you should be sharing symbols, not their components
> (2) you can have a symbol that just consists of one raster -- de  
> facto giving you the equivalent of a raster resource
> (3) a raster used in a symbol will be tiny, so it can be copied  
> easily and without much overhead if you really need to use it in  
> two places and don't want to share a SymbolDefinition.
> (4) if you are going to stick rasters in the old symbol library,  
> might as well use the new one -- see item (2) on how to do that :-)
>
>
> Traian
>
>
> 	-----Original Message-----
> 	From: mapguide-internals-bounces at lists.osgeo.org on behalf of  
> Carsten Hess
> 	Sent: Sun 2/4/2007 10:56 PM
> 	To: MapGuide Internals Mail List; MapGuide Internals Mail List
> 	Cc:
> 	Subject: RE: [mapguide-internals]MapGuideRFC 14-  
> CartographicStylizationEngine(maybe this timeI'll get it right)
> 	
> 	
>
> 	Yeah I was looking at the same thing and don't like it. How about  
> we create a new resource type called "RasterLibrary"?
> 	
> 	Cheers,
> 	  Carsten
> 	
> 	        -----Original Message-----
> 	        From: mapguide-internals-bounces at lists.osgeo.org on behalf  
> of Robert Bray
> 	        Sent: Sun 2/4/2007 10:11 PM
> 	        To: MapGuide Internals Mail List
> 	        Cc:
> 	        Subject: Re: [mapguide-internals] MapGuideRFC 14-  
> CartographicStylizationEngine(maybe this time I'll get it right)
> 	
> 	
> 	
> 	        Guys,
> 	
> 	        Here is the definition of our existing SymbolLibrary:
> 	
> 	        <?xml version="1.0" encoding="UTF-8"?>
> 	        <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
> 	        elementFormDefault="qualified"  
> attributeFormDefault="unqualified">
> 	           <xs:element name="SymbolLibrary"  
> type="SymbolLibraryType"/>
> 	           <xs:complexType name="SymbolLibraryType">
> 	             <xs:sequence>
> 	               <xs:element name="Description" type="xs:string"  
> minOccurs="0"/>
> 	               <xs:element name="Symbol" type="SymbolType"  
> minOccurs="0"
> 	        maxOccurs="unbounded"/>
> 	             </xs:sequence>
> 	           </xs:complexType>
> 	           <xs:complexType name="SymbolType">
> 	             <xs:sequence>
> 	               <xs:element name="Name" type="xs:string"/>
> 	               <xs:element name="Resource" type="xs:string"/>
> 	             </xs:sequence>
> 	           </xs:complexType>
> 	        </xs:schema>
> 	
> 	        In looking at this I have two reservations. First is the  
> naming which is
> 	        not great for re-purposing it (but I can live with it if  
> everyone else
> 	        can). Second we might need to add I type element or  
> attribute to
> 	        SymbolType to indicate if the binary data is a DWF, Image,  
> or some other
> 	        type of future thing.
> 	
> 	        Bob
> 	
> 	
> 	
> 	        Paul Spencer wrote:
> 	        > Carsten,
> 	        >
> 	        > I was thinking of just the raster.  I agree with each  
> symbol being its
> 	        > own resource.  I would just like to have a place to put  
> the raster
> 	        > images in the repository rather than an external  
> reference, and would
> 	        > prefer to have the raster images not be with the symbol  
> so they can be
> 	        > potentially shared between symbols.
> 	        >
> 	        > Cheers
> 	        >
> 	        > Paul
> 	        >
> 	        > On 4-Feb-07, at 7:38 PM, Carsten Hess wrote:
> 	        >
> 	        >> Bob, Paul,
> 	        >>
> 	        >> not sure I follow. Do you want to put the symbol plus all
> 	        >> depdendencies into the symbol library and hence build a  
> symbol library
> 	        >> or do you want to put just the raster into the symbol  
> library?
> 	        >>
> 	        >> I always thought we could make a directory in the  
> resource repository
> 	        >> to be a "symbol library" but each symbol be its own  
> resource. The
> 	        >> reason I liked it is that I can put metadata against it  
> and ultimately
> 	        >> search for the symbol (if we get around to implementing  
> that).
> 	        >>
> 	        >> Think for  example about the FGDC library, it has  
> several hundred
> 	        >> symbols, searching would be useful I think.
> 	        >>
> 	        >> Cheers,
> 	        >>   Carsten
> 	        >>
> 	        >>     -----Original Message-----
> 	        >>     From: mapguide-internals-bounces at lists.osgeo.org on  
> behalf of
> 	        >> Robert Bray
> 	        >>     Sent: Sun 2/4/2007 5:28 PM
> 	        >>     To: MapGuide Internals Mail List
> 	        >>     Cc:
> 	        >>     Subject: Re: [mapguide-internals] MapGuide RFC 14-
> 	        >> CartographicStylizationEngine (maybe this time I'll get  
> it right)
> 	        >>
> 	        >>
> 	        >>
> 	        >>     Carsten,
> 	        >>
> 	        >>     I read your choice (1) as storing it with the  
> SimpleSymbolDefinition
> 	        >>     using Get/SetResourceData. I think Paul is  
> referring to storing the
> 	        >>     images in our existing SymbolLibrary resource,  
> which stores a
> 	        >> collection
> 	        >>     of DWF symbols in a single resource.
> 	        >>
> 	        >>     Bob
> 	        >>
> 	        >>     Carsten Hess wrote:
> 	        >>     > Paul,
> 	        >>     >
> 	        >>     > that is the same as my choice 1) think. We could  
> do that. Like I
> 	        >> said though we have to figure out to have multiple  
> raster in there and
> 	        >> how to refer to them as resource id.
> 	        >>
> 	        >>     >
> 	        >>     > Cheers,
> 	        >>     >   Carsten
> 	        >>     >
> 	        >>     >       -----Original Message-----
> 	        >>     >       From: mapguide-internals- 
> bounces at lists.osgeo.org on behalf
> 	        >> of Paul Spencer (External)
> 	        >>     >       Sent: Sun 2/4/2007 5:03 PM
> 	        >>     >       To: MapGuide Internals Mail List
> 	        >>     >       Cc:
> 	        >>     >       Subject: Re: [mapguide-internals] MapGuide  
> RFC 14 -
> 	        >> CartographicStylizationEngine (maybe this time I'll get  
> it right)
> 	        >>
> 	        >>     >
> 	        >>     >
> 	        >>     >
> 	        >>     >       Carsten,
> 	        >>     >
> 	        >>     >       Why can you not reference it inside the  
> existing
> 	        >> SymbolLibrary object
> 	        >>     >       in the repository?  This mechanism is  
> already used for
> 	        >> point symbols
> 	        >>     >       and seems to fit semantically for this  
> purpose too.  I
> 	        >> believe there
> 	        >>     >       is already a way to do this using  
> MarkSymbolType or
> 	        >> something like
> 	        >>     >       that (I'm not looking at the schema for  
> layer definition
> 	        >> so I may
> 	        >>     >       have that wrong)
> 	        >>     >
> 	        >>     >       Cheers
> 	        >>     >
> 	        >>     >       Paul
> 	        >>     >
> 	        >>     >       On 4-Feb-07, at 3:23 PM, Carsten Hess wrote:
> 	        >>     >
> 	        >>     >       > Hi Paul,
> 	        >>     >       >
> 	        >>     >       > I think we have four choices for binary  
> raster data:
> 	        >>     >       >
> 	        >>     >       > 1) We could attach it to the symbol  
> resource as binary data
> 	        >>     >       > (resource data)
> 	        >>     >       > 2) We could make it its own resource
> 	        >>     >       > 3) We could put it  somewhere on the file  
> system
> 	        >>     >       > 4) We could embedd it in the XML as  
> base64 encoded stream
> 	        >>     >       >
> 	        >>     >       > Currently you find 3) only because of our  
> prototype, we
> 	        >> actually
> 	        >>     >       > don't want to propose that. We played  
> with some of the
> 	        >> XML and use
> 	        >>     >       > it to refer to raster via the file  
> system. That is
> 	        >> easier to debug
> 	        >>     >       > then in the resource repository.
> 	        >>     >       >
> 	        >>     >       > The schema refers to 2) and 4) I think as  
> a possiblity
> 	        >> ... I
> 	        >>     >       > personally also like 1) but then we would  
> have to figure
> 	        >> out how to
> 	        >>     >       > refer to it and how to put multipl raster  
> in there.
> 	        >>     >       >
> 	        >>     >       > Cheers
> 	        >>     >       >   Carsten
> 	        >>     >       >
> 	        >>     >       >       -----Original Message-----
> 	        >>     >       >       From: mapguide-internals- 
> bounces at lists.osgeo.org
> 	        >> on behalf of Paul
> 	        >>     >       > Spencer (External)
> 	        >>     >       >       Sent: Sun 2/4/2007 12:22 PM
> 	        >>     >       >       To: MapGuide Internals Mail List
> 	        >>     >       >       Cc:
> 	        >>     >       >       Subject: Re: [mapguide-internals]  
> MapGuide RFC 14
> 	        >> - Cartographic
> 	        >>     >       > StylizationEngine (maybe this time I'll  
> get it right)
> 	        >>     >       >
> 	        >>     >       >
> 	        >>     >       >
> 	        >>     >       >       I notice that the first example  
> references an
> 	        >> image in the Library://
> 	        >>     >       >       but the documentation in the  
> proposed schema say
> 	        >> its a reference to
> 	        >>     >       >       an external image.
> 	        >>     >       >
> 	        >>     >       >       Is the intention to actually  
> reference images on
> 	        >> the server in an
> 	        >>     >       >       external location on the file  
> system, external via
> 	        >> http, or actually
> 	        >>     >       >       to allow putting images into the  
> repository?
> 	        >>     >       >
> 	        >>     >       >       I like the idea of being able to  
> put images such
> 	        >> as PNGs into the
> 	        >>     >       >       repository and referencing them  
> there - but there
> 	        >> is no concept of
> 	        >>     >       >       this in the proposed schema.
> 	        >>     >       >
> 	        >>     >       >       I guess, thinking about this, it  
> would be best to
> 	        >> reference an image
> 	        >>     >       >       inside a SymbolLibrary.  What would  
> be the
> 	        >> implications of this to
> 	        >>     >       >       your proposal?
> 	        >>     >       >
> 	        >>     >       >       Cheers
> 	        >>     >       >
> 	        >>     >       >       Paul
> 	        >>     >       >
> 	        >>     >       >       On 2-Feb-07, at 4:29 PM, Robert  
> Bray wrote:
> 	        >>     >       >
> 	        >>     >       >       > THIS TIME SENT AS VERY PLAIN TEXT  
> with FIXED
> 	        >> LINK - SORRY FOR THE
> 	        >>     >       >       > SPAN ALL
> 	        >>     >       >       >
> 	        >>     >       >       > All,
> 	        >>     >       >       >
> 	        >>     >       >       > We would like to submit the  
> following RFC for
> 	        >> open discussion and
> 	        >>     >       >       > comments:
> 	        >>     >       >       >
> 	        >>     >       >       >
> 	        >> http://www.osgeo.org/trac/mapguide/wiki/MapGuideRfc14
> 	        >>     >       >       >
> 	        >>     >       >       > - Note this RFC is living on our  
> new Trac based
> 	        >> Wiki. The other
> 	        >>     >       >       > RFCs will be moving to this  
> location shortly.
> 	        >>     >       >       >
> 	        >>     >       >       > Please respond to the list with  
> any feedback and
> 	        >> we will be happy
> 	        >>     >       >       > to respond.
> 	        >>     >       >       >
> 	        >>     >       >       > Thanks,   Walt, Traian, Carsten,  
> Jason (and
> 	        >> others like Bob the
> 	        >>     >       >       > admin assistant)
> 	        >>     >       >       >  
> _______________________________________________
> 	        >>     >       >       > mapguide-internals mailing list
> 	        >>     >       >       > mapguide-internals at lists.osgeo.org
> 	        >>     >       >       >
> 	        >> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 	        >>     >       >
> 	        >>     >       >
> 	        >>  
> +-----------------------------------------------------------------+
> 	        >>     >       >       |Paul Spencer
> 	        >> pspencer at dmsolutions.ca    |
> 	        >>     >       >
> 	        >>  
> +-----------------------------------------------------------------+
> 	        >>     >       >       |Chief Technology
> 	        >> Officer                                         |
> 	        >>     >       >       |DM Solutions Group Inc
> 	        >> http://www.dmsolutions.ca/ |
> 	        >>     >       >
> 	        >>  
> +-----------------------------------------------------------------+
> 	        >>     >       >
> 	        >>     >       >
> 	        >>     >       >
> 	        >>     >       >
> 	        >>     >       >        
> _______________________________________________
> 	        >>     >       >       mapguide-internals mailing list
> 	        >>     >       >       mapguide-internals at lists.osgeo.org
> 	        >>     >       >
> 	        >> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 	        >>     >       >
> 	        >>     >       >  
> _______________________________________________
> 	        >>     >       > mapguide-internals mailing list
> 	        >>     >       > mapguide-internals at lists.osgeo.org
> 	        >>     >       > http://lists.osgeo.org/mailman/listinfo/ 
> mapguide-internals
> 	        >>     >
> 	        >>     >
> 	        >>  
> +-----------------------------------------------------------------+
> 	        >>     >       |Paul Spencer
> 	        >> pspencer at dmsolutions.ca    |
> 	        >>     >
> 	        >>  
> +-----------------------------------------------------------------+
> 	        >>     >       |Chief Technology
> 	        >> Officer                                         |
> 	        >>     >       |DM Solutions Group Inc
> 	        >> http://www.dmsolutions.ca/ |
> 	        >>     >
> 	        >>  
> +-----------------------------------------------------------------+
> 	        >>     >
> 	        >>     >
> 	        >>     >
> 	        >>     >
> 	        >>     >        
> _______________________________________________
> 	        >>     >       mapguide-internals mailing list
> 	        >>     >       mapguide-internals at lists.osgeo.org
> 	        >>     >       http://lists.osgeo.org/mailman/listinfo/ 
> mapguide-internals
> 	        >>     >
> 	        >>     >
> 	        >>     >
> 	        >>     >
> 	        >>  
> ---------------------------------------------------------------------- 
> --
> 	        >>     >
> 	        >>     > _______________________________________________
> 	        >>     > mapguide-internals mailing list
> 	        >>     > mapguide-internals at lists.osgeo.org
> 	        >>     > http://lists.osgeo.org/mailman/listinfo/mapguide- 
> internals
> 	        >>     _______________________________________________
> 	        >>     mapguide-internals mailing list
> 	        >>     mapguide-internals at lists.osgeo.org
> 	        >>     http://lists.osgeo.org/mailman/listinfo/mapguide- 
> internals
> 	        >>
> 	        >> _______________________________________________
> 	        >> mapguide-internals mailing list
> 	        >> mapguide-internals at lists.osgeo.org
> 	        >> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 	        >
> 	        >  
> +-----------------------------------------------------------------+
> 	        > |Paul Spencer                           
> pspencer at dmsolutions.ca    |
> 	        >  
> +-----------------------------------------------------------------+
> 	        > |Chief Technology  
> Officer                                         |
> 	        > |DM Solutions Group Inc                http:// 
> www.dmsolutions.ca/ |
> 	        >  
> +-----------------------------------------------------------------+
> 	        >
> 	        >
> 	        >
> 	        >
> 	        > _______________________________________________
> 	        > mapguide-internals mailing list
> 	        > mapguide-internals at lists.osgeo.org
> 	        > http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 	        >
> 	        _______________________________________________
> 	        mapguide-internals mailing list
> 	        mapguide-internals at lists.osgeo.org
> 	        http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 	
> 	
>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals

+-----------------------------------------------------------------+
|Paul Spencer                          pspencer at dmsolutions.ca    |
+-----------------------------------------------------------------+
|Chief Technology Officer                                         |
|DM Solutions Group Inc                http://www.dmsolutions.ca/ |
+-----------------------------------------------------------------+






More information about the mapguide-internals mailing list