[mapguide-internals] MapGuide RFC
14- CartographicStylizationEngine (maybe this time I'll get it right)
Paul Spencer
pspencer at dmsolutions.ca
Sun Feb 4 19:44:57 EST 2007
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/ |
+-----------------------------------------------------------------+
More information about the mapguide-internals
mailing list