I’m facing issues importing GML file, I reproduced on the play server v2.29:
When I select Dry run option it show success message:
When I dont select Dry run option it keeps processing:
Below the GML file, generated with Quantum GIS v. 2.18.
gml_file.gml (87.7 KB)
@Emma_Kassy/ @Calle_Hedberg - would you please advise on this use case, please? @damasceno.lopes - kindly share your logs with us too since we can not tell much from this information, thank you.
On my way to Rena (in da Norwegian mountains) for some Birken & skiing time - try @jan
I have not been able to use the GML import on 2.29, it always bombs out with a nullexception error.
yesterday, in order to import a large GML file with updated orgunit coordinates, I had to upgrade a copy to 2.30, import the GML data, export the organisationunit meta-data to xml, and then import that into the 2.29 instance.
Thanks @Calle_Hedberg, it worked like a charm.
@jomutsani can you mark this as a solution?
My feeling is that such bastardized procedures should NOT be regarded as a “solution” - it’s more like a really time-consuming and cumbersome work-around because the developers do not have capacity to deal with all bugs (2.29 is by now basically no longer supported, so I doubt that bug will ever be fixed).
Maybe tag it as “Scallywag work-around” ???
Agreed and +1 for “scallywag”