[GRASS5] g51 v.digit

[John A. Preston]

> This doesn't appear to be a driver issue. Each call to
> R_cont_{abs,rel} should result in a single call to gdImageLine()
> within the PNG driver.
> 
> However, I don't think that e.g. d.vect will attempt to "optimise"
> paths, i.e. merge adjacent colinear segments into a single line. So,
> if the actual vector map is comprised of many small segments, that's
> the way that it will get drawn.
But I think that some component of the display architecture should have
this to be able to provide good quality output .

> The new API is currently at the drawing board stage.
> 
> My preference would be a framework, within which individual modules
> would be free to generate arbitrary PostScript objects (in the sense
> of %%BeginObject/%%EndObject). Others may have different views, and
> I'm open to suggestions.
I like that. Would it be possible to include the capabiity of merging adajacent segments
somewhere here?

> However, I am keen to ensure that hardcopy is well supported (which
> basically boils down to ruling out anything which involves explicit
> rasterisation, "pixel" coordinates, or "thin" lines).
I agree.

-- 
John Preston <jpreston at uwimona.edu.jm>