Martin Budaj wrote:
> On Thu, 18 Aug 2005 11:26:26 +0100, Wookey wrote
>
>
>>Hmm, so as it goes wrong with the default (scale 1:200) that suggets
>>I have one scrap which is >560m long. I don't think I do have
>>anything that big (I try to keep scraps to <200m).
>>
>>If anyone cares to
Wookey wrote:
> If anyone cares to investigate this then the benarat dataset illustrates the
> problem.
This stuff is already in the TODO list (at least displaying some
reasonable errors by therion). I will look at it next week, I'm leaving
right now to do a bit of real caving.
S.
+++ Martin Budaj [05-08-18 11:23 +0200]:
> On Thu, 18 Aug 2005 00:10:01 +0100, Wookey wrote
> > I can see why such a scale is a problem in map mode (page larger
> > than PDF can manage), but in atlas mode the page size is limited to
> > A4 (or whatever) - so why can I not print an atlas (with a
On Thu, 18 Aug 2005 00:10:01 +0100, Wookey wrote
> I used to have
> scale 1 2000
> base-scale 1 1000
>
> in my layout. That worked OK, but the symbols were very small and
> the text was microscopic.
They were printed in 1/2 size because of base-scale setting.
> So I added
> code metapost
On Thu, 18 Aug 2005 00:36:39 +0100, Wookey wrote
> Obviously we try to avoid areas which cross scrap joins but cannot
> always do so. Other considerations like altitude colouring make it
> difficult, and in a cave which has a lot of mud or water we could
> find that most scrap joins have areas
The area control is better than it used to be, but is still a major pain in
the arse.
I have put very few areas in the Terikan survey because I know they cause
trouble. I've just tried putting some in and it was a rather frustrating
experience. I'll detail the problems I had so we can decide how
I used to have
scale 1 2000
base-scale 1 1000
in my layout. That worked OK, but the symbols were very small and the text
was microscopic.
So I added
code metapost
fonts_setup(10,16,20,24,28)
And that made the text a sensible size.
I just changed base scale to read
base-scale 1 2000
