speleo3/inkscape-speleo

Inkscape extensions for cave surveying

inkscape-speleo's Issues

Cannont set wall type

I am using Inkscape 0.91 with the most current Speleo extension. When I try to "Set Line Type" of wall on a line I get the following error. When exported to .th2 file the line shows up in therion correctly, but it does not change appearance in inkscape or show the tick marks indicating direction.

Traceback (most recent call last):
File "th2setprops.py", line 105, in
e.affect()
File "C:\Program Files\Inkscape\share\extensions\inkex.py", line 268, in affect
self.effect()
File "th2setprops.py", line 102, in effect
del node.attrib[inkscape_path_effect]
File "lxml.etree.pyx", line 1948, in lxml.etree._Attrib.delitem (src/lxml/lxml.etree.c:42602)
File "apihelpers.pxi", line 502, in lxml.etree._delAttribute (src/lxml/lxml.etree.c:14078)
KeyError: u'{http://www.inkscape.org/namespaces/inkscape}path-effect'

Feature request topreader: improved svg export

Current status:

• When producing a .svg file with topreader.py --dump svg, the resulting planview and sideview layers overlap usually.
• The page size does not match the drawn area

Requested features:

• Place planview and sideview side-by-side without overlap
• Resize the page to cover full drawing area

Missing requirements.txt file for pip

It would be nice to have a requirements.txt file to install with pip install -r requirements.txt

When setting properties of a station a stroke style is added to several objects

Just trying Therion extension for Inkscape, following these instructions (https://therion.speleo.sk/wiki/_media/conversion_of_svg_file_to_therion_format.pdf).

On step 10, when I click on Apply for the first time, my station is redraw with a different style (which is fine) but tons of other objects in my drawing have a stroke added (which is not fine). Is this a bug?

If I uncheck "Drop style" there are no visible changes in my drawing, just the relevant object properties are applied. Can I proceed with "Drop style" unchecked?

th2 open issue

Hellow.
Your plugin is great!!!

Here is one issue:

• I try open TH2 file. I don't understand python language :(, but may be is trivial.

Traceback (most recent call last):
File "th2_input.py", line 149, in
filename = find_in_pwd(th2pref.argv[0])
File "C:\Program Files\Inkscape\share\extensions\th2ex.py", line 458, in find_in_pwd
for dirname in ['', os.environ['PWD']] + path:
File "C:\Program Files\Inkscape\python\Lib\os.py", line 423, in getitem
return self.data[key.upper()]
KeyError: 'PWD'

THX.
Best regards
Random

update needed for Inkscape version 1.0

Hello,
Thank you for providing this extension for Inkscape users!

This is just to let you know that most 3rd party Inkscape extensions, like this one, probably will not work with the upcoming new Inkscape version, the long-awaited version 1.0.

Here is the info you need to update this extension, so that it will work with 1.0 and future versions.
https://wiki.inkscape.org/wiki/index.php?title=Updating_your_Extension_for_1.0

If you have further questions, you can contact Inkscape developers via mailing lists, forum, or the chatroom.

If you have already updated it, please disregard this message.

All best,
brynn

Support th2 line point options

Therion supports line point options which allow for example changing the subtype of a line or putting an altitude label on a line point. SVG has no concept of "line point options" which makes it tricky to map them from/to th2 format. Currently, lines with line point options are imported read-only ("locked") and their data is preserved in the <desc> tag to make a round-trip to th2 possible.

Proposal for editable line point option support

• Represent line as group of path segments
• Every point with options starts a new segment
• Point options can be stored like regular options on the segment

Example:

line wall
  437 56
  370 158
  altitude .
  240 281
endline

Will be split into two segments:

<g inkscape:label="line wall">
  <path inkscape:label="line wall -altitude ." d="M 370 -158 L 240 -281" />
  <path inkscape:label="line wall" d="M 437 -56 L 370 -158" />
</g>

Inkscape V1.2

I believe this extension may be breaking with Inkscape v1.2

I tried to install this with v1.2 and couldn't save files to .th2 and could not open .th2 files. Downgrading to Inkscape v1.1 fixed the problem for me, but specifically I was seeing this error in both saving and opening files in v1.2:

I tried to dig into the problem a little and I'm not 100% what's causing this, but I suspect it's to do with v1.2 removing deprecated fields, which I presume include InkOption. When I manually polyfilled the missing InkOption, subsequent inkex attributes could not be found.

It is also mentioned that some pre v1.0 extension support has been removed in v1.2 in the changelog

Hope this helps!

Import from PocketTopo does not completely account for declination

My imported PocketTopo files all seem to have the plan component of the survey network incorrectly plotted to the magnetic bearings, not corrected according to the declination that was entered at the start of the survey session.
Our magnetic declination is a little over 20 degrees east of true north , and so we often set the declination in PocketTopo to 20 degrees. This has the effect of making true north point directly up the page (more or less).
It seems like Inkscape is taking the sketch correctly, but is not adding the declination to the survey bearings (azimuths).
The elevation is correctly plotted however.

For comparison, here is the original PocketTopo plan sketch.

Might this be a bug in the plugin? I think my version dates from around mid 2020.

Point Stations Incorrectly Spaced

I make a small circle and use the therion extention to set its property to point, type station, option -name 0. When I export to .th2 file these all appear, but they have been offset and skewed to the wrong location.

I can't seem to upload a .zip or .svg in this window as an example.

Feature request: Projection in XVI dump

Hi Thomas,

when creating the Therion exports from e.g. SexyTopo, two separate .xvi files are generated,
one with the plan-projection and one with the extended elevation projection.

When using topreader --dump xvi, only a single .xvi file is created (which, in my specific case, just contained the plan-projection).
Would it be possible to add two different options --dump xvi_plan and --dump xvi_ee to generate .xvi files for both projections?

Or is this feature already included and I am missing it somehow?

Best,
Matthias

Improve topreader `--help`

From #20 (comment) by @MFeldmaier:

Could you improve the help menu and add some explanation to the individual options.
I especially found the difference between xvi and xvi-ee not self-explaining.
Maybe rename the first to xvi-plan?

Note: Consider xvi-plan as an alias for xvi instead of renaming, which would be a breaking change.