-
Notifications
You must be signed in to change notification settings - Fork 14
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
problem with json format #1
Comments
confirmed exceprion is generated by mapscript call applySLD generating a IOError exception without other information. thenks for the report |
SLD generated before mapscript call applySLD: |
error come from this piece of code added as preliminary patch in mapscript should be managed by mapscript team |
wrote a report in the mapserver-dev list: hi mapscript I've a IOError generarted by applySLD call applying this SLD: https://gist.github.com/luipir/6139610 debugging msSLDApplySLD call I found that it exit with the last line mapogcsld.c:479 - return MS_SUCCESS; but an error code returned by python wrapper: _wrap_layerObj_applySLD errorObj *ms_error = msGetErrorObj(); returns: ms_error->code = 1 then wrapper scan ms_error-> code and return error to python... but applySLD was succesful! seems related to a preliminary patch: MapServer/MapServer#3114 applied one years ago I think it could be managed refining the code before applying the above preliminary patch thanks Luigi Pirelli (luigi.pirelli@faunalia.it) |
I found a bug using json file, it is possible to replicate converting lake.gml of Alaska dataset in GeoJSON format using ogr2ogr. The returned error is:
Traceback (most recent call last):
File "/home/lucadelu/.qgis2/python/plugins/rt_mapserver_exporter/mapfileexportdlg.py", line 353, in accept
if mapscript.MS_SUCCESS != ms_layer.applySLD( sldContents, ms_layer.name ):
IOError: msShapefileOpen(): Unable to access file. (/home/lucadelu/geodati/qgis_sample_data/gml/lakes.json)
msShapefileOpen(): Unable to access file. (/home/lucadelu/geodati/qgis_sample_data/gml/lakes.json)
The text was updated successfully, but these errors were encountered: