Users frequently run into issues on the Forums where they are trying to aggregate by a column that pygeoprocessing expects to be an Integer, but they have provided as a real. Classic example: a watersheds vector has a ws_id column where the ws_id column is ogr.OFTReal, but pygeoprocessing.aggregate_raster_values_uri requires that the column type is ogr.OFTInteger and raises an informative exception.
It would be great if we could allow this sort of validation in the UI.
Users frequently run into issues on the Forums where they are trying to aggregate by a column that pygeoprocessing expects to be an Integer, but they have provided as a real. Classic example: a watersheds vector has a
ws_idcolumn where thews_idcolumn isogr.OFTReal, butpygeoprocessing.aggregate_raster_values_urirequires that the column type isogr.OFTIntegerand raises an informative exception.It would be great if we could allow this sort of validation in the UI.