Hello Hugh,

Thank you very much for your answer, the problem has been solved I will post 
here what was causing the issue, for you to know,

When we were modifying the data inside qgis we were not exporting it but 
mashing the previous one by saving, and then changing the name of the file 
outside qgis, instead we exported the shp file from qgis and gave the file a 
new name from there, and the corruption of the file disappeared.

Have a nice day! 馃檪

[Opsait]<http://www.minsait.com/>


Sandra G贸mez S谩nchez

________________________________
De: Hugh Kelley <[email protected]>
Enviado: lunes, 21 de agosto de 2023 14:55
Para: G贸mez S谩nchez, Sandra <[email protected]>
Cc: qgis-user <[email protected]>
Asunto: Re: [Qgis-user] Error - Qgis files getting corrupted after saving

Hi Sandra,

When you say "data" are you referring to spatial data saved in something like a 
shapefile geopackage etc, or the actual qgis file ending in .qgz or .qgs?

If it is the actual qgis file itself that you are seeing corrupted, I would not 
expect a qgis file created by a newer version to be backwards compatible with 
and older version of qgis. I often see people using older versions run into 
weird problems when opening a file created by a newer version. Perhaps others 
will say otherwise but I don't expect this to a problem that can be solved. All 
users should be on a common version for the best experience.

If its spatial data you're seeing corrupted that is something that should be 
solvable anf sharing what file type is being used might get you helpful 
suggestions.

As a note, because opening and saving a qgis file with a different version can 
cause problems across versions, like loosing symbology settings, I backup my 
qgis work at least once a day so that I have something recent to fall back to 
if an issue like this occurs.

Best,

Hugh

On Mon, Aug 21, 2023, 8:43 AM G贸mez S谩nchez, Sandra via QGIS-User 
<[email protected]<mailto:[email protected]>> wrote:
Hello there,

I am facing an issue with the saving files from Qgis and importing them to 
another software.

On this case, we are changing data inside Qgis and then import that data into 
Keycom.

The thing is, we have 2 colleagues which are using Qgis 3.28.8 and 3.32.0 
versions and after they change the data inside qgis, and they save that data, 
the files get corrupted;

I have been trying with my own qgis, which is 3.28.2 and in mine works perfect; 
I have changed their raw data and when I import that data on keycom it works, I 
have also sended them my own data (ready for import) to them, and they are able 
to import it, but once they put that data on their Qgis it gets corrupted and 
we can't work with it, we have checked the steps they are taking but they are 
doing the same as me,

We did a silly test in which I sended them my data, they imported it into 
keycom, it worked, then they changed one single value inside Qgis and it got 
corrupted; so we know that the issue is located into the "saving" form from 
Qgis;

We can open the files from Qgis again and they don't show signs of corruption 
inside, is just when we try to import them into keycom when the error is shown, 
so we are kinda lost here,

is there any issue / feature we have to check for?

Thank you very much,

Sandra

[Opsait]<http://www.minsait.com/>


Sandra G贸mez S谩nchez

________________________________

Este correo electr贸nico y, en su caso, cualquier fichero anexo al mismo, 
contiene informaci贸n de car谩cter confidencial exclusivamente dirigida a su 
destinatario o destinatarios. Si no es vd. el destinatario indicado, queda 
notificado que la lectura, utilizaci贸n, divulgaci贸n y/o copia sin autorizaci贸n 
est谩 prohibida en virtud de la legislaci贸n vigente. En el caso de haber 
recibido este correo electr贸nico por error, se ruega notificar inmediatamente 
esta circunstancia mediante reenv铆o a la direcci贸n electr贸nica del remitente.
Evite imprimir este mensaje si no es estrictamente necesario.

This email and any file attached to it (when applicable) contain(s) 
confidential information that is exclusively addressed to its recipient(s). If 
you are not the indicated recipient, you are informed that reading, using, 
disseminating and/or copying it without authorisation is forbidden in 
accordance with the legislation in effect. If you have received this email by 
mistake, please immediately notify the sender of the situation by resending it 
to their email address.
Avoid printing this message if it is not absolutely necessary.
_______________________________________________
QGIS-User mailing list
[email protected]<mailto:[email protected]>
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

________________________________

Este correo electr贸nico y, en su caso, cualquier fichero anexo al mismo, 
contiene informaci贸n de car谩cter confidencial exclusivamente dirigida a su 
destinatario o destinatarios. Si no es vd. el destinatario indicado, queda 
notificado que la lectura, utilizaci贸n, divulgaci贸n y/o copia sin autorizaci贸n 
est谩 prohibida en virtud de la legislaci贸n vigente. En el caso de haber 
recibido este correo electr贸nico por error, se ruega notificar inmediatamente 
esta circunstancia mediante reenv铆o a la direcci贸n electr贸nica del remitente.
Evite imprimir este mensaje si no es estrictamente necesario.

This email and any file attached to it (when applicable) contain(s) 
confidential information that is exclusively addressed to its recipient(s). If 
you are not the indicated recipient, you are informed that reading, using, 
disseminating and/or copying it without authorisation is forbidden in 
accordance with the legislation in effect. If you have received this email by 
mistake, please immediately notify the sender of the situation by resending it 
to their email address.
Avoid printing this message if it is not absolutely necessary.
_______________________________________________
QGIS-User mailing list
[email protected]
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Reply via email to