archaeodav / felttegn

Public repository for FeltTegn, a Qgis Plugin for processing survey data from archaeological excavations conducted by Danish Museums
GNU General Public License v3.0
5 stars 1 forks source link

En fil der ikke giver problemer i mapdigi, men giver problemer i felttegn #15

Closed karlhjalte closed 2 years ago

karlhjalte commented 2 years ago

Hej

Ved autoopret af denne fil, giver felttegn et næsten ubrugeligt returresultat. Der sker noget meget mærkeligt med A1, som bliver til et polygon der ikke kan færdigbearbejdes. Filen er kørt igennem som både geopackage og .tab fil, men begge resultater er ikke gode. Jeg har forsøgt at optimere .csv-filen til mere Felttegn venlig med punktummer i stedet for mellemrum, men uden forbedring. HOM3720_20210915 - MI.csv HOM3720_20210915 - QGIS.csv

Prøv at køre HOM3720_20210915.-.MI.csv igennem både MI mapdigi og QGIS felttegn, og det er tydeligt at der er nogle større problemer i forhold til videre redigering. Igennem mapdigi bliver resultatet muligt at redde, men i Felttegn kan man ikke rigtigt komme videre

mvh. Hjalte

archaeodav commented 2 years ago

Screenshot_2021-09-22_12-21-01

Not sure what you mean- is this how A1 should look?

karlhjalte commented 2 years ago

Nope. Signal was bad for A1, because of trees. The points were supposed to be along the border of the trench. However, that is of course not the problem. Try to change the outline of A1. It resets itself, and the polygon cannot be altered it seems. Same goes for the little trench next to it. It is not possible to change the outline by nodes (at least not possible for me)

archaeodav commented 2 years ago

Screenshot_2021-09-22_13-56-14

No problem here- either using the reshape tool or by editing vertices.

karlhjalte commented 2 years ago

Strange. For me it kept resetting back to original shape once you saved.

archaeodav commented 2 years ago

Might be worth trying the new version- 0.28 is on git but not yet approved by the QGIS plugin repo, although I couldn't replicate this in 0.25 either.

Which QGIS version are you using? Does it do this with other layers?

karlhjalte commented 2 years ago

Yeah... i'm running 0.25. Didn't notice it was not 0.28 in the repository. QGIS version is 3.16.11 (long term stable)

I will try to run it again and see if I can replicate

How about the generic generated ID for some of the features. All of the features have an ID, but one was double. Can't it just display output even though ID is double, or do you need to troubleshoot before to make certain nothing has same ID (number)? Sometimes as well, features are disconnected with same ID, ie. layer cut by drain

archaeodav commented 2 years ago

How about the generic generated ID for some of the features. All of the features have an ID, but one was double. Can't it just display output even though ID is double, or do you need to troubleshoot before to make certain nothing has same ID (number)? Sometimes as well, features are disconnected with same ID, ie. layer cut by drain

See issue #8. Fix coming shortly

archaeodav commented 2 years ago

Fault not replicable- likely caused by active desktop / OS problems