New answers tagged

4

You can map over a list of entire collection for checking, for each element in the list, if .bandNames().size() corresponds to number bands in original series. I tried my approach with an Image Collection of 124 images (Sentinel 2) where I arbitrarily added a created empty image to get 125 elements. Original images have 23 bands and empty band, by default, ...


1

Following script allows having some control of selecting dates in Image Collection. It includes an arbitrary fc geometry in USA. var fc = ee.Geometry.Polygon( [[[-104.60946499778431, 36.501117552980226], [-104.60946499778431, 35.86265852547925], [-103.45590054465931, 35.86265852547925], [-103.45590054465931, 36....


1

you can use the expression to add a new field and use this one for your filter:


0

Proposed solutions by Jukka Rahkonen jratike80: Need to input layer name ogrinfo -sql "select * from layer limit 1" file.gpkg Multiple lines, but can be put into script ogr2ogr -f gpkg temp.gpkp %input_here% -limit 1 ogrinfo temp.gpkg -al del temp.gpkg


0

For GeoJSON this sort of works (adjust -c to your needs): head -c 1000 HPG_2019_simplified.geojson prints: { "type": "FeatureCollection", "name": "HPG_2019_simplified", "crs": { "properties": {"name": "EPSG:31287"}, "type": "name" }, "features": [ { ...


1

Support for viewParams is up to the specific datastore, the needs to be special code to handle them. For example, here is the handling of view params in JDBC data stores (e.g., PostGIS, Oracle, SQL Server and so on), as part of the "SQL view" mechanism (dubbed "virtual table" down in GeoTools): https://github.com/geotools/geotools/blob/...


Top 50 recent answers are included