You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Shapefile and Column text lengths:
When uploading shapefiles to create a layer, field length is respected in the edit/table in that you aren’t able to enter longer text strings than your original shapefile allowed. However, this brings up two issues:
1: While the DB enforces a column length, the export from the WFS is always a 255 character column, not the smaller character size expected. This is not a big deal as most of our data is small, but should probably be looked at as it can impact larger datasets where space-saving is helpful.
2: When editing in map view against a layer with a field length limit that is relatively short, if you try to enter in a value that is longer than the allowable field length and then save the feature, you get a generic error and cannot save the feature until you figure out which field you’ve over-entered in. Should be more detailed, I am guessing PostgreSQL returns a specific error that could be parsed.
The text was updated successfully, but these errors were encountered:
Shapefile and Column text lengths:
When uploading shapefiles to create a layer, field length is respected in the edit/table in that you aren’t able to enter longer text strings than your original shapefile allowed. However, this brings up two issues:
The text was updated successfully, but these errors were encountered: