shape che mette in crash Qgis 1.8

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

shape che mette in crash Qgis 1.8

emanuele possiedi
Ciao,
ho un problema con il poligono di uno shape.
Se provo a fare l'interrogazione con Qgis 1.8 SO Windows XP, il sistema mi va
in crash.
Se provo a selezionare il poligono e salvarlo con un altro nome non ho
problemi di salvataggio, ma
continuo ad avere problemi nell'interrogazione (mi va in crash).
Ho provato a spezzare il poligono in due (con la funziona taglia) e mi
compare
il messaggio:
"La geometria non è valida. Riparala prima di dividerla".
Ho provato ad importarlo in grass ma continuo ad avere gli stessi problemi.
Lo stesso shape con arview 3.3 e Udig viene interrogato senza problemi.
Come posso provare a riparare la geometria?
Grazie


Link di download
http://we.tl/L7sEZbevNl

_______________________________________________
[hidden email]
http://lists.gfoss.it/cgi-bin/mailman/listinfo/gfoss
Questa e' una lista di discussione pubblica aperta a tutti.
I messaggi di questa lista non hanno relazione diretta con le posizioni dell'Associazione GFOSS.it.
630 iscritti al 1.12.2012
Reply | Threaded
Open this post in threaded view
|

Re: shape che mette in crash Qgis 1.8

pcav
Il 11/01/2013 12:37, [hidden email] ha scritto:

> Ciao,
> ho un problema con il poligono di uno shape.
> Se provo a fare l'interrogazione con Qgis 1.8 SO Windows XP, il sistema mi va
> in crash.
> Se provo a selezionare il poligono e salvarlo con un altro nome non ho
> problemi di salvataggio, ma
> continuo ad avere problemi nell'interrogazione (mi va in crash).
> Ho provato a spezzare il poligono in due (con la funziona taglia) e mi
> compare
> il messaggio:
> "La geometria non è valida. Riparala prima di dividerla".
> Ho provato ad importarlo in grass ma continuo ad avere gli stessi problemi.
> Lo stesso shape con arview 3.3 e Udig viene interrogato senza problemi.
> Come posso provare a riparare la geometria?

provato, con la versione di sviluppo l'interrogazione viene eseguita correttamente;
il taglio, invece, provoca il freeze dell'applicazione.
credo sia il caso di aprire un ticket, allegando il file.
saluti.
--
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
_______________________________________________
[hidden email]
http://lists.gfoss.it/cgi-bin/mailman/listinfo/gfoss
Questa e' una lista di discussione pubblica aperta a tutti.
I messaggi di questa lista non hanno relazione diretta con le posizioni dell'Associazione GFOSS.it.
630 iscritti al 1.12.2012
Reply | Threaded
Open this post in threaded view
|

Re: shape che mette in crash Qgis 1.8

stefano campus
Administrator
In reply to this post by emanuele possiedi
lo shape ha 114 errori!
esegui il test sulla validità della geometria e te ne accorgerai.
vettore-->strumenti di geometria-->controlla validità di geometria
Reply | Threaded
Open this post in threaded view
|

Re: shape che mette in crash Qgis 1.8

Giovanni Manghi-2
In reply to this post by emanuele possiedi
> provato, con la versione di sviluppo l'interrogazione viene eseguita correttamente;
> il taglio, invece, provoca il freeze dell'applicazione.
> credo sia il caso di aprire un ticket, allegando il file.

confermo che su master l'identify funziona, sulla 1.8 é un problema
conosciuto, ossia quello dell'essere estremamente lento quando
identifica features molto complesse (quella in questione ha 70k
vertici),

se credete il ticket relativo

http://hub.qgis.org/issues/4819

si puó anche riaprire.... in effetti con features molto complesse (ho
appena provato con una con 1M vertici) é ancora abbastanza lento, in
particolare su Windows (mentre su Linux sulla stessa macchina é varie
volte piú rapido).

Per quanto riguarda gli errori (riportati di seguito): questi appaiono
solo se nelle opzioni di QGIS si usa "validate geometries" settato su
"qgis", mentre se si setta su "geos" non appare nessun errore. In
quets'ultimo caso lo strumento "split" dovrebbe forse funzionare
meglio, magari lasciano splittare anche una geometria non valida?




-- Giovanni --



