-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Regression with uploading a shapefile with no ascii characters #4025
Comments
taking a look |
thanks @afabiani |
I realized it is not a regression, I tried the method as it was one year ago before your PR with mosaics and there is the same error. It could be that when I uploaded it correctly it was using geonode.rest vs geonode.importer (which I am currently using) |
hi @capooti indeed there is an issue, which should be handled somehow. However, in your specific use case I'm getting an error from GeoServer Importer, not being able to ingest the layer
|
Which GeoServer version are you using? I am with 2.14.x, and this is what I see in log:
Furthermore I can successfully import the shapefile with the GeoServer importer from GeoServer admin site. I believe it is definitely a GeoNode error. Thanks! |
I definitely think is a regression. I have downloaded a few shapefiles from our GeoNode instance - which were successfully uploaded with GeoNode 2.7.x and which have Chinese field names and now they all fail to upload. |
…cii characters (GeoNode#4026) * [Fixes GeoNode#4025] Regression with uploading a shapefile with no ascii characters * [Fixes GeoNode#4025] Regression with uploading a shapefile with no ascii characters * - Rename columns of non-UTF-8 shapefiles attributes before ingesting - Fix test cases
Using master I cannot upload this shapefile, which a few months could be uploaded:
ming_female_1.zip
The error is:
UnicodeDecodeError: 'utf8' codec can't decode byte 0xfd in position 1437: invalid start byte
This is happening in the upload.models.update_from_session() when the session is saved (self.save()).
I believe this can happen to any shapefile with sends some non-ascii character in the unicode_session and it can't be encoded/decoded. @afabiani any hint on this?
The text was updated successfully, but these errors were encountered: