qgisred / QGISRed

GNU General Public License v2.0
23 stars 8 forks source link

"Import Data" inconsistency #16

Closed ratempus closed 4 years ago

ratempus commented 4 years ago

I have a big .inp file for a WDN of a city. I load it on EPANET 2.0.12 (Win7) and run with no problems. With QGISRed v0.9 on QGIS 3.12 I got a Log Messages window with multiples errors about "cannot be interpreted coordinates on X coordinate" and not load the file. Thanks for any help in advance.

neslerel commented 4 years ago

Hi @ratempus, Thanks for your message.

Can you send us the INP file to test it? You can send it by email to nestorlerma@waterpi.com or if it is so big, using https://wetransfer.com/ If not, can you extract COORDINATES and VERTICES sections to another file and send it us? If not, can you open INP file with a text editor and review these sections to try to find something wrong? We want to make all the possible to fix this type of problems.

Thanks again!

ratempus commented 4 years ago

Hi Nestor, Thanks for your answer. First at all, congratulations for QGISRed!

  1. Attached to this email I send the file “Modelo_final1.inp” about whom i commented on the message. I appreciate your collaboration.
  2. When I import data from EPANET to a QGISRed project, and if it is necessary to add elements, is it better to do it directly on the created project? Or is it also possible to edit it once it has been transformed to a QGIS project?
  3. I appreciate any hints on how to add a tank to a junction at the end of an existing pipe using the QGISRed tools (I received a message as, “No node under junction selected”.??

Thank you.

PD: We can write in spanish?

On Mar 31, 2020, at 12:40 AM, neslerel notifications@github.com wrote:

Hi @ratempus https://github.com/ratempus, Thanks for your message.

Can you send us the INP file to test it? You can send it by email to nestorlerma@waterpi.com mailto:nestorlerma@waterpi.com or if it is so big, using https://wetransfer.com/ https://wetransfer.com/ If not, can you extract COORDINATES and VERTICES sections to another file and send it us? If not, can you open INP file with a text editor and review these sections to try to find something wrong? We want to make all the possible to fix this type of problems.

Thanks again!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/neslerel/QGISRed/issues/16#issuecomment-606411874, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO777RPEMJBOALNNU7AAZTDRKF653ANCNFSM4LXCX2SQ.

neslerel commented 4 years ago

Hola, Creo que GitHub no permite adjuntar archivos (o al menos si se contesta desde el email). Al menos yo no he recibido nada. Envíalo al correo que te comentaba en el anterior mensaje, por favor.

Respecto a lo de añadir elemento, esta última versión (0.9) incluye bastantes herramientas de edición para crear elementos, así que lo normal es añadirlos después de importar.

Y en cuanto a añadir un depósito, está el botón para añadirlo y, seleccionado un nudo (Junction o Reservoir) debería cambiarlo. Ese mensaje que comentas, no lo localizo, no sé a qué se debe. Desde GitHub, cuando respondes un mensaje puedes adjuntar alguna imagen, lo que puede ayudarnos a identificar el problema.

Gracias por tus comentarios!

neslerel commented 4 years ago

Hola @ratempus, Algo comentado en este issue sigue sin funcionar? Podemos cerrarlo y si sale algo más, creas otro issue?

ratempus commented 4 years ago

Hola Nestor, Gracias por escribir. Estuve ocupado en otro proyecto que me alejó de la correspondencia. Efectivamente, la sugerencia que me diste de la coma, funciono muy bien. Veo que hay una actualizacion de QGISRed (0.1) .

Puedes cerrar el issue #16. Muchas gracias. Estaremos en contacto.

Raúl A. Castañeda S. ...from my iPhone

On May 14, 2020, at 10:15 AM, neslerel notifications@github.com wrote:

 Hola @ratempus, Algo comentado en este issue sigue sin funcionar? Podemos cerrarlo y si sale algo más, creas otro issue?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.