[postgis-devel] Nice diagrams
chodgson at refractions.net
Tue Jul 22 09:59:24 PDT 2008
Perhaps the documentation could be built before the source packages are
even built, so that people downloading the source don't need to have
these dependencies, or waste time building the documentation
images/documents from the sources. Only people building from an SVN
checkout would need to do so, and ideally building the documentation
would be separate step from building the library so that people who are
helping with development don't necessarily need to have the dependencies
for the documentation build either.
Just thinking this would be a good option to minimize the impact of the
additional dependencies introduced for the documentation build.
Kevin Neufeld wrote:
> Sure, sounds good to me too. I think it's important to have similar
> styles throughout all the example images. This would be a good way to
> accomplish that.
> So, would we then have a section in the Makefile that would convert
> all the svg image files to png and eps files? I can see this growing
> quite large if we need to add different custom parameters to
> ImageMagick's convert utility for different images or files types.
> Mark Cave-Ayland wrote:
>> Obe, Regina wrote:
>>>> So, the proposal is to store the basic drawing in a SVG file
>>>> and them use image magick to add effects and create EPS and PNG for
>>>> and web respectively ?
>>> That was my thought - store in some vector format so all sorts of
>>> resolutions can be accommodated and not worry about shadowing and all
>>> that stuff in the core output format. Use ImageMagick to do the fancy
>>> fluffy stuff.
>> Sounds good to me.
>>> It may or may not be desirable to have shadowing in say PDF. SVG seems
>>> like the easiest candidate to produce that core format and as you said
>>> numerouse editors can output that.
>>> As far as how we produce SVG hadn't thought much about it and not sure
>>> it matters if we use InkScape or whatever. OpenJump can Save As SVG,
>>> and for me personally that would be my choice since I use it a lot for
>>> ad hoc queries anyway. I like that I can run my demo query, save as
>>> and be done with it.
>>> For certain cases the raw PostGIS output even using a template would be
>>> a hassle when we need to overlay to show different colors, points etc.
>>> and so forth since it would almost guarantee manual fiddling.
>> Yeah, I suspect that automatically generating the results from a
>> shapefile will still require extra fiddling, although it could be a
>> good starting point. My feeling is that it is more likely to be the
>> styling of the images that will change rather than the contents, and
>> it's probably just as easy to make the content changes using a
>> program such as Inkscape.
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
More information about the postgis-devel