I am trying to import a survex .3d file into therion. Currently, I am just trying to get all survey point into a pdf file. Anyway, I get a weird error about scaling. Does anyone know how to fix this? --------- thconfig --------- input layout.th source main.th export map -layout plan -output Alva_Blankenship_Cave.pdf ---------- layout.th -------- layout plan scale 1 200 units imperial legend on color map-fg altitude transparency on #PDF DOCUMENTION doc-author "Philip Schuchardt" code tex-map \cavename={Alva Blankenship Cave} \comment{Cartography By: Philip Balister and Philip Schuchardt \copyright 2006 VPI Cave Club} endcode code metapost def l_wall_bedrock_AMER (expr P) = T:=identity; pickup PenA; thdraw P; enddef; def p_gradient_AMER (expr pos,theta,sc,al) = U:=(.15u, .4u); T:=identity aligned al rotated theta scaled sc shifted pos; pickup PenC; #Left Hand side thdraw (-.3u, -.2u) -- (-.7u, .1u); thdraw (-.2u, -.1u) -- (-.4u, .6u); #Centerline thdraw (0u, 0u) -- (0u, .9u); #Right side thdraw (.3u, -.2u) -- (.7u, .1u); thdraw (.2u, -.1u) -- (.4u, .6u); enddef; initsymbol ("p_gradient_AMER"); initsymbol ("l_wall_bedrock_AMER"); endcode symbol-assign line wall:bedrock AMER symbol-assign point gradient AMER endlayout --------- main.th --------- survey "EG3" import EG3.3d endsurvey "EG3" --------------------- Compile------------------------ therion 0.3.10 initialization file: /etc/therion.ini reading ... done configuration file: thconfig reading ... done reading source files ... done preprocessing database ... done scanning centreline tree ... done searching for centerline loops ... done calculating station coordinates ... done processing survey data ... ####################### cavern log file ######################## 1> Survex 1.0.38 2> Copyright (C) 1990-2005 Olly Betts 3> 4> Survey contains 772 survey stations, joined by 0 legs. 5> There are 0 loops. 6> Survey has 772 connected components. 7> Total length of survey legs = 0.00m ( 0.00m adjusted) 8> Total plan length of survey legs = 0.00m 9> Total vertical length of survey legs = 0.00m 10> Vertical range = 42949672.68m (from 20 at 42949672.68m to 21 at 0.00m) 11> North-South range = 42949672.86m (from 495 at 42949672.86m to 21 at 0.00m) 12> East-West range = 42949672.91m (from 15 at 42949672.91m to 21 at 0.00m) 13> 772 0-nodes. 14> ######################### transcription ######################## 4> 772 : eg3.ah38@EG3 6> 772 : eg3.ah38@EG3 10> 20 : eg3.a2@EG3 -- 21 : eg3.a1@EG3 11> 495 : eg3.a40@EG3 -- 21 : eg3.a1@EG3 12> 15 : eg3.a8@EG3 -- 21 : eg3.a1@EG3 13> 772 : eg3.ah38@EG3 #################### end of cavern log file #################### done calculating basic statistics ... done processing extended elevation ... done processing references ... done selecting export objects ... done processing projection plan ... done writing Alva_Blankenship_Cave.pdf ... therion: error -- scale too large -- maximal scale for this configuration is 1 : 928886
On Tue, Mar 14, 2006 at 08:19:36PM -0500, Philip Schuchardt wrote:
10> Vertical range = 42949672.68m (from 20 at 42949672.68m to 21 at 0.00m) 11> North-South range = 42949672.86m (from 495 at 42949672.86m to 21 at 0.00m) 12> East-West range = 42949672.91m (from 15 at 42949672.91m to 21 at 0.00m)
This looks like some weird coordinate wrap-around, since 42949672.91m is 0xfffffffb cm, which is -5cm if interpreted as a signed value. I think the problem must be in the data being fed into Survex, since Survex itself doesn't store coordinates in integer cm until after this point (they're used to store coordinates in the .3d file). Cheers, Olly
I took out must the data and only have 2 survey stations and I get same error. Is there something wrong with this data? Do I need to downgrade survex to make it work? ---------- EG3.svx ------------ *begin EG3 *entrance A2 *units tape feet *begin ; Trip 1 *date 2004.07.04 *calibrate declination 7.55 *team "Blah" Notes *team "Blah" Instruments *team "Blah" Lead Tape *data normal from to compass tape clino ;from to compass tape clino A1 A2 285 7.6 -7 *end *end EG3 On Tuesday 14 March 2006 8:59 pm, Olly Betts wrote:
On Tue, Mar 14, 2006 at 08:19:36PM -0500, Philip Schuchardt wrote:
10> Vertical range = 42949672.68m (from 20 at 42949672.68m to 21 at 0.00m) 11> North-South range = 42949672.86m (from 495 at 42949672.86m to 21 at 0.00m) 12> East-West range = 42949672.91m (from 15 at 42949672.91m to 21 at 0.00m)
This looks like some weird coordinate wrap-around, since 42949672.91m is 0xfffffffb cm, which is -5cm if interpreted as a signed value.
I think the problem must be in the data being fed into Survex, since Survex itself doesn't store coordinates in integer cm until after this point (they're used to store coordinates in the .3d file).
Cheers, Olly _______________________________________________ Therion mailing list Therion@speleo.cz http://www.speleo.cz/mailman/listinfo/therion
On Tue, Mar 14, 2006 at 09:47:50PM -0500, Philip Schuchardt wrote:
I took out must the data and only have 2 survey stations and I get same error. Is there something wrong with this data? Do I need to downgrade survex to make it work?
I don't think there's anything wrong with the data, or with survex. Hmm, in fact I've just realised exactly where the problem almost certainly lies. If you edit extern/img.c in the therion source code and change (at about line 42): # define INT32_T long to read: # define INT32_T int And then recompile and reinstall therion, then I'm pretty confident everything will work. If it does then let me know and I'll fix this in a better way. Cheers, Olly
Nope that didnt fix it. When I ran it on ~x86 box it worked... I must be a AMD64 issue... therion 0.3.10 initialization file: /etc/therion.ini reading ... done configuration file: thconfig reading ... done reading source files ... done preprocessing database ... done scanning centreline tree ... done searching for centerline loops ... done calculating station coordinates ... done processing survey data ... ####################### cavern log file ######################## 1> Survex 1.0.38 2> Copyright (C) 1990-2005 Olly Betts 3> 4> Survey contains 2 survey stations, joined by 0 legs. 5> There are 0 loops. 6> Survey has 2 connected components. 7> Total length of survey legs = 0.00m ( 0.00m adjusted) 8> Total plan length of survey legs = 0.00m 9> Total vertical length of survey legs = 0.00m 10> Vertical range = 42949672.68m (from 2 at 42949672.68m to 1 at 0.00m) 11> North-South range = 0.30m (from 2 at 0.30m to 1 at 0.00m) 12> East-West range = 42949670.68m (from 2 at 42949670.68m to 1 at 0.00m) 13> 2 0-nodes. 14> ######################### transcription ######################## 4> 2 : eg3.a2@EG3 6> 2 : eg3.a2@EG3 10> 2 : eg3.a2@EG3 -- 1 : eg3.a1@EG3 11> 2 : eg3.a2@EG3 -- 1 : eg3.a1@EG3 12> 2 : eg3.a2@EG3 -- 1 : eg3.a1@EG3 13> 2 : eg3.a2@EG3 #################### end of cavern log file #################### done calculating basic statistics ... done processing extended elevation ... done processing references ... done selecting export objects ... done processing projection plan ... done writing Alva_Blankenship_Cave.pdf ... therion: error -- scale too large -- maximal scale for this configuration is 1 : 928886 On Wednesday 15 March 2006 12:22 am, Olly Betts wrote:
On Tue, Mar 14, 2006 at 09:47:50PM -0500, Philip Schuchardt wrote:
I took out must the data and only have 2 survey stations and I get same error. Is there something wrong with this data? Do I need to downgrade survex to make it work?
I don't think there's anything wrong with the data, or with survex.
Hmm, in fact I've just realised exactly where the problem almost certainly lies.
If you edit extern/img.c in the therion source code and change (at about line 42):
# define INT32_T long
to read:
# define INT32_T int
And then recompile and reinstall therion, then I'm pretty confident everything will work. If it does then let me know and I'll fix this in a better way.
Cheers, Olly
On Wed, Mar 15, 2006 at 08:51:15AM -0500, Philip Schuchardt wrote:
Nope that didnt fix it.
Ah yes, I need to also fix the get32() function. Can you try the attached patch? To apply it: cd therion-0.3.9 patch -p0 < img.patch (if you've already made the previous change it'll say the first hunk is already applied and ask if you want to reverse the patch - just say no and ignore the first hunk failing to apply). And then rebuild and reinstall. Cheers, Olly
The patch fixes the AMD64 scaling problem... Can you please add this patch to the snapshot? On Wed, Mar 15, 2006 at 08:51:15AM -0500, Philip Schuchardt wrote:
Nope that didnt fix it.
Ah yes, I need to also fix the get32() function. Can you try the attached patch? To apply it: cd therion-0.3.9 patch -p0 < img.patch (if you've already made the previous change it'll say the first hunk is already applied and ask if you want to reverse the patch - just say no and ignore the first hunk failing to apply). And then rebuild and reinstall. Cheers, Olly
Olly, Just for your info the 3d file Philip Schuchardt is working with has the coordinate system for the cave set up so the station coordinates are also the UTM coordinates. This makes overlays easy with geo-referenced surface maps. This would explain why the x,y numbers are large. Philip Olly Betts wrote:
On Tue, Mar 14, 2006 at 08:19:36PM -0500, Philip Schuchardt wrote:
10> Vertical range = 42949672.68m (from 20 at 42949672.68m to 21 at 0.00m) 11> North-South range = 42949672.86m (from 495 at 42949672.86m to 21 at 0.00m) 12> East-West range = 42949672.91m (from 15 at 42949672.91m to 21 at 0.00m)
This looks like some weird coordinate wrap-around, since 42949672.91m is 0xfffffffb cm, which is -5cm if interpreted as a signed value.
I think the problem must be in the data being fed into Survex, since Survex itself doesn't store coordinates in integer cm until after this point (they're used to store coordinates in the .3d file).
Cheers, Olly _______________________________________________ Therion mailing list Therion@speleo.cz http://www.speleo.cz/mailman/listinfo/therion
I don't think that this is UTM. UMT has usually 7digits in y-direction and 6 in x-direction. Wolfgang Philip Balister schrieb:
Olly,
Just for your info the 3d file Philip Schuchardt is working with has the coordinate system for the cave set up so the station coordinates are also the UTM coordinates. This makes overlays easy with geo-referenced surface maps. This would explain why the x,y numbers are large.
Philip
Olly Betts wrote:
On Tue, Mar 14, 2006 at 08:19:36PM -0500, Philip Schuchardt wrote:
10> Vertical range = 42949672.68m (from 20 at 42949672.68m to 21 at 0.00m) 11> North-South range = 42949672.86m (from 495 at 42949672.86m to 21 at 0.00m) 12> East-West range = 42949672.91m (from 15 at 42949672.91m to 21 at 0.00m)
This looks like some weird coordinate wrap-around, since 42949672.91m is 0xfffffffb cm, which is -5cm if interpreted as a signed value.
I think the problem must be in the data being fed into Survex, since Survex itself doesn't store coordinates in integer cm until after this point (they're used to store coordinates in the .3d file).
Cheers, Olly _______________________________________________ Therion mailing list Therion@speleo.cz http://www.speleo.cz/mailman/listinfo/therion
_______________________________________________ Therion mailing list Therion@speleo.cz http://www.speleo.cz/mailman/listinfo/therion
Hmm, you are correct. I need to check whcih svx file Philip is working with. The range in meters is confusing me. Guess I need to look closely at what is going on. Philip Wolfgang Zillig wrote:
I don't think that this is UTM. UMT has usually 7digits in y-direction and 6 in x-direction.
Wolfgang
Philip Balister schrieb:
Olly,
Just for your info the 3d file Philip Schuchardt is working with has the coordinate system for the cave set up so the station coordinates are also the UTM coordinates. This makes overlays easy with geo-referenced surface maps. This would explain why the x,y numbers are large.
Philip
Olly Betts wrote:
On Tue, Mar 14, 2006 at 08:19:36PM -0500, Philip Schuchardt wrote:
10> Vertical range = 42949672.68m (from 20 at 42949672.68m to 21 at 0.00m) 11> North-South range = 42949672.86m (from 495 at 42949672.86m to 21 at 0.00m) 12> East-West range = 42949672.91m (from 15 at 42949672.91m to 21 at 0.00m)
This looks like some weird coordinate wrap-around, since 42949672.91m is 0xfffffffb cm, which is -5cm if interpreted as a signed value.
I think the problem must be in the data being fed into Survex, since Survex itself doesn't store coordinates in integer cm until after this point (they're used to store coordinates in the .3d file).
Cheers, Olly _______________________________________________ Therion mailing list Therion@speleo.cz http://www.speleo.cz/mailman/listinfo/therion
------------------------------------------------------------------------
_______________________________________________ Therion mailing list Therion@speleo.cz http://www.speleo.cz/mailman/listinfo/therion
_______________________________________________ Therion mailing list Therion@speleo.cz http://www.speleo.cz/mailman/listinfo/therion
As Olly mentioned before, the problem is not in the data - but how therion is compiled under 64bit. When therion uses routines from img.c to read .3d file, it reads them not correctly => number are so large. This problem has nothing to do with data or survex. Survex reports large ranges, because it recevies wrong information from therion. S. Quoting Philip Balister <philip@balister.org>:
Hmm, you are correct. I need to check whcih svx file Philip is working with. The range in meters is confusing me. Guess I need to look closely at what is going on.
Philip
Wolfgang Zillig wrote:
I don't think that this is UTM. UMT has usually 7digits in y-direction and 6 in x-direction.
Wolfgang
Philip Balister schrieb:
Olly,
Just for your info the 3d file Philip Schuchardt is working with has the coordinate system for the cave set up so the station coordinates are also the UTM coordinates. This makes overlays easy with geo-referenced surface maps. This would explain why the x,y numbers are large.
Philip
Olly Betts wrote:
On Tue, Mar 14, 2006 at 08:19:36PM -0500, Philip Schuchardt wrote:
10> Vertical range = 42949672.68m (from 20 at 42949672.68m to 21 at 0.00m) 11> North-South range = 42949672.86m (from 495 at 42949672.86m to 21 at 0.00m) 12> East-West range = 42949672.91m (from 15 at 42949672.91m to 21 at 0.00m)
This looks like some weird coordinate wrap-around, since 42949672.91m is 0xfffffffb cm, which is -5cm if interpreted as a signed value.
I think the problem must be in the data being fed into Survex, since Survex itself doesn't store coordinates in integer cm until after this point (they're used to store coordinates in the .3d file).
Cheers, Olly _______________________________________________ Therion mailing list Therion@speleo.cz http://www.speleo.cz/mailman/listinfo/therion
------------------------------------------------------------------------
_______________________________________________ Therion mailing list Therion@speleo.cz http://www.speleo.cz/mailman/listinfo/therion
_______________________________________________ Therion mailing list Therion@speleo.cz http://www.speleo.cz/mailman/listinfo/therion
participants (5)
-
Olly Betts -
Philip Balister -
Philip Schuchardt -
Stacho Mudrak -
Wolfgang Zillig