4

I think you are trying to use a property that only became available in versions later than ArcGIS Pro 2.4. When I run the code below: import arcpy aprx = arcpy.mp.ArcGISProject(r"C:\temp\Projects\TestProject\TestProject.aprx") mapx = aprx.listMaps()[0] print(mapx.name) lyr = mapx.listLayers()[0] print(lyr.name) print(lyr.metadata.description) it ...


4

I suspect that you may be following a code sample for the metadata module of ArcPy which is only available to work with the ArcGIS Pro (and not ArcMap) application of ArcGIS Desktop, and only since ArcGIS Pro 2.5 was released: The Metadata class allows you to access an item's metadata, and export metadata to a standard metadata format. If you have ...


4

You can use layerOptions to add creation options. layerOptions is a list of strings formated as 'KEY=VALUE'. Hence, embedding a layer description in the geopackage just comes to adding options.layerOptions = ["DESCRIPTION=This are the roads covering such and such, Dec 2019"] Here is a generic function which saves a layer into a geopackage and uses the ...


4

In addition to axel_ande awnser: This error seems to occur whenever the metadata.txt is illformed! That might be also the reason why using the PluginBuilder helped for DIV in his awnser because the automatically generated metadata.txt is valid. Possible trap holes (be free to add more): missing required entries. see here tag separation is , only! Without ...


3

You may have an XML metadata file created from a different version of your file. If I start with just the grib file: $ ls -l total 192 -rw-r--r-- 1 rowlings rowlings 189591 Apr 12 11:53 snow.grb $ Then the stats are okay: $ gdalinfo -mm -stats snow.grb Min=-0.000 Max=0.917 Computed Min/Max=-0.000,0.917 Minimum=-0.000, Maximum=0.917, Mean=0.038, ...


3

GeoNetwork 3.6 uses GeoTools 16.0. This version of GeoTools doesn't support urn:ogc:def:crs:OGC:1.3:CRS84 CRS. The support for this CRS was introduced in GeoTools 17.1. GeoNetwork 3.8 still uses the GT 16 so the problem still exists in current GN release. Issue in GN for tracking the problem: #4072


3

pyexiv2 Solution: Select layer and run the script. You have to change values to string for non-string fields using str() method. This solution is about layers which were created by ImportPhotos plugin. For other layers, you must specify the file path related to feature. from pyexiv2 import Image layer = iface.activeLayer() for feature in layer....


2

The shapfile driver doesn't support metadata writing. However, the geopackage driver does: https://gdal.org/drivers/vector/gpkg.html#metadata Changing your code to use this should work with GDAL 2+: ds = ogr.GetDriverByName('GPKG').Open('C:/Polygons.gpkg', 1)


2

Not 100% on this but I think metadata is a work in progress, being approached from a number of angles. If you have metadata to save, apparently it can be saved to a file which sits in the same directory as the data. As per this answer QGIS Default Metadata If you are trying to read existing metadata from another system (your case) I presume QGIS is ...


2

It's fairly easy. You open and read the input raster as a numpy array, run your calculation, open the output raster in 'w' write mode and use the georeferencing and other metadata (aka the profile) from the input raster. import rasterio as rio import numpy as np def ndvi2bio(x): #function to convert from ndvi to BIO return 400*(x)+680 with rio.open('...


1

It is discussed in the documentation here: https://pro.arcgis.com/en/pro-app/arcpy/metadata/migrating-from-arcmap-to-arcgis-pro.htm I just use a simple wrapper: import arcpy from arcpy import metadata as md def pro_import_metadata(source_metadata:str, import_type:str, target_metadata:str, enable_automatic_updates:bool): target_item_md = md.Metadata(...


1

You can copy them to the new image using: newImg.copyProperties(oldImg, img.propertyNames()) Applied to your example: var scaledCollection = collection.map( function(img) { return img.multiply(0.0001).copyProperties(img, img.propertyNames()); }); print(scaledCollection); I can only speculate that properties are not maintained because it ...


1

I believe the issue is to do with which metadata you are accessing. Study your code you are accessing the metadata from what? A layer, but how did you get a handle on that...from the map document. You are not accessing the metadata of the dataset but a layer object in a map. If you go to the properties of the layer and change the dialog to layer has own ...


1

There is a new API that might be useful for your case, see https://github.com/qgis/QGIS/pull/38189 for a start.


1

I installed SNAPSHOT-metadata-plugin-2017 on my Microsoft Window 7 machine using Geoserver 2.17 and Apache Tomcat 9.0.36. Before staring please make sure that you are using JDK 11.0.2 (x64/86 based on your own OS system type). It's supported completely by both Geoserver 2.17.x and Apache Tomcat 9.x.x as it has been mentioned in geoserver consideration and ...


1

If you're using GeoTiffReader then you can call getMetadata() to get a GeoTiffIIOMetadataDecoder which you can use to access those metadata fields. If you know the exact metadata tags you want to extract then you can look up their TIFF tag codes using a site like https://www.awaresystems.be/imaging/tiff/tifftags.html and call getAsciiTIFFTag() with the code....


1

Based on the chapter 9 (Geometries) of the Introduction to PostGIS Workshop (http://postgis.net/workshops/postgis-intro/geometries.html), seems to me like the value stored in the type field of the geometry_columns table is showing the type of the first geometry stored in the referenced table. To store an explicit type and srid of geometry you need to cast ...


1

A digital elevation model is not representing an optical property of the earth's surface, such as its reflectivity at certain wavelengths, nor is it influenced by the phenomena of refraction or diffusion that occur in the atmosphere. Instead, it represents the elevation of the topographic surface with respect to a reference surface. Although the model ...


1

Looking over the link, the data you are accessing is a culmination of various data sources to create a seamless grid of elevation data. The "metadata" for the dataset: https://land.copernicus.eu/imagery-in-situ/eu-dem/eu-dem-v1-0-and-derived-products/eu-dem-v1.0?tab=metadata states: The EU-DEM v1.0 is derived from an automated data fusion process using ...


1

For what it sounds like you want to do, you could just use GeoNetwork, with PostgreSQL as the back end database.


Only top voted, non community-wiki answers of a minimum length are eligible