0,segments 4 and 11 of line 1360 intersect at 447461.267665, 5000959.57033
0,segments 0 and 3 of line 1365 intersect at 405522.006663, 5000839.07891
0,segments 0 and 4 of line 1365 intersect at 405522.006663, 5000839.07891
0,segments 3 and 17 of line 1365 intersect at 405522.006663, 5000839.07891
0,segments 4 and 17 of line 1365 intersect at 405522.006663, 5000839.07891
0,segments 6 and 16 of line 1365 intersect at 405522.006203, 5000929.0796
0,segments 6 and 17 of line 1365 intersect at 405522.006203, 5000929.0796
0,segments 7 and 16 of line 1365 intersect at 405522.006203, 5000929.0796
0,segments 7 and 17 of line 1365 intersect at 405522.006203, 5000929.0796
0,segments 12 and 15 of line 1365 intersect at 405462.007282, 5000929.07912
0,segments 12 and 16 of line 1365 intersect at 405462.007282, 5000929.07912
0,segments 0 and 73 of line 1372 intersect at 407381.976357, 5000389.09059
0,segments 0 and 74 of line 1372 intersect at 407381.976357, 5000389.09059
0,segments 73 and 77 of line 1372 intersect at 407381.976357, 5000389.09059
0,segments 74 and 77 of line 1372 intersect at 407381.976357, 5000389.09059
0,segments 0 and 3 of line 1377 intersect at 405222.014513, 5000329.0725
0,segments 0 and 4 of line 1377 intersect at 405222.014513, 5000329.0725
0,segments 3 and 41 of line 1377 intersect at 405222.014513, 5000329.0725
0,segments 4 and 41 of line 1377 intersect at 405222.014513, 5000329.0725
0,segments 36 and 41 of line 1377 intersect at 405222.014221, 5000389.07297
0,segments 37 and 41 of line 1377 intersect at 405222.014221, 5000389.07297
0,segments 0 and 3 of line 1379 intersect at 459401.305, 5000239.6219
0,segments 0 and 4 of line 1379 intersect at 459401.305, 5000239.6219
0,segments 4 and 7 of line 1379 intersect at 459401.305, 5000239.6219
0,segments 0 and 18 of line 1399 intersect at 464411.290632, 4994149.48346
0,segments 18 and 51 of line 1399 intersect at 464411.290632, 4994149.48346
0,segments 20 and 24 of line 1399 intersect at 464381.291172, 4994269.48654
0,segments 20 and 25 of line 1399 intersect at 464381.291172, 4994269.48654
0,segments 21 and 24 of line 1399 intersect at 464381.291172, 4994269.48654
0,segments 21 and 25 of line 1399 intersect at 464381.291172, 4994269.48654
0,segments 0 and 20 of line 1418 intersect at 464831.284356, 4992619.44425
0,segments 20 and 23 of line 1418 intersect at 464831.284356, 4992619.44425
0,Geometry has 509 errors.
2,segments 0 and 3 of line 0 intersect at 401382.153288, 5018299.13498
2,segments 0 and 4 of line 0 intersect at 401382.153288, 5018299.13498
2,segments 3 and 3205 of line 0 intersect at 401382.153288, 5018299.13498
2,segments 4 and 3205 of line 0 intersect at 401382.153288, 5018299.13498
2,segments 255 and 259 of line 0 intersect at 398022.241794, 5019079.11566
2,segments 255 and 260 of line 0 intersect at 398022.241794, 5019079.11566
2,segments 256 and 259 of line 0 intersect at 398022.241794, 5019079.11566
2,segments 256 and 260 of line 0 intersect at 398022.241794, 5019079.11566
2,segments 277 and 281 of line 0 intersect at 398112.241674, 5019229.11656
2,segments 277 and 282 of line 0 intersect at 398112.241674, 5019229.11656
2,segments 278 and 281 of line 0 intersect at 398112.241674, 5019229.11656
2,segments 278 and 282 of line 0 intersect at 398112.241674, 5019229.11656
2,segments 401 and 404 of line 0 intersect at 398322.246442, 5020039.12088
2,segments 401 and 405 of line 0 intersect at 398322.246442, 5020039.12088
2,segments 431 and 435 of line 0 intersect at 398172.25138, 5020189.12086
2,segments 431 and 436 of line 0 intersect at 398172.25138, 5020189.12086
2,segments 432 and 435 of line 0 intersect at 398172.25138, 5020189.12086
2,segments 432 and 436 of line 0 intersect at 398172.25138, 5020189.12086
2,segments 1081 and 1085 of line 0 intersect at 394092.379621, 5023099.11307
2,segments 1081 and 1086 of line 0 intersect at 394092.379621, 5023099.11307
2,segments 1082 and 1085 of line 0 intersect at 394092.379621, 5023099.11307
2,segments 1082 and 1086 of line 0 intersect at 394092.379621, 5023099.11307
2,segments 1165 and 1170 of line 0 intersect at 394722.392338, 5024689.11765
2,segments 1166 and 1170 of line 0 intersect at 394722.392338, 5024689.11765
2,segments 1264 and 1365 of line 0 intersect at 395082.40719, 5026069.12129
2,segments 1264 and 1366 of line 0 intersect at 395082.40719, 5026069.12129
2,segments 1773 and 1791 of line 0 intersect at 399972.324258, 5027299.15864
2,segments 1773 and 1792 of line 0 intersect at 399972.324258, 5027299.15864
2,segments 1773 and 1794 of line 0 intersect at 399942.324885, 5027299.15834
2,segments 1773 and 1795 of line 0 intersect at 399942.324885, 5027299.15834
2,segments 1774 and 1791 of line 0 intersect at 399972.324258, 5027299.15864
2,segments 1774 and 1792 of line 0 intersect at 399972.324258, 5027299.15864
2,segments 2174 and 2178 of line 0 intersect at 400662.269449, 5024899.15676
2,segments 2174 and 2179 of line 0 intersect at 400662.269449, 5024899.15676
2,segments 2175 and 2178 of line 0 intersect at 400662.269449, 5024899.15676
2,segments 2175 and 2179 of line 0 intersect at 400662.269449, 5024899.15676
2,segments 2180 and 2184 of line 0 intersect at 400602.269746, 5024839.15601
2,segments 2180 and 2185 of line 0 intersect at 400602.269746, 5024839.15601
2,segments 2181 and 2184 of line 0 intersect at 400602.269746, 5024839.15601
2,segments 2181 and 2185 of line 0 intersect at 400602.269746, 5024839.15601
2,segments 2198 and 2202 of line 0 intersect at 400662.264397, 5024599.15567
2,segments 2198 and 2203 of line 0 intersect at 400662.264397, 5024599.15567
2,segments 2199 and 2202 of line 0 intersect at 400662.264397, 5024599.15567
2,segments 2199 and 2203 of line 0 intersect at 400662.264397, 5024599.15567
2,segments 2276 and 2285 of line 0 intersect at 398832.307365, 5024779.13994
2,segments 2277 and 2285 of line 0 intersect at 398832.307365, 5024779.13994
2,segments 2278 and 2282 of line 0 intersect at 398802.308505, 5024809.13976
2,segments 2278 and 2283 of line 0 intersect at 398802.308505, 5024809.13976
2,segments 2279 and 2282 of line 0 intersect at 398802.308505, 5024809.13976
2,segments 2279 and 2283 of line 0 intersect at 398802.308505, 5024809.13976
2,segments 2420 and 2424 of line 0 intersect at 397152.325618, 5023699.12722
2,segments 2420 and 2425 of line 0 intersect at 397152.325618, 5023699.12722
2,segments 2421 and 2424 of line 0 intersect at 397152.325618, 5023699.12722
2,segments 2421 and 2425 of line 0 intersect at 397152.325618, 5023699.12722
2,segments 2578 and 2582 of line 0 intersect at 397182.296566, 5021929.12317
2,segments 2578 and 2583 of line 0 intersect at 397182.296566, 5021929.12317
2,segments 2579 and 2582 of line 0 intersect at 397182.296566, 5021929.12317
2,segments 2579 and 2583 of line 0 intersect at 397182.296566, 5021929.12317
2,segments 2603 and 2608 of line 0 intersect at 397752.290994, 5022319.12628
2,segments 2604 and 2607 of line 0 intersect at 397752.290994, 5022319.12628
2,segments 2604 and 2608 of line 0 intersect at 397752.290994, 5022319.12628
2,segments 2748 and 2751 of line 0 intersect at 399012.278089, 5023219.1368
2,segments 2748 and 2752 of line 0 intersect at 399012.278089, 5023219.1368
2,segments 2780 and 2793 of line 0 intersect at 399012.267845, 5022589.13487
2,segments 2781 and 2792 of line 0 intersect at 399012.267845, 5022589.13487
2,segments 2781 and 2793 of line 0 intersect at 399012.267845, 5022589.13487
2,segments 2804 and 2809 of line 0 intersect at 399192.257894, 5022229.1352
2,segments 2805 and 2808 of line 0 intersect at 399192.257894, 5022229.1352
2,segments 2805 and 2809 of line 0 intersect at 399192.257894, 5022229.1352
2,segments 3102 and 3107 of line 0 intersect at 401532.151161, 5018419.13662
2,segments 3103 and 3106 of line 0 intersect at 401532.151161, 5018419.13662
2,segments 3103 and 3107 of line 0 intersect at 401532.151161, 5018419.13662
2,segments 0 and 77 of line 2 intersect at 398172.291386, 5022889.12949
2,segments 0 and 78 of line 2 intersect at 398172.291386, 5022889.12949
2,segments 77 and 81 of line 2 intersect at 398172.291386, 5022889.12949
2,segments 78 and 81 of line 2 intersect at 398172.291386, 5022889.12949
2,segments 0 and 3 of line 3 intersect at 398922.262576, 5022139.13277
2,segments 0 and 4 of line 3 intersect at 398922.262576, 5022139.13277
2,segments 3 and 11 of line 3 intersect at 398922.262576, 5022139.13277
2,segments 4 and 11 of line 3 intersect at 398922.262576, 5022139.13277
2,segments 26 and 34 of line 15 intersect at 397512.354208, 5025949.13437
2,segments 26 and 35 of line 15 intersect at 397512.354208, 5025949.13437
2,segments 27 and 34 of line 15 intersect at 397512.354208, 5025949.13437
2,segments 27 and 35 of line 15 intersect at 397512.354208, 5025949.13437
2,segments 28 and 33 of line 15 intersect at 397482.35532, 5025979.13428
2,segments 29 and 33 of line 15 intersect at 397482.35532, 5025979.13428
2,segments 0 and 3 of line 19 intersect at 399582.29001, 5024719.14646
2,segments 0 and 4 of line 19 intersect at 399582.29001, 5024719.14646
2,segments 4 and 203 of line 19 intersect at 399582.29001, 5024719.14646
2,segments 18 and 22 of line 19 intersect at 399462.301488, 5025259.14711
2,segments 18 and 23 of line 19 intersect at 399462.301488, 5025259.14711
2,segments 19 and 22 of line 19 intersect at 399462.301488, 5025259.14711
2,segments 19 and 23 of line 19 intersect at 399462.301488, 5025259.14711
2,segments 24 and 104 of line 19 intersect at 399432.303613, 5025349.14713
2,segments 24 and 105 of line 19 intersect at 399432.303613, 5025349.14713
2,segments 25 and 104 of line 19 intersect at 399432.303613, 5025349.14713
2,segments 25 and 105 of line 19 intersect at 399432.303613, 5025349.14713
2,segments 80 and 84 of line 19 intersect at 399372.311782, 5025769.1479
2,segments 80 and 85 of line 19 intersect at 399372.311782, 5025769.1479
2,segments 81 and 84 of line 19 intersect at 399372.311782, 5025769.1479
2,segments 81 and 85 of line 19 intersect at 399372.311782, 5025769.1479
2,segments 0 and 3 of line 47 intersect at 396282.354401, 5024359.12462
2,segments 0 and 4 of line 47 intersect at 396282.354401, 5024359.12462
2,segments 4 and 7 of line 47 intersect at 396282.354401, 5024359.12462
2,segments 0 and 4 of line 50 intersect at 395772.350025, 5023429.12062
2,segments 4 and 81 of line 50 intersect at 395772.350025, 5023429.12062
2,segments 0 and 3 of line 63 intersect at 394722.343157, 5021659.11386
2,segments 0 and 4 of line 63 intersect at 394722.343157, 5021659.11386
2,segments 3 and 7 of line 63 intersect at 394722.343157, 5021659.11386
2,segments 4 and 7 of line 63 intersect at 394722.343157, 5021659.11386
2,segments 0 and 3 of line 65 intersect at 394812.339835, 5021569.11406
2,segments 0 and 4 of line 65 intersect at 394812.339835, 5021569.11406
2,segments 3 and 7 of line 65 intersect at 394812.339835, 5021569.11406
2,segments 4 and 7 of line 65 intersect at 394812.339835, 5021569.11406
2,Geometry has 114 errors.
_______________________________________________
[hidden email]
http://lists.gfoss.it/cgi-bin/mailman/listinfo/gfoss
Questa e' una lista di discussione pubblica aperta a tutti.
I messaggi di questa lista non hanno relazione diretta con le posizioni dell'Associazione GFOSS.it.
630 iscritti al 1.12.2012