[mapguide-internals] MapGuide RFC 14 - Cartographic StylizationEngine (maybe this time I'll get it right)

Paul Spencer pspencer at dmsolutions.ca
Sun Feb 4 17:26:53 EST 2007


Bob, I like the idea of keeping them around, if only to act as a  
central repository of images managed by the server and available for  
referencing.

I don't think that storing images outside of the server is a good  
idea, its too easy to delete them or forget they are used by MapGuide.

I don't like the idea of storing images with the actual symbol  
definitions either since it is quite likely that images could be  
reused between symbols.

If the SymbolLibrary is going to be deprecated, then perhaps a new  
object could be created just to hold images for this purpose?

Another benefit of keeping SymbolLibrary around is that it would make  
it quite nice to build up libraries and be able to share them as  
packages.  Not that you couldn't do that in another way I guess, but  
it just seems so nice and neat and clean this way :)

Cheers

Paul

On 4-Feb-07, at 5:16 PM, Robert Bray wrote:

> Some thoughts:
>
> I don't think (2) works because it is binary, not XML. (3) seems  
> like a bad choice for this type of data, in my opinion its better  
> to keep it coupled with the resource.
>
> I like (1) because it keeps the image with the symbol definition. I  
> also like (4), but mainly for saving the resource as XML.
>
> Paul's suggestion is also a viable option if we want to keep the  
> Symbol Library concept around. I guess the burning question is do  
> we still need the DWF symbols / symbol libraries? With this  
> proposal should we deprecate them and keep them around only for  
> backward compatibility?
>
> Bob
>
>
>
> Paul Spencer wrote:
>> 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

+-----------------------------------------------------------------+
|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