-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merging different data structure from different versions of Felttegn #32
Comments
Did you fix this OK? Otherwise I have some suggestions |
Remembered I got the fix from Kaj a long time ago (almost two weeks ago).
Just hadn't cognitively understood exactly the problem and what he wrote at
the time, but suddenly it made sense.
But I guess adding same structure and names are necessary. But do you know
an easy fix or good solution?
So I would say I have the fix, but probably not a good one
Den ons. 24. nov. 2021 kl. 23.02 skrev David Stott ***@***.***
…:
Did you fix this OK? Otherwise I have some suggestions
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC4GF767GHEVJDN5C6KW2I3UNVOGZANCNFSM5IXCQL2A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Re-name the fields (You can change the name of the fields in the layer properties as long you're in an edit session) |
yeah... pretty much what I also thought necessary
I just submitted a new issue :-)
Den ons. 24. nov. 2021 kl. 23.11 skrev David Stott ***@***.***
…:
Re-name the fields
https://gis.stackexchange.com/questions/75563/renaming-attributes-fields-in-shapefile-attribute-table-using-qgis
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC4GF73M2IVISQZ5PIKUNKTUNVPHRANCNFSM5IXCQL2A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi
What is best approach for merging data from different versions of Felttegn? Perhaps I am forgetting something, but right now we have the problem at an excavation that started managing data in an older version of Felttegn. That older version gave some other problems, but they are fixed with new version. However, it is not possible to just merge data between different data structure, ie. used to be called "notes" is now called "kommentar". This results in easy copy-paste not being the solution. What is best approach for merging data with different names but same reason for origin?
The text was updated successfully, but these errors were encountered: