Skip to content
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

Shapefiles and Column Lengths #50

Open
slibby opened this issue Dec 17, 2014 · 1 comment
Open

Shapefiles and Column Lengths #50

slibby opened this issue Dec 17, 2014 · 1 comment

Comments

@slibby
Copy link

slibby commented Dec 17, 2014

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.
@slibby
Copy link
Author

slibby commented Dec 17, 2014

Linked to #19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant